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.
MicrosoftDAsnow can you try to manually register the AADBroker plug in on the user session that is experiencing this issue?
From Powershell, first verify if it's installed:
Get-AppxPackage Microsoft.AAD.BrokerPlugin
I would it expect that the ADDBrokerPlugin isn't installed, if so, try to manually register the app:
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode
Tom_A_MSFT
The command to register the AAD Broker plugin works but does not persist after logoff/logon. Additionally, all new profiles need this command to be ran. We have implemented a login script that runs the AAD Broker plugin registration command which is keeping Modern Auth working for all users at this point but we cannot seem to get to the root cause. We have engaged Microsoft support and our partner resources but the issue doesn't seem to be able to be replicated with a standard gallery image.
I'm suspicious of FSLogix. I'm going to test disabling FS Logix and see if local profiles do not have the issue. However, we've simply set everything up per MS documentation on our Win 10 multi-session image, installed Office in shared activation mode per the WVD documentation, then snapshot, sysprep, and re-deployed using the WVD deployment template and our custom/sysprep image. We've also gone back to the bare basics in terms of the FS Logix GPO after tinkering with various settings.
I will update this thread as we learn more but any new information would certainly be appreciated. I'll just state the obvious here but turning off modern authentication through the registry is not an option for our MFA enabled accounts.
I've also found a past issue where FSLogix was having issues with edge and the solution was to register the appx package for edge.
Article on FSLogix forum here:
https://social.msdn.microsoft.com/Forums/windowsserver/en-US/d18184fe-a703-44e8-a4d3-f824ed10eeb6/edge-disappears-after-november-2019-updates?forum=FSLogix#3ae4fa02-dba2-4790-9655-d81efeef52f3
I'm not sure if anyone else has noticed additional appx package issues. We also see a black screen at login for users due to app readiness service. We are also seeing failures for some of these additional appx packages (which can be temporarily fixed by registering again in PowerShell).
Faulting application path:ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
WindowsInternal.ComposableShell.Experiences.TextInput.InputApp.exe
microsoft.windowscommunicationsapps_16005.11029.20108.0_x64__8wekyb3d8bbwe
Microsoft.WindowsStore_11811.1001.18.0_x64__8wekyb3d8bbweDeanbostedor I'm having the exact issue you described and also believe it's an FSLogix problem. Have you made any progress troubleshooting? I've gone through the same steps you described.
I can easily reproduce the issue when using the FSLogix profile service and logging in to the brokered WVD service with the Remote Desktop app, but if I login to the WVD hosts directly using MSTSC, and get a local profile, the issue cannot be reproduced.
Rob Blankers - Quick question -
Are you using Azure Active Directory Domain Services?
I've found that when the users first launch Outlook or OneDrive, they are prompted to register the device (this is by default). When they do this, the Windows 10 session host is workplace joined/Registered to them in Azure AD. However, when they move to new hosts they are never asked to register the new Windows 10 session host. It appears that after a length of time, they need to authenticate while being on the original host that they workplace joined or they start receiving the "need password". If I put the other hosts in drain mode and log them in, they can authenticate again.
Could you try this and let me know if you see the same behavior?
- Tom_A_MSFT i was having the same problem as others on this thread, and manually registering the aadbrokerplugin per your recommendation fixed the issue. thanks.
Tom_A_MSFT activating the aad brokerplugin in a user session doesn't appear to persist. i logged out and back in and i'm back to the same problem i had before.
