Forum Discussion
Windows Server 2022 - KMS Activation yet?
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 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!
- Well, I don't know what changed, but I built a new WS2022 VM, joined it to our AD domain, and it KMS activated. Very nice. We're finally here!