Have you ever wanted to detect a monitoring condition on an agent (Lets call it ProdWebser-01) and follow up the condition with a custom to either remediate the issue or get additional data for the alert? Great Idea, leveraging the agent is one of the best strengths of SCOM.

If you’re developing a management pack with custom UI and/or .NET modules you’ve gone through the steps of getting your DLL recognized by the engine and loaded as an Assembly or DeployedAssembly depending on the project (here’s an SCSM example). Durning an ongoing project constantly updating the resource mpx file to have the correct QualifiedName can be frustrating, time-consuming, and error-prone.

Resetting the monitor that triggered an alert is the best option in SCOM as it will allow the monitor to alert again, if needed. Working programmatically this is easy for alerts that are generated from a Unit Monitor. A Dependency Monitor can be more challenging, which is what we’ll address here. To properly reset your Dependency Monitor you will need to find the underlying Unit Monitor(s) and reset them.

90 seconds with ServiceNow’s Identification and Reconciliation engine, a key tool to your complete CMDB. Configuration data is spread enterprise-wide, spanning multiple systems and sources, each with its strengths and weaknesses. To create a centralized database that can be used confidently by all teams this cornucopia of data needs to be pruned, consolidated, and maintained.