Have you ever created a rule, monitor, task or group in the Operations console and then exported the unsealed MP and tried to find the rule, monitor, task or group? If you have, you will have noticed that when you create an MP element such as a rule, monitor, task or group in the Operations Console, it’s assigned a name with a unique GUID in the MP and this can make it hard to search for. Let’s explore this a little further.

In the Operations Console, create a new rule named Domain Admin Membership Change. Export the unsealed MP from the Operations Manager Console and open the xml document in Notepad. (Or any xml editor)

<Monitoring>

<Rules>

<Rule ID="MomUIGeneratedRule2a5e0cd6c818445b9e62c8d4992127ce" Enabled="true" Target="Windows!Microsoft.Windows.Server.2003.OperatingSystem" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

<Category>SecurityHealth</Category>

<DataSources>

<DataSource ID="DS" TypeID="MicrosoftWindowsLibrary6062780!Microsoft.Windows.EventProvider">

<ComputerName>$Target/Host/Property[Type="MicrosoftWindowsLibrary6062780!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

<LogName>Security</LogName>

Look for the Rule ID in this example, highlighted above. This is the name assigned to the rule by the Operations Console. You can see that this name matches the friendly name of Domain Admin Membership Change that you entered when creating the rule in the Operations Console.

<DisplayString ElementID="MomUIGeneratedRule2a5e0cd6c818445b9e62c8d4992127ce">

<Name>Domain Admin Membership Change</Name>

The Command Shell can also be used to resolve the friendly name known as the DisplayName property to the GUID by running the following command:

Get-rule | where-object {$_.DisplayName –eq “Domain Admin Membership Change”} | format-list Name

The result of this command can be seen below.

This can be useful in helping you to correlate the friendly name that you assigned to a rule to the ‘Name’ property that the Operations Manager console assigned to the rule when you created it.

For more of this type of technical information on Ops Mgr 2007 check out our training at www.infrontconsulting.com/events.htm.

If you receive the following error when attempting to run a PowerShell script “The file foo.ps1 is not digitally signed. The script will not execute on the system.”

To resolve this, locate the ps1 file in Windows Explorer and right click on the file and select Properties.

In the Properties dialog box, click Unblock and click OK.