OpsMgr++

When creating a monitor or a rule for a multi instance component you need to be very careful or else you may end up with wrong monitoring logic. The two important parts are: 1. Target the rule/monitor to the correct target type 2. Specify the correct...

One of the issues that we saw in OpsMgr RTM is that if you disabled a discovery using an override let say a particular SQL DB, the instance created by this discovery would not be removed. In SP1 we have added a new cmdlet to force the removal of instances...

Here is a sample that demonstrates how to create a performance collection rule using the SDK. The only caviat is that this rule will not work for agentless monitoring. A powershell version will follow soon. using System; using System.Collections...

This question came up several times in various forums so I wanted to post a sample script that shows how you can retrieve the list of both rules and monitors targeted to a particular class (target): $mc = get-monitoringclass | where {$_.DisplayName...

Below is a link to a targeting poster that we have created to help select the proper targets when creating rules and monitors. The poster illustrates some of the most common scenarios and provides best practices on how to properly target rules and monitors...