The recommended approach is to always use Single Sign-On. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |