Office 365 account problems

[blue_calx]

Hello,

I am in the process of setting up a new VDI environment and having a very hard time with Office 365 account persistence. I am running an instant clone non-persistence desktop pool with Windows 10 Enteprise Build 1709.

I have tried Office 365 builds 1708 and 1803. I have authentication token roaming setup to the UEMProfile network share via GPO and capturing <LocalAppData>\Microsoft\Credentials via UEM (in the Office 2016 Shared Settings template).

Office 365 account persistence works for a bit but then after a while, this happens:

I have tried having these Office 365 builds via App Volume or baked into the master image. Still the same results. I am pulling my hair out on this one.

If I click "Fix Me" I have to sign back into Office 365 or sometimes just reactivate. Shared Computer activation is definitely enabled.

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:

Update history for Office 365 ProPlus (listed by date) | Microsoft Docs

I would appreciate any help on this. My next step is to open a case with VMware if I can't get it resolved. Thank you!!

[techguy129]

Have you followed this guide step by step?

Best Practices for Delivering Microsoft Office 365 in VMware Horizon 7 | VMware

We have office 365 locally installed in our gold image. We are on build: Version 1803 (Build 9126.2259). So far no issues with account errors. We do not capture the credentials path you listed with UEM and login is persistent.

[blue_calx]

Yes I have followed that guide. Are you using Azure SSO or just password syncing?

[techguy129]

We use ADFS

[blue_calx]

We are not using ADFS so that is why that path needs to be captured by UEM.