Pascal Springer

okay, so we are talking about the token in %localappdata%\Microsoft\Office\16.0\Licensing. For this we have only the machinie GPO active: "Use shared computer activation" The tokens from the user are stored in the profile in the mentioned path. They tokens are copied back to the network store at logoff. With the next login they have there token back. This way it worked without any issues till 10.2023. With the Office patches from October 2023 it startet with some users seeing error 1001. Mostly always in published apps.

Sorry forgot to ask: So wich legacy token do you mean?

Hi Jeff, sorry for the late response. No we don't have hybrid join. VDAs using the onprem AD. We also not using profile disks like fslogix. We are still on Citrix UPM only. We are planing to move to profile disk with our new storage..

Hello Every one. we have still this issue, basicall in published Apps. We are running Windows Server 2022, Citrix LTSR 2203 CU4, Citrix UPM with WEM. No vhdx profiles. In the past - without this issue - we had all mentioned reg keys ("DisableADALatopWAMOverride", "DisableAADWAM", "DisableMSAWAM") keys activated and also this one: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity\EnableADAL - DWORD 1 After the issue starts we tried it with deleting all mentioned keys , this did not help. We tried it also with only this one: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Exchange\AlwaysUseMSOAuthForAutoDiscover - DWORD 1 Additoneld we did everything mentioned here: https://support.microsoft.com/en-us/office/error-something-went-wrong-1001-signing-in-to-microsoft-365-desktop-applications-6f63238d-d83c-437c-a929-de72fe819793 Now we are testing Francois "Solution with only the mentioned Keys DWORD 0 and also HKEY_CURRENT_USER\SOFTWARE\Microsoft\Exchange\AlwaysUseMSOAuthForAutoDiscover - DWORD 1 But I think this will no help. Does some have a real solutuion? It would be really nice to know :) Regards

It seems CU4 Update 1 fixed this issue.