Forum Discussion

Michael Sovitzky-Reinders's avatar
Michael Sovitzky-Reinders
Brass Contributor
Jul 19, 2021

Windows Server 2022 - KMS Activation yet?

I noticed Friday on my company's VLSC site that there are now MAK and KMS keys for WS2022. I have confirmed that I can now activate 2022 with a MAK key, volume license.

 

However, I'm unable to activate it via our KMS server. I found the KMS key on our VLSC site:

 

Windows Srv 2022 DataCtr/Std KMS
XXXXX-XXXXX-XXXXX-XXXXX-KQDWV
KMS

(Masked for privacy)

 

I used these commands on our KMS server (running WS2016):

 

slmgr.vbs /ipk KMS key

slmgr.vbs /ato

Both commands were successful. When I type slmgr.vbs /dlv all, I see this entry:

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=Retail
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)

 

This all appears normal.

 

Does anyone know why WS2022 won't activate yet? This is what I get on my WS2022 systems:

 

Something prevented us from communicating with our activation servers. Wait a few minutes and then try again. Error code: 0x87E10BC6

 

I can even enter this command on the 2022 system to manually tell it to use our KMS server (Yes, I joined the 2022 system to our AD domain)

 

slmgr.vbs -skms ourkmsserver.domain.name

 

That works, but when I try:

 

slmgr.vbs /ato

 

It gives essentially the same error.

 

Does anyone know if these keys are simply too new? Might there be a patch or MCU required on older Windows Server O/Ss to be able to activate newer versions? I know there was a patch back in the day that 2012 R2 KMS servers needed to install before they could successfully activate 2016 servers.

 

Thank you for any info you may have!

 

- Michael

General
management
  • Sue1998's avatar
    Sue1998
    Brass Contributor
    Oct 09, 2022
    The KMS activation is only for 180 days, after 180 days, you need to activate it again , it is troublesome, and if you find a KMS key online , it has as risk of black screen if the key is blocked !
    I get the retail server 2022 datacenter product key from the Microsoft partner online store keyingo.com, and it is easier to activate with the retail key, and you wont have any problems in the future too
  • Mary Hoffman's avatar
    Mary Hoffman
    Icon for Microsoft rankMicrosoft
    Aug 31, 2021
    If the price is too good to be true, it should be suspect. getsoftwarekey.com is not a Microsoft partner and they do not sell legitimate Microsoft product keys. Further, you run the risk of identity theft and credit card abuse.
  • abbodi1406's avatar
    abbodi1406
    Steel Contributor
    Jul 23, 2021

    Michael Sovitzky-Reinders 
    Server 2016 and 2019 got the KMS 2022 support with May 2021 updates, otherwise, you would not be able to install the key

    Update to extend KMS support for Windows Server 2022 LTSC

     

    maybe they didn't open the activation servers globally for 2022 CSVLK yet
    you could try:
    - change your current region to United States
    - or reboot and try again
    - or refresh the licensing store

    wmic path SoftwareLicensingService where __CLASS='SoftwareLicensingService' call RefreshLicenseStatus
      • Michael Sovitzky-Reinders's avatar
        Michael Sovitzky-Reinders
        Brass Contributor
        Aug 23, 2021

        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

Resources