Server 2019 KMS Host and VAMT doesn't like Server 2019 KMS Keys

Hi,

We have a 2019 KMS Host and no matter how I try, VAMT doesn't like the CSVLK or GVLKs for Server 2019.

VAMT just says Unsupported Key, which means Server 2019 KMS Clients have no client key to use for activation.

Anyone else experienced this? VAMT is from latest ASK and 2019 KMS Host server is fully patched.

Thanks

Thanks for the reply

I've seen those ones - and did manage to add the CSVLK using slmgr.vbs

However the bigger problem is that I can't even add the GVLKs either. Same error in VAMT. And because the KMS Host Server is 2019 Standard, I can only add the GVLK for Standard Edition using slmgr.vbs, it doesn't accept the Datacenter GVLK.

ldoodle said:

Thanks for the reply

I've seen those ones - and did manage to add the CSVLK using slmgr.vbs

However the bigger problem is that I can't even add the GVLKs either. Same error in VAMT. And because the KMS Host Server is 2019 Standard, I can only add the GVLK for Standard Edition using slmgr.vbs, it doesn't accept the Datacenter GVLK.

Hi there
Load of documentation here from the Ms site might be of some help.

Seems as if the Ms documentation might (actually for once !!) be of some use here :

https://docs.microsoft.com/en-us/win...ctivation-keys

https://docs.microsoft.com/en-us/win...n/install-vamt

https://docs.microsoft.com/en-us/win...ivation-client

cheers
jimbo

Seen on those too!

None of the 2019 Keys listed work in VAMT, this is my problem! So Server 2019 Client OS cannot activate against the new KMS Host.



The first one in this list is Windows 10 2015 LTSC.





- - - Updated - - -

Clearly there is a massive bug in VAMT because I've tried earlier versions with the same problem.

2019 GVLKs just don't work. Is there another way I can add GVLKs to the KMS Host?

See if any of these links are useful:

https://docs.microsoft.com/en-us/win...t-step-by-step

https://docs.microsoft.com/en-us/win...ctivation-vamt

Thanks. As I say the problem is since there is no GVLK (KMS Client Key) clients will not be given a key to activate with in the first place.

My environment is hundreds of servers so I don't really fancy installing the GVLK per server (which does work by the way using the GVLK given on the Microsoft page).

In VAMT, I can't even right click a computer > Install product key because there is no GVLK for Server 2019. Because there is no GVLK to install, activation fails.