Ahh, that might be the crucial bit for us. ![]() Thanks for the info, sorry its taken a while to reply, I have not been well.ġ. This article covers PRT, but if not using FAS just ignore the Cert part but follow the Workplace Join section. If you are using Hybrid Azure AD, make sure to get it setup for proper TGT or PRT generation for users single sign-on. Enable Shellbridge, it fixes a lot of auth messages.ģ. Make sure you are using a profile manager that can support the token storage of office. Not quite the same, but we are on 2203 CU1 so doesn't apply.ġ. Applocker is NOT currently enabled, for testing. Tried : HKEY_CURRENT_USER\Software\Microsoft\Exchange, AlwaysUseMSOAuthForAutoDiscover dword=1Ĩ. We had already blocked AAD workspace join using : HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: “BlockAADWorkplaceJoin”=dword:00000001ħ. Clearing local credential store made no difference. Checked the 2012 R2 UPM profile vs 2019 and its essentially the same, just a few additions for 2019 start menu etc.ĥ. Tried setting the overridecache and cachelocation settings as well, still no files. Given that the dir is not synced in the 2012 UPM profile, the files are not there in 2012 R2, but 2012 R2 VDAs are working fine, I don't think that is related.Ĥ. I tried adding it to sync dir in UPM as a test, nothing appeared in UPM or in the local VDA profile. I thought I should as we are using shared activation, but I wasn't the one who setup O365 office when we moved to it 2 years ago. I don't see any files in %localappdata%\Microsoft\Office\16.0\Licensing on 2012 R2 or on 2019. This DOES fix it, but as per the article ( ), is not recommended, so trying to understand the issue and resolve it, rather than masking it.ģ. Reg add "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity" /v DisableAADWAM /t REG_DWORD /d 1 /f Reg add "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity" /v DisableADALatopWAMOverride /t REG_DWORD /d 1 /f Next time they launch the desktop they get the same login prompt again.ġ. If they login and do 2FA then they are able to use Outlook just fine for the duration of that session. ![]() On 2019 we have a MS login prompt for Outlook each time the user launches the Citrix desktop. Users are OnPrem users, synced to O365/AAD, mailboxes are in 365 now so hybrid setup. We use Office 365 apps, Office, Word etc. Note: Please follow the steps in our to enable e-mail notifications if you want to receive the related email notification for this thread.We have been using Server 2012 R2 for our VDAs for a long time, finally moving to Server 2019. ![]() If you have extra questions about this answer, please click "Comment". If the answer is helpful, please click "Accept Answer" and kindly upvote it. To find the settings, follow: File>Account settings> Account settings>Change>More settings>Security>User identification. Please check if you configure Outlook to always prompt you for login credentials.Did you try the above steps to clear login credentials helpful? Considering the issue of login credentials, I agree with S.Sengupta.Please check your version of Outlook to make sure it is the latest version.To resolve this issue, you can try the following solutions: Can you log in normally using Outlook for Web?.Do you have the same problem when logging in to another account?.What does this ‘credential window’ refer to? Can you provide a screenshot (please be careful to cover your personal privacy information.).Hi our better research, please provide more information about this case:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |