SCOM Management Pack VSAE Fragment Library

This is the SCOM Management Pack Fragment Library which includes VSAE Fragments you can use to make SCOM management packs quickly and easily.See instructions at:

5 Star
5,860 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • TimedScript.PowerShell adding parameters
    2 Posts | Last post August 13, 2017
    • Thanks for the update, i find your Rule.TimedScript.PowerShell very helpful but i also would like to give parameters to the script, or better, overridable parameters.
      I tried adding the <Parameters><Parameter> parts right after the scriptbody like in other fragments and although the build is successfull it doesn't seem to work so if you can put such in example in a newer version that would be great. 
    • Sorry so late with this - I added rules for times scripts - both just as a write action, and to execute as a datasource then alert on output.
  • SNMP Walk Discovery
    1 Posts | Last post April 22, 2017
    • Hi Kevin,
      Can we have a fragment for SNMP Discovery (not device) but objects that SNMP device manage ... I used SNMP Walk discovery in XML file (xSNMP if you know about it) but it is difficult to maintain. hope if we can have a fragment that will save time and efforts.
      Thanks a lot
  • Thanks Kevin
    1 Posts | Last post March 22, 2017
    • A few other practical fragments can be:
      1) Monitor for Powershell scripts
      2) Monitor for log file not modified
      3) Monitor for log file based on key word occurrence X amount of times in a specific time frame
      4) monitor for dynamic service name
  • Fix for version 1.5? - Issue with the PowerShell script monitor
    2 Posts | Last post January 30, 2017
    • First of all, thank you so much for the effort to get it together. It saves me a ton of time and I sure others too. I do use VS everyday for C# and now is one tool for all my needs. 
      My issue with the script (Generic.Monitor.TimedScript.PowerShell.Fragment.mpx) was that the monitor never initialized until I changed what was returned to the PropertyBag. I realized that the example script returned 'GoodCondition' in the propertybag but the monitor itself was looking for the string 'Good'. Once I fixed that it worked perfectly. It was somewhat easy fix for me but I wonder that others that have no experience with SCOM/XML/X-PATH sintax nor Visual Studio it would a little harder so I decided to share.
      Here´s what I changed:
      $bag.AddValue('Result','GoodCondition') <<=== Those were different
                          <XPathQuery Type="String">Property[@Name='Result']</XPathQuery>
                          <Value Type="String">Good</Value> <<=== Those were different
    • Thanks for the feedback!  However - that was actually already fixed in version 1.4.  You were probably working from a previous version?
      Regardless, I just uploaded 1.5.  :-)
21 - 24 of 24 Items