VHLK Product Key for Windows Server 2019 Datacenter not working.

David F 41 Reputation points
2023-01-05T21:11:02.993+00:00

I've installed the VHLK - I'd like to apply a key to it. From product key portal I created a key from datacenter 1809 (Server 2016), since the winver reports 1809. It didn't like it, so then created one for datacenter 1903 (Sever 2019), still doesn't like it. What option from the portal should I use to generate a key to keep the VHLK working beyond 180 days?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,113 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426.1K Reputation points MVP
    2023-01-05T21:20:33.847+00:00

    created a key from datacenter 1809 (Server 2016), since the winver reports 1809. It didn't like it, so then created one for datacenter 1903 (Sever 2019),

    1809 == Server 2019 (gui or core) long term servicing channel, version, not Server 2016
    1903 == was a semiannual channel core only version of Server 2019

    You cannot use a volume key to activate the evaluation directly. Either download the install media from volume center or the other option is two step. As a work around , you can use a kms key as intermediary step.

    Dism /online /Set-Edition:ServerDataCenter /ProductKey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /AcceptEula  
    

    https://learn.microsoft.com/en-us/windows-server/get-started/kmsclientkeys#windows-server-ltscltsb-versions

    then if successful use your own volume product key below after reboot

    slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx  
    slmgr /ato  
    

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. David F 41 Reputation points
    2023-01-05T21:37:06.073+00:00

    Hey DSPatrick, thanks for the info. I have a couple more clarifications...

    1 - In the VS Subscriptions / Product keys it shows Server 2016 so it was a bit confusing to me. See attached.

    2 - The VHLK shows it's using the datacenter version but you referenced the standard edition. If I download the OS installation, do I install over the top of the existing installation (will that break the VHLK configuration that you guys setup?).

    3 - Are you saying all I need to do if I like is to type in: Dism /online /Set-Edition:ServerStandard /ProductKey:N69G4-B89J2-4G8F4-WWYCC-J464C /AcceptEula then type in the code generated for me in the subscripts portal? That seems easier than trying to reinstall.

    Thanks.

    276677-20230105-133252.png

    0 comments No comments

  2. Dave Patrick 426.1K Reputation points MVP
    2023-01-05T22:31:30.667+00:00

    3-

    Yes, that's correct assuming Server 2019 DataCenter. If the OS is something different then find to correct KMS product key here. Also check the edition is correct, either ServerDataCenter or ServerStandard
    https://learn.microsoft.com/en-us/windows-server/get-started/kmsclientkeys#windows-server-ltscltsb-versions

    then if successful use your own volume product key below after reboot

     slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx  
     slmgr /ato  
    

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  3. David F 41 Reputation points
    2023-01-05T23:23:11.027+00:00

    I don't understand what I did, but it worked. thanks.