Compartir a través de

monitoring KMS 2012 with SCOM 2012

  • Artículo

Hi all,

as you have probably seen, there is no new KMS MP for KMS 2012 and SCOM 2012. The old one is only for KMS 2008 monitoring and SCOM 2007. Since SCOM 2012 can read 2007 MP schemas, the MP can be used also with SCOM 2012.

However the discovery will take place only when detecting some KMS keys which are 2008 specific.

To work around this issue you can create on the KMS 2012 server a registry key under the following path: SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL

Create a new key named: KeyManagementServiceVersion

It does not need a specific value, we only detect its presence.

This is a workaround for monitoring KMS 2012 servers with SCOM 2012 with using also the official MP.

Comments

  • Anonymous
    April 15, 2015
    Yes confirmed as working well. Suggest setting the key as either 2012 or 2012R2 depending on the windows server version you have enabled as a KMS host server. Older versions used the actual KMS version... e.g. 6.3.9600.16497
    but it seems that at some point during development MS in their wisdom decided to drop this particular key. As SCOM uses this reg setting as the trigger to identify if a server is running as a KMS. This quick fix works !
  • Anonymous
    June 01, 2016
    Great JOB!!!!Congrats, it works !!!
  • Anonymous
    April 10, 2018
    Hi Silvana,what about doing it with SCOM 2016?Any special considerations?Thnaks for your feedback.