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.
This is still a big problem for us as well. Can someone at Microsoft weigh in here?
clwendt we have identified that having the auto-workplace join feature in combination with a profile solution can lead to unpredictable results, e.g. the office login plugin not functioning.
We are taking a couple of actions:
1) Working with the feature team to disable auto-workplace join on the win10 multi-session SKU.
2) While #1 isn't done: adding a registry key in the image to disable auto-workplace join
Both will only apply to new deployments.
For existing deployments you can find a workaround in this thread. In summary:
There are two ways of preventing this:
- You should REALLY updated the Documentation to state NOT to use AZ AD DS for other than PoC's
Im like 1 month into a project and testing have gone really well (But after Token expirery etc.) all the issues keeps coming..
There is a ton of issues on WVD / MultiSession OS with all Microsoft applications - works like a charm with almost all other software except the products that MS provide etc..
When something is changed it just breaks something else.. 😞 - So if i implement #1 i need to reset the users FSLogix Profile?
Or is it just working after relogon?
Is there a manual fix to remove the Token / Identity which does NOT involve recreation of the profile? PieterWigleven Great to hear there is a fix underway! How can we make sure that we get the announcement when the fix is out?
clwendt timeliness have not been defined yet but could be as early as next month. Images are updated in the second week of a given month.
This is for new deployments only, for existing ones please consider using on of the workarounds.
