locked
KMS Management-Pack RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks

    We are using SCOM 2007 R2 in our enterprise and also installed the KMS-Management-Pack.

    the discovery of the components and all these things worked fine. but we're getting all day the following alert:

    Idle Minutes Monitor Alert  Alert Description  

    Source:  Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel / Office 2010

    Desc: Key Management Service (KMS) inactivity exceeded threshold.


    the funny thing is, that the alert will auto-close a few-minutes later.

    i have already checked the kms-event-log and there are many 12990-events. ok, during the night, there is a "hole" during several reboots of our terminal-servers.
    creating an override on the threshold-value (720 minutes!) didn't work :(

    another post in this forum ("http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/1391acf8-f0be-4a48-9039-8d24e275f1fd") recommends to install the hotfix KB981314. but this hotfix isn't compatible with our win2008r2-kms-server.

    any other ideas? or should i just disable this monitor (not very pretty, but the easiest way....?)


    thanks for some replies and greetings from the cold & rainy switzerland

    Friday, May 31, 2013 7:02 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Please also try the following hotfix:

    "0x80041001" error when the Win32_Environment WMI class is queried by multiple requestors in Windows 7 or in Windows Server 2008 R2

    http://support.microsoft.com/kb/2692929

    Thanks.

    Nicholas Li
    TechNet Community Support

    • Marked as answer by Nicholas Li Friday, June 7, 2013 3:52 AM
    • Unmarked as answer by Sandro D'Incà Monday, June 24, 2013 6:06 AM
    Monday, June 3, 2013 6:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi nicholas

    thank you for the reply but the hotfix doesn't work :(

    any other ideas / possibilities to analyze this error?

    Monday, June 10, 2013 3:16 PM