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.
We gave users a shortcut to remove WorkplaceJoin:
dsregcmd.exe /forcerecovery
The user must supply credentials and will receive an error at the end of the wizard about a policy block (because of the BlockAADWorkplaceJoin registry key). Outlook would start working immediately in some cases; other users had to Sign Out and Sign In to one of the Office apps.
Everything was perfect for two weeks, but now we're getting reports of Outlook not syncing. This time, there's no authentication prompt or the Need Password icon in the status bar. One user I checked with so far had Status OK for Get-AppxPackage Microsoft.AAD.BrokerPlugin, so that doesn't seem to be the issue.
Hi Wyatt_Best
Thanks for sharing it. Actually, I have reset all profiles. It fixed the main problem. I also had to redeploy my hosts because we were getting some conflicts (eventually Teams or Onedrive started in disconnected) and I saw my old hosts were with some references on Azure AD. Today was the first day after all renewed Seems that users could work fine.
One of the issues that is in place after changes is that all Office apps are like standalone. They asked to type in credentials in all of them. I'm thinking what a mess will be to change passwords. How have you workaround it guys?
- This in conjunction with the GPO to block future Azure AD Joins is the solution
- bing_badaboem,
Do you have found a solution for the problem? We also use RDS 2019 with FSLogix and two servers. Sometimes Outlook (and Teams) ask for a password. Solution is to log the user in to the other server.
I don't want to create new user profiles for all the users.
Mark Lunn Do you have a script for me? Thank you Mark.
We use 2019 rdsh and fslogix with same problems with outlook.
We went for the route to enable sso and hybrid azure ad join.
From the two reg keys we needed to skip the second so only have the
[HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin​]
"BlockAADWorkplaceJoin"=dword:00000001in place. Otherwise the machines won't go past pending state in aad.
Even with the current fslogix profiles people now are able to open outlook.
Time will tell if it's permenant. We did not yet enabled conditional access to bypass mfa.
Thanks Mark!
Aditional Info: Microsoft finally helpded us and has published a solution:
https://docs.microsoft.com/en-us/office/troubleshoot/activation/reset-office-365-proplus-activation-state#clear-credentials-from-workplace-join
WPJCleanUp.cmd
It works! Without having to recreate FSLOFIX profile.
Hope it can helps someone else.
Regards!
Berni
- Have sent you a PM. I am currently trying to write to info into a blog
Mark Lunn can you provide me with the script too?
Or is there a blog or post somewhere for this script?
If I understand correct the command dsregcmd /forcerecovery will do the same but manually.
So running this command once per user would do the same as the script but manual?
regards,
- Could you PM it to me as well ? Thank you.
- Hi JSpecMugen,
PM has been sent I'd like to get a copy of the script used to clean out the tokens for existing profiles. I'd also be willing to help get the write-up out there. I know it's going to be corrected moving forward, but with the likes of Nerdio and NetApp "instant deploy" users out there... This would be immensely helpful to a large group of admins.
Appreciate all the hard leg work you've put on this. Very interested the process behind the script.
-Cheers
Unfortunately, our users just authenticate a lot. It's extra burdensome because we have MFA enabled.
