Tom,
Thank you for answering.
Le 21/12/2016 à 14:47, Tom Gamull a écrit :
Something is triggering the activation that windows is detecting as
a
change in hardware.
Our DCs are made of hosts from 3 different models, so chances are that
windows is detecting a different CPU ID or something (that is a pity, as
I thought all this was hidden to the guest)
I’ve not had this problem on 2012 or past versions,
It may be true that we only encountered these issues on 2008 R2 guests.
you’ll usually encounter it when changing the hardware drivers (such
as
converting from physical to virtual). Generally you want to install
compatible drivers (like the ovirt windows guest tools).
Every guests here is installed with oVirt guest tools.
Since then, we made no driver change, neither on hosts nor guests.
A good
practice though is to snapshot before you make a change such as drivers
in case you need to set the activation key.
For Desktops in VDI when you use a gold image, you generally make a
snapshot before activation - see here for an answer
-
https://social.technet.microsoft.com/Forums/en-US/25c4c85c-c8a9-4316-8bfa...
I'm not sure this was relevant.
what kind of activation keys are you using?
Further readings lead me to think that the kind of key IS the main
reason I'm facing this.
Do you have KMS server?
No. I was told to be very prudent with using KMS servers, so not planned.
--
Nicolas ECARNOT