Environment: ESXI 6.7, Horizon 7.13.1, DEM 9.9.0.905, Windows 10 21H2, Microsoft 365 (Shared Computer Activation), Teams Machine-wide Install. 4 Pools that share the same golden image and current snapshot.
So we have a GPO in place for Office Shared Computer Activation that automatically activates Microsoft 365 and configures an Outlook profile for a new user the first time they log into the VDI. This GPO does this without any prompts to the user. When all is working as it should this GPO has zero issues.
However, sometimes (maybe 50%), when we publish a new snapshot to a pool, and log into the new clone, we notice is Teams does not automatically sign the user in. If Teams does not auto sign in a user, then that's the red flag that let's us know the Office GPO is broken (for some reason they go hand and hand). Thus, a new user that signs into the pool will get all the prompts for manual Office activation. And even if the user goes through all the prompts to complete activation, it still fails stating that Office is unlicensed.
To fix this problem what we have to do is disable provisioning in the affected pool, select all the machines and remove them so there are zero available, then re-enable provisioning to let it recreate all the machines. Then, if we log into the pool Teams will auto sign in as it should, and the Office GPO works for new users. That's the problem and fix in a nutshell, however sometimes it's a bit more complicated.
Occasionally we have to disable provisioning and delete/recreate machines in a different pool that shares the same golden image, as sometimes publishing a new snapshot in Pool A causes the broken Office behavior in Pool B, even though Pool B was previously working. Therefore, if we publish a snapshot in one pool, we essentially have to log into all other pools that share that same golden image make sure we see Teams auto sign in the user. If Teams launches as expected, great! However If one or more pools are broken, which can be easily identified by Teams not auto signing in at login, then we have to start the process of deleting the machines in those pools and let them recreate, then sign in to make sure it's fixed.
When everything is working, it stays working until we publish a new snapshot. When it's broken, it will stay broken and it seemingly ignores any GPO changes we make until we take the steps above to fix the broken pool, and once we do that then everything start working again. Has anyone seen similar behavior or have any ideas as to what may be the underlying issue?
