Forum Discussion
Solved
Outlook login issues with WVD - FSLogix
Having an issue where user of WVD Windows 10 Multi-session have issues moving between hosts. Essentially first login on a host is fine, when the user moves to a new host outlook eventually says "need...
DAsnow this scenario isn't ringing a bell in terms of a common scenario, probably best to contact support on this.
This is very interesting, I'am in the same situation with outlook sign in issues on new rds plattform with 2019 and latest 365 office suite. Work for a while, but suddenlty some users cant login to outlook, event viewer has alot of aadtokenbrokerplugin error on the rds host where user are logged on.
We dont use seamless sso/adsync or adfs becausse there are users from many different 365 tenants. Open case with Ms Support, but for now they just messing around with the wrong things.
We dont use seamless sso/adsync or adfs becausse there are users from many different 365 tenants. Open case with Ms Support, but for now they just messing around with the wrong things.
Hi Carlinge,
I resolved this exact case with Microsoft last week. The issue is a defect in Office which "workplace joins" the session hosts by default. This causes a token to be created associated to the session host where Office is initially setup and cannot work as users move around to other session hosts.
The fix is to enter these registry keys for all session hosts (I pushed out through GPO and it works fine)
[HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin]
"BlockAADWorkplaceJoin"=dword:00000001
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WorkplaceJoin]
"autoWorkplaceJoin"=dword:00000000
Also, if you have an issue after doing this, it may be that the appx package for the AAD Token Broker plugin is not working. You can get this working again by implementing a login script that does the following:
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode
I have my case numbers in one of the previous post if your MS Support person would like to reference.
I resolved this exact case with Microsoft last week. The issue is a defect in Office which "workplace joins" the session hosts by default. This causes a token to be created associated to the session host where Office is initially setup and cannot work as users move around to other session hosts.
The fix is to enter these registry keys for all session hosts (I pushed out through GPO and it works fine)
[HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin]
"BlockAADWorkplaceJoin"=dword:00000001
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WorkplaceJoin]
"autoWorkplaceJoin"=dword:00000000
Also, if you have an issue after doing this, it may be that the appx package for the AAD Token Broker plugin is not working. You can get this working again by implementing a login script that does the following:
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode
I have my case numbers in one of the previous post if your MS Support person would like to reference.