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-ReindersSep 23, 2021Brass Contributor
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
- kwester-ebbinghaus-businessSep 24, 2021Iron Contributoroyoussuf 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.