Activation with KMS with other domain not working

2

On standalone computers for which I want to activate the Windows 2016 and 2019 license I have set the KMS domain with:

slmgr.vbs -skms-domain DomainFQDN

When I type, on the computer which I want to activate, the following command line, it returns correctly the two KMS servers.

nslookup -type=all _vlmcs._tcp.DomainFQDN

The server accepts the license key with slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.

However, during the activation process with slmgr.vbs -ato I get the following error message:

Error: 0x80072EE2

The network trace shows:

  • that the computer does not request the DNS to find KMS servers on the registered domain
  • the computer requests the DNS for activation-v2.sls.microsoft.com

Did I miss something or am I doing something wrong?

windows
domain
activation
kms
asked on Server Fault May 26, 2019 by Luke • edited May 28, 2019 by Luke

1 Answer

4

Windows will only use KMS for activation if the appropriate KMS client setup key for your operating system is installed. There is a single KMS client setup key for each version of Windows that is used by all KMS clients, worldwide, that are running that version. It is not specific to your organization.

The appropriate KMS client license key will be preinstalled by default on volume editions of Windows, but if you have installed any other license key (such as a MAK key) then Windows will attempt to activate against Microsoft's servers rather than using KMS.

The other common mistake is to install the KMS key your organization was given. Doing this turns the computer into a KMS server rather than a KMS client.

You can use slmgr /dlvor slmgr /dli to find the key type. If the computer is correctly configured to be a KMS client, then the "Description" field will refer to the VOLUME_KMSCLIENT channel and the "Product Key Channel" will be Volume:GVLK.

If the wrong key is installed, use slmgr /ipk to reinstall the appropriate setup key from the list provided at the link above and then try activation again.

answered on Server Fault May 27, 2019 by Harry Johnston • edited May 29, 2019 by Harry Johnston

User contributions licensed under CC BY-SA 3.0