Today I helped a colleague troubleshoot a couple of systems were unable to activate using Key Management Service (KMS). Basically for this situation it boiled down to this:
Determine for the KMS service
- Which server is hosting the KMS service.If an SRV record has been added for KMS DNS auto discovery, run from CMD: nslookup -type=srv _vlmcs._tcp
- If the server hosting the KMS is functioning correctly:
- Check if the server is up and running.
- Check if the “Software Protection” service (sppsvc) is running.
- Verify if the KMS service is listening on port 1688: telnet localhost 1688
- Verify the KMS status. Run from CMD: slmgr.vbs /dli
- Verify if a KMS key is installed and activated.
- Verify if the minimum threshold for activation is being met.
- Verify if other clients are able to activate using KMS. Even though the output of “slmgr.vbs /dli” gives you an indication, you can use the “Volume Activation Management Tool” (VAMT) for more insight and functionality.
- Verify that a VLK key is being used.
For clients that are not able to activate
- Verify if the correct KMS server can be resolved correctly:
nslookup -type=srv _vlmcs._tcp - Verify if the KMS can be contacted:
telnet <KMS FQDN or IP> 1688- If this is not the case, perform a traceroute to determine potential causes. Reasons could include:
- No default gateway configured on the client to reach the KMS.
- No route configured on the client to reach the KMS.
- Firewall on the client is blocking the traffic.
- Firewall on the server is blocking the traffic.
- If it is a VM, the virtual network might be misconfigured.
- Routing on the network is not correct.
- Firewall on the network is blocking traffic.
- If this is not the case, perform a traceroute to determine potential causes. Reasons could include:
- Clear any previous (mis)configuration: slmgr.vbs /ckms
- Attempt activation: slmgr.vbs /ckms
NOTE: If you have lots of systems where you need to clear configuration and then attempt activation, you can also perform slmgr.vbs on remote computers using:
slmgr.vbs TargetComputerName [username] [password] /parameter [options]
Additional information
If you haven’t been able to resolve the issue, you might want to take a look here:
- Understanding KMS
- How to troubleshoot the Key Management Service (KMS)
- Deploying KMS activation
- How to discover Office and Windows KMS hosts via DNS and remove unauthorized instances
- Volume Activation Operations Guide
- Configuring KMS hosts
- Slmgr.vbs options
- Reporting Activation Information Using Volume Activation Management Tool 2.0
blog.bjornhouben.com 