![]() 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.
0 Comments
Leave a Reply. |