
Microsoft Office 365 Product Key Generator Online 2021. Microsoft Office 365 Product Key Generator Overview. This still doesn't fix SSO so users still have to go through the sign-in process on initial profile creation so I wouldn't consider it an acceptable solution for production, but it's pointing in the right direction. HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity:"EnableADAL"=dword:00000000 So what happened between those Office 365 builds? One likely answer is Modern Authentication, and indeed if you disable this with the following reg value it changes the sign-in dialog to a legacy one that does work with XenApp on Windows 2019 as attached: Unfortunately this version went out of support a year ago, so is not really a viable workaround even in the short term. 2278 (1705) works 100% SSO on first app launch, no sign-in required. 2372 (1708) doesn't work but behaves differently prompts for sign-in, enter email then instead of password box you get an additional seamless Word window with no content pop up in the background that prevents you clicking anything else in Word. 2428 (1803) does not work same symptoms as current and all in between versions I've tested. OK so not exactly success, but progress with different O365 versions: I'll try and nail down the last working version as that might be an acceptable workaround until Citrix/MS get this fixed between them. Interesting to hear that older versions of Office 365 work too. Suspicion that it's something to do with that new Windows Defender Exploit Protection crap, but I've disabled everything I can to no avail. So looks like something in Server 2019 is breaking whatever Citrix does for web redirection, causing SSO to break. When launched via XenApp, Office 365 is automatically activated by SSO as it ought to be. Then launch an Office app with the same user on the same VDA via XenApp it retains the activation in the local profile.įor comparison I built a Server 2016 VM with the same VDA and Office versions, same OU/GPOs and the same test user account. RDP to the VDA then SSO works and Office 365 is activated automatically, no sign in required. Launch an Office app from XenApp, get prompted to sign in then the blank white box where the password prompt should be.
Office 365 1907 (11901) with shared computer activation.
Exactly the same issue here attempting to build the same setup.