Forum Discussion

DAsnow's avatar
DAsnow
Copper Contributor
Nov 21, 2019
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...
  • Doug_Coombs's avatar
    Doug_Coombs
    Nov 22, 2019

    DAsnow this scenario isn't ringing a bell in terms of a common scenario, probably best to contact support on this.

carliv's avatar
carliv
Copper Contributor
Apr 08, 2020
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.
Tom_A_MSFT's avatar
Tom_A_MSFT
Icon for Microsoft rankMicrosoft
Apr 16, 2020

carliv  if you are getting AADBroker plug in errors in the event viewer can you try a couple things to help identify the issue?

 

1. From PowerShell check if AADBroker plug in is registered by running this command, note this is a per user install so you will need to have user experiencing this issue try this: 

Get-AppxPackage Microsoft.AAD.BrokerPlugin

2. If it returns no output, issue is the AADBroker plug in isn't registered. Now see if you can force registration, again from user session:

Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

3. I suspect when you run the second command it may hang and never progress past "Initializing"

4. If #3 is true, then the AppXSvc is having an issue. To resolve you'll need to do the following as admin on the VM experiencing the issue:

  1. Go to TaskManager>Services, find AppxSvc, note processID
  2. Rt. Click AppxSvc> Go to Details>End Task
  3. Once AppxSvc is in stopped state, again from TaskManager>Services>AppxSvc Rt.Click>Start

5. Now have user run the registration command again:
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown


If it succeeds we know the AppxSvc was blocking. This should at least workaround the issue. Let me know if this works and the OS version of the VM you are experiencing the issue on.