But when we had a test user with the activation problem, we deleted the following registry key: But after some more testing, we noticed the problem came back.Īfter some investigation on the internet, I found the following article.Īt first, this didn’t seem to be related to our problem. Since the customer had implemented ADFS, these lines could be safely removed from the VMware UEM configuration.Īfter we reset the VMware UEM profile settings (Office 2016 – Shared Settings.zip) for a couple of test users, the problem at first seemed to be solved. When I reviewed the VMware UEM configuration, the following two lines were added in the “Office 2016 – Shared Settings” personalization configuration:Īs stated in the article, you only have to save (and roam) these settings if you do not use Single Sign-On. However, as mentioned earlier, sometimes the users were prompted to re-enter their credentials again. The customer had implemented ADFS and SSO worked most of the time. The recommended approach is to always use Single Sign-On.
#Office 2016 activation key problem license#
Next, I reviewed the article how the license token renewal process works. The most important part of non-persistent VDI is configuring the deployment.xml with the “SharedComputerLicensing” property, as indicated in the mentioned article. It turned out, the customer had installed Office 365 correctly in their base image. When I started troubleshooting, I used the following article for Office 365 Click-to-Run installation requirements, activation and roaming of the license token. However, the problem would always re-occur. When they deleted the user’s profile, the problem was gone and the users could work again for a couple of days. The customer gave me some additional information. ADFS implementation (Used for Single Sign-On).Office 365 Click-to-Run (latest version).Horizon Cloud with Hosted Infrastructure version 17.2.The customer environment consisted of the following components:
The result: Office 365 activation didn’t work and they could not use their Office applications. In most cases, the “Fix me” button didn’t work for the users, nor did re-entering the credentials. At random, some users were required to re-enter their Office 365 credentials Single Sign-On was not working correctly.When users start up an Office application, sometimes they would receive the following error: “There is a problem with your account, please try again later”.This week a customer informed us they had a strange problem with Office 365 Click-to-Run.
0 kommentar(er)
