We are running:
Horizon 2006
Windows 10 20H2
Office 2019
AD Volume Activation for both Office and Windows
Instant Clones (deleted at log off)
We are running into a random issue with the instant clones where Office isn't activated when the user logs in. At first I thought something was wrong with AD Volume Activation, but then I realized that windows is activated so that's working.
The base image is on the domain for ease of software deployments. Is there something that should be done on the base image before creating a snapshot to ensure Office activates properly. I do this as part of the script before I take a snap to deactivate windows:
slmgr.vbs /ckms (This option removes the specified KMS host name, address, and port information from the registry and restores KMS auto-discovery behavior.)
slmgr.vbs /ckhc (This option disables KMS host caching. This setting instructs the client to use DNS auto-discovery each time it attempts KMS activation (recommended when using priority and weight).)
Is there something similar for Office that I can run to deactivate before taking the snap?
