Forum Discussion
Outlook login issues with WVD - FSLogix
DAsnow this scenario isn't ringing a bell in terms of a common scenario, probably best to contact support on this.
User logs on, profiledisc created, user logs on, gpo's work fine and all behaves 'correctly'.
we configure outlook (autodiscover via O365) and outlook starts.
user logs off and at next logon if they are redirected to another host all hell breaks loose.
outlook says; "password required". If we click the prompt the 'signon' bliks and dissapears.
E.g. Outlook does not work any more.
If we then remove profile (%appdata%\local\microsoft\outlook inkl. roaming) and create new profile and try to configure outlook it gives an error 'are you this user' blablabla...
Tried setting different regsettings but nothing helps also tried updating to newest Windows 1909 but to no avail.
if we however DELETE the entire VHD profile then we can configure outlook for that user again but only that way.
These are the reg keys we used for WVD session hosts :
[HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin]
"BlockAADWorkplaceJoin"=dword:00000001
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WorkplaceJoin]
"autoWorkplaceJoin"=dword:00000000"
If you go back to some of my other posts, I describe what is happening in detail. The short version is that Office Pro Plus is doing workplace join as designed for non-Hybrid Azure AD joined devices on Host A. The Modern Authentication/Azure AD token contains a device ID tied to Host A. When the user logs into Host B, the token is invalid as the device ID no longer matches to the host. So, Outlook freaks out and Modern Auth breaks.
You must get the registry keys in place on the hosts (I used a GPO), then delete the user profile to clear the token/workplace join settings in the user's profile.
Although, I think someone else in this thread figured out a command to remove the workplace join without needing to delete the profile, not sure.
I believe that the new multi-session Windows 10 images have the registry key by default but your issue indicates that you do not have the keys.
