KMS and Windows Server 2019 - activation of old OSes

Iron Contributor

Hello,
I would like to 'prepare' our KMS to activate Windows Server 2019.
I took a look at this page https://docs.microsoft.com/en-us/windows-server/get-started-19/activation-19 and noticed that the Volume License for Windows Server 2019 doesn't activate Server 2008 R2 or windows 7 anymore.
At the moment our KMS has the 2016 Volume License key and using 'slmgr /dlv all' I can see this :

 

Name: Windows(R), ServerStandard edition
Description: Windows(R) Operating System, VOLUME_KMS_WS16 channel
Partial Product Key: ....
License Status: Licensed

 

Name: Windows(R), ServerStandard edition
Description: Windows(R) Operating System, VOLUME_KMS_2012-R2_WIN10 channel
This license is not in use.
License Status: Unlicensed

 

Name: Windows(R), ServerStandard edition
Description: Windows(R) Operating System, VOLUME_KMS_WS12_R2 channel
This license is not in use.
License Status: Unlicensed

 

The key before that was used was the 2012 R2 for Windows 10
I understand that this key is not used anymore as the 2016 one was ok for all the OSes supported by the 2012 R2 one.
But now, what will happen when I register the 2019 one ?
I want to be sure that 2008 servers and windows 7 machines are still activated.

Am I right to assume that the 2016 key will remain 'active' even after registering the 2019 one ?

 

Thanks in advance for your help.

Marc

3 Replies

I have the same question.  I have not been able to find an answer in any of the documentation I've been able to locate so far.

I am running KMS from Windows Server 2016 Standard.   

Ours also shows Description: Windows(R) Operating System, VOLUME_KMS_WS16 channel and currently services all previous OSs including Windows 7.

The documentation found on https://docs.microsoft.com/en-us/windows-server/get-started-19/activation-19 indicates that once the 2019 key is added, there will not be support for Windows 7.

Will adding the new key "stack" or will it replace the existing? 

 

Thanks in advance. 

Ken

 

Hello Ken,

 

Apparently Microsoft did change the documentation and it is now stated that the Server 2019 key supports activating Windows 7 machines.

So, everything should be ok. (I hope 🙂 )

 

Marc

 

i found the issue it turns out that update kb971033 has something to do with this issue. here is how you fix it 

 

run this from an elevated command prompt:

 

wusa /uninstall /kb:971033
net stop sppuinotify
sc config sppuinotify start= disabled
net stop sppsvc
del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah
del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah
del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat
net start sppsvc
cscript c:\windows\system32\slmgr.vbs /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 <---win 7 kms key
cscript c:\windows\system32\slmgr.vbs /ato
sc config sppuinotify start= demand