windows server 2019 kms activation not working

The following images show sample outputs: Volume:GVLK means the device uses to KMS activation, Volume:MAK means the device uses to MAK activation. Look for the Product Key Channel setting. To confirm the activation method set on the device, run the following command: slmgr -dlv If the device does not activate, the server might be set to MAK activation instead of KMS activation. Note: If you receive the error 0xC004F074 The Key Management Server (KMS) is unavailable,Ĭontinue with the following steps to ensure the server clock synchronizes with the KMS clock. Request activation from the KMS: slmgr.vbs /ato Set the KMS manually within the registry: slmgr.vbs /skms :1688 We recommend the followingĪrticle for help resolving the issue: Update ServiceNet routes on cloud Is an interface, hardware, or routing issue. Note: If there is a reply, continue to step 3. Then, right-click CommandĬonfirm that you can ping the Rackspace KMS server by running the following command: ping kms-server-from-table-above Log in to your cloud server as administrator by clicking Locate the appropriate KMS server in the following list: Data center Ensure that the Windows Server is configured to use the correct KMS server

Use the steps in the following sections to resolve this issue. The server’s clock differs from the KMS clock by more than four hours.

Also, you can't have the Active Directory role installed, it will prevent converting so have to remove the role, convert then reinstall the role.Problem: The Key Management Server (KMS) rejects periodic activation requests,Īnd the Microsoft® Windows® operating system shows as unlicensed.Ĭause: The two leading causes of this issue are: EVAL Standard Core installs can only be converted to Windows Server Datacenter Core which requires a Datacenter product key. Note: Windows Server Standard Core cannot be converted from EVAL. If customer is trying to activate VM and they are running Datacenter version of operating system on the host they can use AVMA keys for VMs but the AVMA keys will not work to convert from EVAL so we must use KMS key to convert then after it is converted update the VM with the AVMA key with this command. Substitute product key with product key on customer's COA sticker if available.ĭism /online /set-edition:ServerStandard /productkey:N69G4-B89J2-4G8F4-WWYCC-J464C /accepteula Example of command with Server 2019 KMS key.

Windows server 2019 kms activation not working