Extending Windows Computer class from a SQL CMDB in SCOM

<!--[if lt IE 9]>

<![endif]-->

Comments

• Anonymous
  January 24, 2017
  CMDB (or whatever the source is) might change and that would require you to rewrite the mp. I create the extended windows computer class based on a registry value and I create scom task to set the registry key. An external script runs daily and reads from the source (CMDB, Excel, CSV, whatever). If there are new or changed properties the scom task(s) are called to set the registry with the new values. When the source changes all i need to do update the external script to grap its data from another source. And if for some reason the "source" is unavailable you can just manually set the keys.
• Anonymous
  October 19, 2017
  The comment has been removed
• Anonymous
  October 19, 2017
  The comment has been removed
  • Anonymous
    October 20, 2017
    We found the error,but in the next step the Data is not populated to the discovered object.
    • Anonymous
      October 25, 2017
      The comment has been removed
      • Anonymous
        October 25, 2017
        Hello Micheal,have you taken a look at the Discovered Invertory View at the Monitoring Pane. Choose your class extension and the values should be there.Hope it helps.Regards Sebastian
        • Anonymous
          October 25, 2017
          Hi Sebastian,i already did, but non of the matching servers come up.When i look under authoring -> management pack objects -> object discoveries i find the discovery that i had imported with the management pack. And in the discovery, i find the values i definite. So right now i don´t know exactly what my problem is.I pull my objects from the SharePoint.... checkedWith the object i get the values i to publish to the server objects in SCOM.... checkedThe script takes the server objects from SCOM and match it against the objects from SharePoint.... checkedHow can i find the error? Can i push the matching data into a file (Excel/csv) to check if the mapping and variables work?Thank you,Michael
          • Anonymous
            November 09, 2017
            The comment has been removed