Verify that the client and KMS host can communicate.

Did the KMS host log a request from the client computer? Verify that the name of the KMS client computer is listed.

Check this event for the following information:

On the KMS host computer, look in the KMS event log for event ID 12290. If the client is running a non-Microsoft firewall, does the outbound port have to be configured?.Is the KMS host name in the event correct?.Is the result code 0? Anything else is an error.On the KMS client computer, look in the Application event log for event ID 12289. For more information about KMS requirements, see the Volume Activation Planning Guide. Windows Server 2008 R2 KMS clients require a KMS count of 5 for activation. Until the KMS host has a count of 25, Windows 7 client computers cannot be activated. On the KMS host computer, run Slmgr.vbs and use the /dli command-line option to determine the host’s current count. Verify that the KMS activation threshold is met. The KMS client computer does not activate Alternatively, run Slmgr.vbs and use the the /dli command-line option. On the KMS client computer, open the System control panel, and look for the Windows is activated message.

If you use System Center Operations Manager, the System Center Data Warehouse database stores event log data for reporting, therefore you do not have to back up the event logs separately. If you use the event log to track or document KMS activations, periodically export the Key Management Service event log from the Applications and Services Logs folder of Event Viewer. However, if you use a tool to routinely clean up event logs, the activation history stored in the logs can be lost. Should I back up KMS host information?īackup is not required for KMS hosts. If you suspect that your issue is related to DNS, see Common troubleshooting procedures for KMS and DNS issues.

Ms office activation failed