ProbeAction (ProbeActionModuleType)

System Center

Updated: August 10, 2011

Applies To: Operations Manager 2007 R2, System Center Operations Manager 2007

Represents an implementation of a probe action module type definition.

<ProbeAction ID=”ModuleID” Comment=”Comment” TypeID=”ModuleTypeID”>
Custom Schema Defined Parameters

The following sections describe attributes, child elements, and the parent element of the ProbeAction element.



Attribute Description


Required attribute. Represents the identity of the element.


Optional attribute. Represents commentary by the management pack author.


Required attribute. Represents the ProbeAction module type definition from which this ProbeAction module inherits its configuration schema.

ID Attribute


Value Description

The format for the ID attribute should be UniqueElementID.

The ID string must contain the following characteristics:

  • The length is less than 255 characters.

  • The ID begins with a letter (a-z) or a number (0-9).

  • The ID contains only letters, numbers, the period character (.), or the underscore (_) character.

  • The ID is unique across all elements within the scope of the ProbeAction module’s containing workflow.

  • The ID is case-sensitive.

Child Elements

The child element of the ProbeAction module is defined by the Configuration (ProbeActionModuleType) schema of its base type as referenced in the TypeID attribute.

Parent Elements


Element Description

MemberModules (ProbeActionModuleType)

Contains all of the modules that are used in the linear workflow of a module type definition.

A ProbeAction module takes a single input stream and outputs data. The data types of its input and output data are defined in its InputType (ProbeActionModuleType) and OutputType (ProbeActionModuleType) elements, respectively. Like a DataSource (DataSourceModuleType) module, the probe action module runs a process or script to gather data from a source, processes it in some way, and finally returns the data. However, unlike a data source module, a probe action module can receive input data and therefore does not have to be the first element in the workflow.

A probe action module type never alters system state. If you want your module to affect system state, you must instead use or implement a WriteAction (WriteActionModuleType) module.

With the exception of a Task workflow, a probe action module type is usually preceded by a data source scheduler module so that its action can occur at an interval at some frequency.

A probe action module’s base type must always be a descendant of a ProbeActionModuleType type.

In the following sample, a composite probe action module modularizes the functionality of a ProbeAction (ProbeActionModuleType) module and a ConditionDetection (ProbeActionModuleType) module. In this case, the Microsoft.Windows.ProductInstallationProbe module contains a probe that is used to query WMI at a certain interval. The condition detection module filters on the ProductCode value that was passed in through the configuration parameter. The module will return System.PropertyBagData if the filter the condition detection satisfies the filter.

<ProbeActionModuleType ID="Microsoft.Windows.ProductInstallationProbe" Accessibility="Public">
    <xsd:element name="ComputerName" type="xsd:string" />
    <xsd:element name="ProductCode" type="xsd:string" />
    <OverrideableParameter ID="ComputerName" ParameterType="string" Selector="$Config/ComputerName$" />
    <OverrideableParameter ID="ProductCode" ParameterType="string" Selector="$Config/ProductCode$" />
        <ProbeAction ID="WmiProbe" TypeID="Microsoft.Windows.WmiTriggerProbe">
          <Query>SELECT * FROM Win32_Product</Query>
        <ConditionDetection ID="FilterOnProductCode" TypeID="System!System.ExpressionFilter">
                <XPathQuery Type="String">Property[@Name='IdentifyingNumber']</XPathQuery>
                <Value Type="String">$Config/ProductCode$</Value>
        <Node ID="FilterOnProductCode">
          <Node ID="WmiProbe" />