[2004, 20h2] [20H2] Active-Directory Based Activation not working

[FragglePete]

I've had Active-Directory Based Activation for Windows 10, Server, etc running for a couple of years now with no issues - just seems to have work flawlessly - easy to setup once I've had the appropriate KMS key added to our agreement.

 

However, just been tinkering with our new 20H2 based image and noticed that the devices were showing 'Windows is not activated' - and shows the following error:

 

Windows reported that the hardware of your device has changed.

Error code: 0xC004F211

 

Which seems odd, as it's supposed to activate regardless if joined to the Domain - but no! I know in the past with KMS you've had to run various updates to the KMS server to get it to recognise newer versions of Windows, Server and Office, etc but couldn't see an update for AD Based Activation.

 

Just rebuilt another PC using our 2004 image and this activates ok.

 

Has anyone else using AD Based Activation and 20H2 images noticed this ? Or any ideas?

 

Thanks

 

Pete

[Davit2005]

I've had Active-Directory Based Activation for Windows 10, Server, etc running for a couple of years now with no issues - just seems to have work flawlessly - easy to setup once I've had the appropriate KMS key added to our agreement.

 

However, just been tinkering with our new 20H2 based image and noticed that the devices were showing 'Windows is not activated' - and shows the following error:

 

Windows reported that the hardware of your device has changed.

Error code: 0xC004F211

 

Which seems odd, as it's supposed to activate regardless if joined to the Domain - but no! I know in the past with KMS you've had to run various updates to the KMS server to get it to recognise newer versions of Windows, Server and Office, etc but couldn't see an update for AD Based Activation.

 

Just rebuilt another PC using our 2004 image and this activates ok.

 

Has anyone else using AD Based Activation and 20H2 images noticed this ? Or any ideas?

 

Thanks

 

Pete

 

Is this by doing a fresh install of 20H2 or an upgrade?

 

I would suggest speaking to MS but last time I spoke to the Volume licensing team about a query when we upgraded office they did not know what a KMS server was (or maybe could not bother raising the issue higher).