KMS Server 2016 - doesn't accept Server 2019 CSVLK or GVLK

Question

KMS Server 2016 - doesn't accept Server 2019 CSVLK or GVLK

Lanky Doodle 161

Hi,

I have a 2016 KMS Server and I am trying to add my CSVLK Host Key and the GVLK for Server 2019. None of them work, either in VAMT or SLMGR.VBS. Get "unsupported key" in VAMT and something about "Server Core" in SLMGR.VBS. I'm not using Server Core.

The Server has latest SSU and January 2022 CU, which I read is the main cause of this issue (Server 2016 not being updated enough).

What am I missing?

Thanks

Lanky Doodle 161 Reputation points

2022-02-08T18:59:33.777+00:00

I have downloaded the "latest" ADK from here https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install and installed only the VAMT component.

By "latest", I mean the Windows 11 one, based on this note: "If your environment has a mix of Windows versions, use the ADK version that matches the latest operating system in your environment."

Weirdly the Server 2022 CSVLK and GVLKs are perfectly fine!
Lanky Doodle 161 Reputation points

2022-02-08T20:35:57.88+00:00

I have now managed to add the 2019 KMS Host key to the KMS Server with slmgr.vbs. Don't know why it wasn't working earlier. But I still cannot add the GVLK.

However the GVLK for Server 2019 can be manually added to a Server 2019 KMS client with slmgr.vbs, and then successfully activates against the 2016 KMS Server. This isn't ideal as I have hundreds of Servers in my estate so was hoping to be able to add them all in the VAMT > select them all > Update product information > right click again > add product key > automatically choose a GVLK.

But that process from VAMT fails because it cannot find a suitable key, because the GVLK is not there.

Lanky Doodle 161 Reputation points

2022-02-08T18:59:33.777+00:00

I have downloaded the "latest" ADK from here https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install and installed only the VAMT component.

By "latest", I mean the Windows 11 one, based on this note: "If your environment has a mix of Windows versions, use the ADK version that matches the latest operating system in your environment."

Weirdly the Server 2022 CSVLK and GVLKs are perfectly fine!
Lanky Doodle 161 Reputation points

2022-02-08T20:35:57.88+00:00

I have now managed to add the 2019 KMS Host key to the KMS Server with slmgr.vbs. Don't know why it wasn't working earlier. But I still cannot add the GVLK.

However the GVLK for Server 2019 can be manually added to a Server 2019 KMS client with slmgr.vbs, and then successfully activates against the 2016 KMS Server. This isn't ideal as I have hundreds of Servers in my estate so was hoping to be able to add them all in the VAMT > select them all > Update product information > right click again > add product key > automatically choose a GVLK.

But that process from VAMT fails because it cannot find a suitable key, because the GVLK is not there.

Answer 1

Limitless Technology 37,646

Hello Lanky Doodle,

It would help if you can post the specific error. Also have you confirmed that the CSVLK you have installed on the 2016 server is valid to activate Windows Server 2019? Also, please ensure that the KMS Host is fully updated.

Other relevant information about KMS deployments can be found here: https://learn.microsoft.com/en-us/windows-server/get-started/kms-activation-planning

-------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept as answer--

Lanky Doodle 161 Reputation points

2022-02-09T14:51:13.233+00:00

Hi,

Thanks for the reply.

This 2016 KMS server is updated to January 2022 CU. Just to confirm, I'm having trouble adding the GVLKs to VAMT, not the CSVLK (I had to add the 2019 ones via slmgr.vbs).

This is the error in VAMT:

You can see 3 keys in the GUI. The first one is Windows 10 Enterprise LTSC 2015 and the second and third keys are the Server 2019 ones. None of these 3 can be added:

As mentioned, I have added the Server 2022 GVLK.
Lanky Doodle 161 Reputation points

2022-02-11T18:35:26.867+00:00

Any ideas anyone?
Lanky Doodle 161 Reputation points

2022-02-14T17:24:42.943+00:00

Any ideas?

This is the error I actually get when trying to install a product key from VAMT:

Should not be this hard in this day and age to import a ****ing product key from Microsoft, to Microsoft.
Lanky Doodle 161 Reputation points

2022-02-20T18:02:06.677+00:00

OK, so I have built a Server 2019 KMS Host and even this one doesn't accept the 2019 GVLK keys.

Thankfully I found a load of pirated keys online so I'm all good now.

Way to go Microsoft for not allowing your customers to use your own keys!

KMS Server 2016 - doesn't accept Server 2019 CSVLK or GVLK

1 answer

Activity