KMS Idle Time Monitor Monitor

  • ID:  Microsoft.Windows.KeyManagement.Product.IdleMinutesMonitor
  • Description:  The purpose of this rule is to alert system administrators to a possible KMS or network outage. This rule monitors the end-to-end operation of KMS activation. A notification event is created by KMS if no activation or renewal requests were logged by KMS (activity event 12290) in the specified time interval. In addition to new activations, periodic renewal requests are expected to occur (default is 7 days). Whether or not this alert is serious depends on the number of machines in the KMS environment, how many are actually connected, and the configured renewal interval.
  • Target:  Key Management Service Product
  • Enabled:  Yes

Operational States

Name State Description
Under Threshold Success  
Over Threshold Error  

Overridable Parameters

Parameter Name Default Value Description Override
Frequency in seconds 900 The frequency in seconds for monitoring KMS Product Idle Minutes against threshold.
Threshold (Minutes) 480 The threshold in minutes for idle activity.

Alert Details

Monitor State Message Priority Severity Auto Resolution
Over Threshold (Error) Idle Minutes Monitor Alert Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The purpose of this rule is to alert system administrators to a possible KMS or network outage. This rule monitors the end-to-end operation of KMS activation. A notification event is created by KMS if no activation or renewal requests were logged by KMS (activity event 12290) in the specified time interval. In addition to new activations, periodic renewal requests are expected to occur (default is 7 days). Whether or not this alert is serious depends on the number of machines in the KMS environment, how many are actually connected, and the configured renewal interval.

Causes

Any failure or incorrect configuration of the KMS service, other Windows components, firewall, hardware, network or routers can trigger the Idle Minutes Alert. This alert can also result from normal behavior, since it is possible that not enough machines attempted to activate or renew during the specified time interval.

Resolutions

The first step is to determine whether there really is a problem. Start with a known good KMS client and run (with elevated privileges) the script slmgr.vbs -ato . If the activation/renewal fails, it will report an error code. You can direct the client to connect to a specific KMS machine by using the slmgr.vbs -skms option. The request event (12288) and response event (12289) in the Windows Application event log may provide additional information, including the identity of failing KMS machines. If there has been a failure, check the following:

Software Licensing service (slsvc) is running.

Other KMS machine behavior is normal.

KMS firewall port is open (default is TCP 1688).

Attempt to connect to KMS using telnet to the KMS port(you won’t be able to do anything other than connect)

Use a network monitor (e.g. netmon) to capture and trace network problems.

There is one Idle Minutes Monitor that is used to monitor for activity. It may be desirable to adjust the time threshold, depending on expected KMS activity.

External References
This monitor does not contain any external references.

See Also for Key Management Service Management Pack


Downloads for Key Management Service Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED