My next step is to open a case with VMware if I can't get it resolved. Update history for Office 365 ProPlus (listed by date) | Microsoft Docs Has anyone ran into this problem? If you don't have this problem and have a similar setup as mine, what Office 365 build are you using? You can find a build history here: Shared Computer activation is definitely enabled. If I click "Fix Me" I have to sign back into Office 365 or sometimes just reactivate. I have tried having these Office 365 builds via App Volume or baked into the master image. Office 365 account persistence works for a bit but then after a while, this happens: I have authentication token roaming setup to the UEMProfile network share via GPO and capturing \Microsoft\Credentials via UEM (in the Office 2016 Shared Settings template). I am running an instant clone non-persistence desktop pool with Windows 10 Enteprise Build 1709. This will list the currently installed Office products. Users with 64 bit version of Office would change directory to c:program filesMicrosoft OfficeOffice16). I am in the process of setting up a new VDI environment and having a very hard time with Office 365 account persistence. They had me open an elevated command prompt and change directory to the c:program files (x86)Microsoft OfficeOffice16 (mine is 32 bit.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |