locked
unable to activate windows server 2019 standard with KMS server hosted on windows server 2012 R2. RRS feed

  • Question

  • Hi, i'm having problem activating windows server 2019 volume license version with my KMS server. My KMS server is hosted on a windows server 2012 R2 and currently activating windows 10, windows server 2012 R2 and 2016 ok without any issue. but when i try to activate windows server 2019, i get the following error.


    Friday, December 28, 2018 2:48 AM

Answers

  • Issue resolved by performing the steps below in sequence.

    1) Slmgr /upk

    2) Restart the KMS server  (Very important) do not ipk without reboot.

    3) Slmgr /ipk "the volume license key"

    4) Slmgr /ato to activate.


    • Marked as answer by aloysiustan79 Wednesday, January 23, 2019 2:46 AM
    • Edited by aloysiustan79 Wednesday, January 23, 2019 2:46 AM
    Wednesday, January 23, 2019 2:46 AM

All replies

  • Looks like Server 2019 client KMS cannot be hosted on Server 2012

    https://docs.microsoft.com/en-us/windows-server/get-started-19/activation-19

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Friday, December 28, 2018 3:50 AM
  • Hi Dave,

    Sorry it was mistake. The KMS is hosted on a windows server 2012 R2 which is supported.

    Friday, December 28, 2018 6:16 AM
  • I'd check that 2012 R2 has the mentioned updates or as a work-around try other activation options such as;

    slmgr /ipk #####-#####-#####-#####-#####

    slmgr /ato

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Proposed as answer by Dave PatrickMVP Wednesday, January 23, 2019 2:47 AM
    Friday, December 28, 2018 1:09 PM
  • Hi,

    KMS Activation for Windows Server 2019 can be run from Windows Server 2012 R2 with the appropriate prerequisites: 

    July 2016 Servicing Stack Update: KB3173424 

    November 27, 2018 Preview of Monthly Rollup: KB4467695

    Note: the most recent Cumulative Update will include these changes as well.  They were originally introduced in KB4343891. 

    More information, you can refer to the following link:

    KMS Activation in Windows Server 2019

    https://blogs.technet.microsoft.com/askpfeplat/2018/10/08/kms-activation-in-windows-server-2019/

    Hope it could be helpful.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 31, 2018 2:25 AM
  • Hi, Since my KMS box is activating windows 2012 R2, 2016 without any issue, I presumed that my KMS server already have July 2016 service stack update installed. As for KB4467695, my lastest CU is KB4483187 installed on 21/12/2018 so the Nov 27 2018 KB4467695 should be included as well.

    Wednesday, January 2, 2019 4:08 AM
  • Any have successfully activated Windows server 2016 with KMS hosted on windows server 2012 R2?
    Thursday, January 3, 2019 6:43 AM
  • Also having this very same error.

    Have KMS Key installed using AD KMS on a windows server 2016 domain controller.

    Getting the same error as OP.

    Server 2016 is running latest CU.  Windows 10 and Windows Server 2016 are able to AD Activate.  No 2019 server is able to at this time.  I have verified that the server 2019 kms key is installed.

    Windows Server 2016 May 2018 Servicing Stack Update: KB4132216 
    November 27, 2018 Cumulative Update: KB4467681

    *Note* – You can install any future Windows Server 2016 Cumulative update and get these fixes.  Most Organizations would have installed KB4457131 as part of their patching process.  All fixes for Windows Server 2016 are cumulative. 

    Tuesday, January 22, 2019 4:21 PM
  • Issue resolved by performing the steps below in sequence.

    1) Slmgr /upk

    2) Restart the KMS server  (Very important) do not ipk without reboot.

    3) Slmgr /ipk "the volume license key"

    4) Slmgr /ato to activate.


    • Marked as answer by aloysiustan79 Wednesday, January 23, 2019 2:46 AM
    • Edited by aloysiustan79 Wednesday, January 23, 2019 2:46 AM
    Wednesday, January 23, 2019 2:46 AM
  • Glad to hear it works, can you please also mark my answer?

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, January 23, 2019 2:48 AM
  • Windows Server 2012 R2

    July 2016 Servicing Stack Update: KB3173424

    September 11, 2018 Cumulative Update: KB4457129

    Note – If you’re reading this after a subsequent Patch Tuesday, the most recent Cumulative Update will include these changes as well. They were originally introduced in KB4343891.

    Windows Server 2016

    May 2018 Servicing Stack Update: KB4132216

    August 30, 2018 Cumulative Update: KB4343884

    Note – You can install any future Windows Server 2016 Cumulative update and get these fixes. Most Organizations would have installed KB4457131 as part of their patching process. All fixes for Windows Server 2016 are cumulative.

    • Proposed as answer by Sergey O O Friday, February 15, 2019 10:15 AM
    Friday, February 15, 2019 10:14 AM