Use the following procedure to create a probe-based (script) performance collection rule in Operations Manager 2007. Probe-based rules can get data from an unlimited number of sources, such as the file system or operating system properties. Probe-based rules should not change the state of an object. The data collected by the rule will display in performance views for the targeted objects.

To create a probe-based performance collection rule in Operations Manager 2007

  1. Start the Operations Manager 2007 Create Rule Wizard.

    For information about starting the Create Rule Wizard, see How to Start the Create Rule Wizard in Operations Manager 2007.
  2. On the Select a Rule Type page, do the following:

    1. Expand Collection Rules, expand Probe Based, and then click Script (Performance).

    2. Select a Management pack from the list or click New to create a management pack with the Create a Management Pack Wizard.

      By default, when you create a management pack object, disable a rule or monitor, or create an override, Operations Manager saves the setting to the Default Management Pack. As a best practice, you should create a separate management pack for each sealed management pack you want to customize, rather than saving your customized settings to the Default Management Pack. For more information, see Default Management Pack.
    3. Click Next.

  3. On the Rule Name and Description page, do the following:

    1. Type the Rule name, such as NumProc.

    2. Click Select, select a target, such as Windows Computer, and then click OK.

    3. Leave Rule is enabled selected to have the rule take affect at the completion of the wizard, or clear the check box to enable the rule at a later time, and then click Next.

  4. On the Schedule page, specify how often the rule will run, and then Select Synchronize at to set the time the rule will start. For example, set the rule to run every 1 hour starting at 12:15 AM. Rules set to run on a daily interval are scheduled to start at 12:00AM.

  5. On the Script page, do the following:

    1. Type the Name and extension of the script, such as NumProc.vbs.

    2. Set Timeout to the length of time in seconds, minutes, hours, or days, the script can run before it is terminated.

    3. Type the Script, for example:

      Set oAPI = CreateObject("MOM.ScriptAPI")

      set bag= oAPI.CreatePropertyBag()

      Set WshShell = WScript.CreateObject("WScript.Shell")

      Set WshSysEnv = WshShell.Environment("SYSTEM")

      call bag.AddValue("Number of Processors", WshSysEnv("NUMBER_OF_PROCESSORS"))

      call oAPI.Return(bag)

      The preceding example will determine the number of processors a computer has.
    4. Click Next.

    For more information about the MOMScriptAPI, see the Operations Manager 2007 Software Development Kit (SDK), available at
  6. On the Performance Mapper page, map parameters from the script to fields in the event, for example:

    Parameters are case sensitive.
    1. In Object, type Processor.

    2. In Counter, type Number_of_Processors.

    3. In Instances, type All Instances.

    4. Click the Value () button.

    5. In the Value dialog box, click Data, and then click Property.

    6. In Value, replace [PropertyName] with Number of Processors. The path should read, $Data/Property[@Name='Number of Processors']$.

    7. Click OK, and then click Create.

Did you find this information useful? Please send your suggestions and comments about the documentation.