Nov 21 2019 01:45 PM - edited Nov 21 2019 01:46 PM
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 password" however the modern authentication prompts are never presented to the user.
Anyone have any insight? Perhaps Something with AzureFiles / FSlogix?
Thanks in advance.
Sep 21 2020 02:15 AM
@Warent2454Have sent you a PM with the details.
-Mark
Sep 21 2020 06:10 AM
@Mark Lunn can you share the script to clean the user profiles? Thanks
Sep 22 2020 12:24 AM
Could you share your workaround for the profiles ?
Sep 28 2020 01:22 PM
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
Nov 04 2020 03:50 AM
@Mark Lunn - is there any way I could get a copy of the script to clear the token please? Really do not want to recreate profiles for 200 users!
Thanks in advance
Simon
Nov 04 2020 04:58 AM
Nov 06 2020 04:48 PM
@Mark Lunn Can you send me the script to me as well? Thanks a lot.
I have to say that dsregcmd.exe /forcerecovery is a great workarround in the mean time.
Nov 11 2020 11:54 PM
@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,
Nov 12 2020 03:11 AM
@Berni81Have sent you a PM. I am currently trying to write to info into a blog
Nov 12 2020 03:12 AM
Nov 12 2020 05:47 AM
Thanks Mark!
Aditional Info: Microsoft finally helpded us and has published a solution:
WPJCleanUp.cmd
It works! Without having to recreate FSLOFIX profile.
Hope it can helps someone else.
Regards!
Berni
Nov 12 2020 06:38 AM
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:00000001
in 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.
Apr 06 2021 12:12 AM
Oct 12 2021 06:28 AM
Oct 12 2021 06:31 AM
Oct 12 2021 06:34 AM
Oct 12 2021 06:38 AM
Oct 12 2021 06:39 AM