SCOM Override report and uigenerated names on monitors/reports

System Center Operations Manager (SCOM) 2007 lacks any reports on the effective rules or monitors applied to the environment. I feel comforted by being able to see what I've got enabled. I decided to make all my custom monitors and rules as disabled in sealed management packs and enable them in overrides placed in other management packs. This is pretty much the best practice that I see everybody say you should use.

When you author your overrides in the SCOM console and then go run the handy Override report, all the Affected Elements have an obfuscated name similar to uigenerated and is less than helpful.

Solution?

• Export the management pack that contains the overrides
• Edit the xml and find the <LanguagePack ... > element
• Modify the IsDefault attribute to be true instead of false.
• Modify the version of the management pack at ManagemetPack|Manifest|Identity|Version
• Save and Import the management pack

This does not resolve the issue of the Targets being obfuscated. I did not find an easy solution for that, but had to create a custom version of the stored procedure and report to fix it.

So you want to generate an alert from an Event Log on a cluster?

So you've got a shiny new installation System Center Operations Manager (SCOM) 2007 and some services running on a Cluster you want to monitor. One might think it would be a simple matter of creating a rule and targeting the cluster.

One would be wrong.

The xml of the management pack has to be edited to include the 1 element added to the configuration of the datasource for the rule. For example:

.
.
.
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<AllowProxying>1</AllowProxying> <!-- This is it here -->
<Expression>
.
.
.

This is necessary only if the service generating the event logs is NOT cluster-aware. Applications like SQL Server are cluster-aware and will emit their messages with their computer name set properly. If the application is not cluster-aware, it will use the cluster-node that it's running on as it's computer name.

So you want to base an Alert off an Event Log message in a Clustered Environment?

So you've got a shiny new installation System Center Operations Manager (SCOM) 2007 and some SQL Servers that are Clustered. One might think it would be a simple matter of creating a rule and targeting the cluster.

One would be wrong.

The xml of the management pack has to be edited to include the 1 element added to the configuration of the datasource for the rule. For example:

.
.
.
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<AllowProxying>1</AllowProxying> <!-- This is it here -->
<Expression>
.
.
.

Hello

Welcome to my little corner of the blogsphere. Who knows what this will turn into. I mainly created this to share any insights I may gain into the workings of Microsoft's System Center Operations Manager (SCOM).