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.
Did you look at this link? It's actually documented right in their known issues. It doesn't matter how many times you try to work around it 2210 forces this behavior. The only solution I have found is to downgrade back to FSLogix 2201 until Microsoft creates a path forward. Stay on 2201 do not upgrade to 2210.
https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#azure-ad-authentication-for-applications
https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#azure-ad-authentication-for-applications
I have. Still in talks with MS regarding a fix or at the very least a switch to control the behaviour in 2210+.
From 2210+ those 3 folder locations "no longer roam" with FSLogix. The manner in how they do that is unknown to me at the moment. You can still redirect those folders to the local disk and they actually get populated. But it looks like 2210 just ignores them altogether.
My way (only works 2201 and before) is better for persistent VM's: Just use the Microsoft Azure AD broker plugin and dump that info local to the host. Their way requires the user to login everytime on every O365 app. Unworkable in my opinion. But my way only works with persistent hosts so both have their flaws I guess. Will keep the post live with updates from the case. It's being escalated...again.
From 2210+ those 3 folder locations "no longer roam" with FSLogix. The manner in how they do that is unknown to me at the moment. You can still redirect those folders to the local disk and they actually get populated. But it looks like 2210 just ignores them altogether.
My way (only works 2201 and before) is better for persistent VM's: Just use the Microsoft Azure AD broker plugin and dump that info local to the host. Their way requires the user to login everytime on every O365 app. Unworkable in my opinion. But my way only works with persistent hosts so both have their flaws I guess. Will keep the post live with updates from the case. It's being escalated...again.
- Supper frustrating. Almost like firing your whole UAT team was a bad idea for Microsoft 🤔🤔.
My last response from Microsoft on my ticket says they will have a hotfix for this but I'm not holding my breath.