Forum Discussion
Windows Server 2022 - KMS Activation yet?
Microsoft
olsookie
No, nothing yet. My org's KMS server and this server are both patched up to Aug 2021 patches. After a reboot, it still won't activate. Issuing 'slmgr.vbs /ato' also returns the error code immediately.
I would imagine (trust) Microsoft will have another post when this is fully live. Also, a post, of some sort, about the issuing of official ISO media (which they did 8/18) to VLSC and VS Subscriber Downloads.
My hunch is that they'll reveal GA happening 9/16/21 at their Windows Summit. Just 3 weeks to go, I guess... 😉
- Michael
- Michael Sovitzky-Reinders : Will it work on Windows server 2012 R2. If we need to upgrade then what are the minimum version of Server it require to configure KMS key for Windows 2022.
There are 2 possible questions you're asking. I will assume one of them is:
If we enter the new WS2022 KMS key on our recent KMS Server, will this activate a (client) server running WS2012R2?Yes, if you have a KMS Server running WS2022, it will activate other WS2022 clients, and all prior, supported versions of Windows Server/Windows 10, etc.
If our KMS Server is running WS2012R2, is it supported to enter a WS2022 key to activate WS2022 clients?
No, it doesn't look like it. It would appear your KMS Server needs to be either 2016, 2019, or 2022 to be able to activate 2022 servers.
https://support.microsoft.com/en-us/topic/kb5003478-update-to-extend-kms-support-for-windows-server-2022-ltsc-5ae389ab-7650-46a7-ad53-bc7653684dfc
Please let me know if this answers your question.
- Michael
- oyoussuf instead of KMS please consider to use ADBA / Active Directory based activation. It is much simpler. You can optionally use VAMT 3 to create reports / manage activations or preinstall the generic keys
In Domain Joined scenarios I would not use KMS servers anymore. Some of my customers have no KMS anymore when they have only 2012R2 or newer and Office 2013 or newer.
Michael Sovitzky-Reinders While it is true that your KMS server should be updated with the latest cumulative updates, it also needs to be updated with the Windows Server 2022 CSVLK which you obtain from the Volume Licensing program.
- Mary Hoffman
I already have applied and activated that key. Here is an excerpt from my original post:
Name: Windows(R), ServerDatacenter edition
Description: Windows(R) Operating System, VOLUME_KMS_WS22 channel
Activation ID: ---
Application ID: ---
Extended PID: 03612-04573-000-204477-03-1033-14393.0000-1972021
Product Key Channel: Volume:CSVLK
Installation ID: ---
Use License URL: https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Ret...
Validation URL: https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx
Partial Product Key: KQDWV
License Status: Licensed
Remaining Windows rearm count: 1000
Remaining SKU rearm count: 1001
Trusted time: 7/19/2021 7:39:34 AM
Key Management Service is enabled on this machine
Current count: 50
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
(Items masked for privacy)
That tells me it is licensed, with a CSVLK key, and should activate WS2022 servers. Do you have any other idea why this isn't working? Thank you.
- MichaelI read some more online and made some progress. I ran these 3 lines:
slmgr.vbs /upk (uninstall current product key)
slmgr.vbs /ipk [Windows Server 2022 KMS client setup key]
slmgr.vbs /ato
This worked!
Now, I don't know why this took these unnecessary steps...I'll have to build out another test instance of WS2022, join it to our domain and see if it auto activates like it should within 1 reboot of Install.
I'll update this post when I have more news.
You can find the KMS client setup key here:
https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys
Thank you!
