Why is my KMS not working?
Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Guidelines for troubleshooting the Key Management Service (KMS)
In this articleAs part of their deployment process, many enterprise customers set up the Key Management Service (KMS) to enable activation of Windows in their environment. It is a simple process to set up the KMS host, after which the KMS clients discover the host and try to activate on their own. But what happens if that process doesn’t work? What do you do next? This article walks you through the resources that you require in order to troubleshoot the issue. For more information about event log entries and the Slmgr.vbs script, see Volume Activation Technical Reference. KMS overviewLet’s start with a quick refresher on KMS activation. KMS is a client-server model. Conceptually, it resembles DHCP. Instead of handing out IP addresses to clients on their request, KMS enables product activation. KMS is also a renewal model, in which the clients try to reactivate on a regular interval. There are two roles: the KMS host and the KMS client.
From a troubleshooting perspective, you may have to look at both sides (host and client) to determine what is going on. KMS hostThere are two areas to examine on the KMS host. First, check the status of the host software license service. Second, check the Event Viewer for events that are related to licensing or activation. Slmgr.vbs and the Software Licensing serviceTo see verbose output from the Software Licensing service, open an elevated Command Prompt window and enter slmgr.vbs /dlv at the command prompt. The following screenshot shows the results of this command on one of our KMS hosts within Microsoft. The most important fields for troubleshooting are the following. What you are looking for may differ, depending on the issue to be solved.
We often get asked about the “cumulative requests” section of the slmgr.vbs /dlv output. Generally this data is not helpful for troubleshooting. The KMS host keeps an ongoing record of the state of each KMS client that tries to activate or reactivate. Failed requests indicate KMS clients that the KMS host does not support. For example, if a Windows 7 KMS client tries to activate against a KMS host that was activated by using a Windows Vista KMS key, the activation fails. The “Requests with License Status” lines describe all the possible license states, past and present. From a troubleshooting perspective, this data is relevant only if the count is not increasing as expected. In that case, you should see the number of failed requests increasing. This indicates that you should check the product key that was used to activate the KMS host system. Also, notice that the cumulative request values reset only if you reinstall the KMS host system. Useful KMS host eventsEvent ID 12290The KMS host logs Event ID 12290 when a KMS client contacts the host in order to activate. Event ID 12290 provides a significant amount of information that you can use to figure out what kind of client contacted the host and why a failure occurred. The following segment of an event ID 12290 entry comes from the Key Management Service event log of our KMS host. The event details include the following information:
If you are troubleshooting a client and cannot find a corresponding event ID 12290 on the KMS host, that client is not connecting to the KMS host. Some reasons why an event ID 12290 entry may not exist are as follows:
KMS clients log two corresponding events, event ID 12288 and event ID 12289. For information about these events, see the KMS client section. Event ID 12293Another relevant event to look for on your KMS host is event ID 12293. This event indicates that the host did not publish the required records in DNS. This situation is known to cause failures, and it is something that you should verify after you set up your host and before you deploy clients. For more information about DNS issues, see Common troubleshooting procedures for KMS and DNS issues. KMS clientOn the clients you use the same tools (Slmgr and Event Viewer) to troubleshoot activation. Slmgr.vbs and the Software Licensing serviceTo see verbose output from the Software Licensing service, open an elevated Command Prompt window and enter slmgr.vbs /dlv at the command prompt. The following screenshot shows the results of this command on one of our KMS hosts within Microsoft. The following list includes the most important fields for troubleshooting. What you are looking for may differ, depending on the issue to be solved.
Useful KMS client eventsEvent ID 12288 and Event ID 12289When a KMS client successfully activates or reactivates, the client logs two events: event ID 12288 and event ID 12289. The following segment of an event ID 12288 entry comes from the Key Management Service event log of our KMS client. If you see only event ID 12288 (without a corresponding event ID 12289), this means that the KMS client was not able to reach the KMS host, the KMS host did not respond, or the client did not receive the response. In this case, verify that the KMS host is discoverable and that the KMS clients can contact it. The most relevant information in event ID 12288 is the data in the Info section. For example, this section shows the current state of the client plus the FQDN and TCP port that the client used when it tried to activate. You can use the FQDN to troubleshoot cases in which the count on a KMS host is not increasing. For example, if there are too many KMS hosts available to the clients (either legitimate or rogue systems) then the count may be distributed over all of them. An unsuccessful activation does not always mean that the client has 12288 and not 12289. A failed activation or reactivation may also have both events. In this case, you have to examine the second event to verify the reason for the failure. The Info section of event ID 12289 provides the following information:
What does support ask for?If you have to call Support to troubleshoot activation, the Support Engineer typically asks for the following information:
Additional References
FeedbackSubmit and view feedback for How do I force KMS activation?Open an elevated command prompt and run one of the following commands:. To install the KMS key, type slmgr. vbs /ipk To activate online, type slmgr. vbs /ato .. To activate by telephone, follow these steps: Run slmgr. vbs /dti and confirm the installation ID.. How long does KMS take to activate?Any Windows client that configured to use 'KMS Client Channel' will be activated against the new KMS host automatically within 2 hours (as this is the 'KMS Activation Interval' default value).
How do I restart KMS service?Restart the Software Protection Service by running restart-service sppsvc in an elevated PowerShell console (or net stop sppsvc && net start sppsvc if PowerShell is unavailable). Run slmgr. vbs /dli to get the KMS activated client count.
How do I fix the connection to my KMS server failed?Make sure that Windows Update is enabled and your intenret connection is stable before running the batch files. To check if my KMS servers are blocked or not, please open your internet browser then try going to: http://kms8.msguides.com/. If the page is visible, it means this server is not blocked.
|