Jump to content
  • 0

Citrix UPM breaks Office 365 Activation


Marc Kuhn

Question

Hi all

 

we are building a new environment with Server 2019 and 1912 LTSR and Office 365 ProPlus. At the moment we are struggeling with the shared license activation.

 

I sorted it out that it is working like a charm without Citrix UPM, As soon as i configure UPM the activation isn't working anymore.

 

We are not using FSLogix. Does anyone have any similar issues?

 

Many thanks for your feedback

 

Best regards,

Marc

Link to comment

18 answers to this question

Recommended Posts

  • 1

I suspect your issue is similar to mine.  1912 UPM seems to have issues.  If I disable UPM or rollback to 1909, everything works.

 

https://discussions.citrix.com/topic/406984-vda-upm-1912-office-365-authentication-issues/#comment-2058482

 

Others have reported similar issues with other apps when using 1912 UPM, there is a provate fix available

 

https://discussions.citrix.com/topic/406884-windows-10-modern-apps-breaking-wsappx

 

  • Like 2
Link to comment
  • 0

Hi all

 

after researching more and more we found that solution, which is working for us at the moment:

 

https://help.duo.com/s/article/5253?language=en_US

 

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]
"DisableADALatopWAMOverride"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]
"DisableAADWAM"=dword:00000001

 

But we are wondering, if that is a normal behaviour or could that be probably an issue with the Citrix UPM from 1912 LTSR?

Link to comment
  • 0

Hi guys,

 

I have make upgrade from 1909 to 1912 to solve a problem with UPM, but now have the problem with Office 365 ProPlus Activation, but aditionally i have a open case about that, and now i think i found here the solution with this post:

 

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]
"DisableADALatopWAMOverride"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]
"DisableAADWAM"=dword:00000001

 

I gonna make the test with 200 of user, and gonna tell you what happend.

 

Link to comment
  • 0

Hi hortiz588

 

i tested in my environment, if in the registry of the user the inheritance is broken like written in this articel:

 

https://discussions.citrix.com/topic/406884-windows-10-modern-apps-breaking-wsappx

 

and found out that is true. Probably the better workaround would be to test if it works, when you enable it again. i just don't know yet how to do it via GPO.

 

Best regards,

Marc

Link to comment
  • 0
3 minutes ago, Marc Kuhn said:

Hi hortiz588

 

i tested in my environment, if in the registry of the user the inheritance is broken like written in this articel:

 

https://discussions.citrix.com/topic/406884-windows-10-modern-apps-breaking-wsappx

 

and found out that is true. Probably the better workaround would be to test if it works, when you enable it again. i just don't know yet how to do it via GPO.

 

Best regards,

Marc

Hi Marc,

 

I just have follow the inheritance procedure, but the authentication activation of the office 365 is lost when the user logon and logoff and logon again,  so i make by GPO the regedit agregation of the 2 keys found here, and it start to works fine when the user logon and logoff in diferents machines.

 

 

Link to comment
  • 0

Hi hortiz588

 

i think there should be a possabiliby to set the inheritance to enable again somehow. But with lack of time i wasn't able to check that deeper. Probably you can get the fix from Citrix. Or if FSLogix would be also a solution you can go with a Userprofile without Citrix UPM. I tested that with W2019 and 1912 LTSR and Offce365 is activating well.

 

For the moment i guess we are going with the 2 regkeys as well in our envionment we have with Citrix UPM enabled.

 

Best regards,

Marc

Link to comment
  • 0

Hi Marc,

 

I understand why is working in your enviroment, is because you have shared activation, we have here Windows 10 1909, and Citrix VDA 19.12 and its random vm to users. So i think that its why, but i have the great notice is with the combination of the inheritance and 2 keys works now fine the activation and maintain the token and user logon.

Link to comment
  • 0

I got the private fix from Citrix, it resolved the AppModel-State errors in my thread here

 

https://discussions.citrix.com/topic/406984-vda-upm-1912-office-365-authentication-issues/#comment-2058482

 

But Office and Onedrive still won't auto sign in and obtain a licence.  I will try the 2 reg keys above, but everything was working with 1909 and 7.15 CU5 without these keys.  An additional issue, my login time are incredibly long now.

Link to comment
  • 0

Anyone still having this problem?  I've put in the reg fixes and it stops the sign in prompt/activation problem, but Outlook now takes a very long time to open and i can see its getting stuck at the Modern Auth window.  Eventually after about 3-4 minutes it auths and starts OK

 

I have to stay on at least VDA 1912 because of MS Teams Optimization features that we use

Link to comment
  • 0

Just to add to this.

 

We are having the same problem with office 365 and server 2019.

We are using FSlogix but this is a POC so only testing for now.

 

There was some REG key we tried and it worked but the VM is now having problems logging in.

Removed the REG key office Activation failed again but could log into the VM.

 

We have a call open with MS and they are saying it is a problem with the new security build into Server 2019 .

They did confirm that Citrix and MS is working on a Fix.

 

 

 

 

Link to comment
  • 0

So i got a answer back From MS about the Problem with Office 365 and Server 2019

 

We have since analyzed the logs we had and after further discussions with NAME we have reached the conclusion that this behavior is a known issue that both Microsoft and Citrix are working on fixing at the moment; there is also an article on the Citrix side explaining this:

 

https://support.citrix.com/article/CTX267071

 

At the moment, the recommendation is to use the workaround that is mentioned here which is to disable AdalatopWAM by adding the following key:

 

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity

“DisableADALatopWAMOverride”= dword:00000001

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...