KMS 2016 and Windows 7

[Sagima]

Adding the Server 2016 KMS key to my 2016 KMS server resulted in a so far irreversible windows 7 not genuine warning on my windows 7 machines that called in before I noticed it.

 

Similar to the problem described in this forum posting:

 

https://social.technet.microsoft.com/Forums/en-US/98d40290-8dc3-4abe-89d0-36cf8c2971e0/windows-10-enterprise-kms-host-renders-windows-7-enterprise-kms-clients-not-genuine-?forum=win10itprosecurity

 

but obviously I used a 2016 kms server not a windows 10 one.

Our newest technician has been assigned the fun job of finishing off the windows 7 migration asap now (we had done about 75% of our windows computers over the last 6 months) - he was to have it done by the end of the year

 

In our case re-arming doesn't work

 

I would have to recommend using KMS only for windows 7/2008r2 and Office and using Active Directory activation for Windows 10/2016 if you have a mixed environment in case you fall victim too.