Rearming Office 2016 Is there a better way to deploy Non Persistent Linked Clones?

[Jeostang]

I deploy 160 VMs that are non persistent linked clones. They are all linked to a golden master. The master has office 2016 installed. I've rearmed once and can't rearm anymore. (I guess because 30 days have passed.) I update the master every month. Most of the time office does not have a client ID (shows none), this time office updated and there is a client ID that I can't clear so I'm not able to push this master out since all 160 machines will have the same client ID and our KMS won't license them like that. Is there a better way I should be doing this when I update my master? Right now I'm going to go back to a earlier snapshot and hope the client ID is clear. Is there anyway to gain more rearms?


Thanks

Continue reading...