This section lists Operations Manager 2005 management pack elements and provides details about what happens during the conversion process, including how the converted elements are used in Operations Manager 2007.

Operations Manager 2005 Object Operations Manager 2007 Object

Alert severity

Health state


Monitor—for alert-generating rules

Rule—for non-state-generating rules

Collection Rule—for performance rules

Computer group

Computer Group class

Installation class

Two Discovery rules are also generated during conversion.

Class (used for state monitoring)



Rule or monitor


Module type





Notification group

Notification rules


Not converted


Not converted

Console scope

Not converted


Knowledge article



Computer Groups

In Operations Manager 2005, computer groups are used to group computers with like characteristics. Processing rule groups are then used to target groups of rules to these computers.

Operations Manager 2007 focuses on monitoring individual services and applications instead of computer objects. This approach allows Operations Manager 2007 to monitor the physical server differently from the software that is installed on the computer. When a computer group is converted from Operations Manager 2005 to Operations Manager 2007, two object types are created. One object type is for the physical computer, and the other one is for software.

For example, the Operations Manager 2005 version of the Microsoft SQL Server 2000 Management Pack contains a computer group for servers running SQL Server 2000. After conversion, the Operations Manager 2007 console contains a Microsoft SQL Server 2000 Computer Group and also an object type called Microsoft SQL Server 2000 Installation.


Discovery is the process of finding objects that Operations Manager is configured to monitor. In Operations Manager 2005, population of computer groups is done by computer discovery rules, while the discovery of services is accomplished through service discovery scripts.

When an Operations Manager 2005 computer group is converted, two discovery rules are created for use in Operations Manager 2007. One rule controls membership in the computer group, and the other rule finds installed versions of the software that belong to the software installation class.

Service discovery is accomplished through the use of service discovery scripts. These scripts are contained in management packs. These scripts work the same way in Operations Manager 2007 that they do in Operations Manager 2005. No conversion is necessary.


Rules in Operations Manager 2005 either gather and analyze data or change the state of a monitored object. The health state of a monitored object is displayed with colors in Operations Manager, such as green (running and healthy), yellow (in danger of a failure), or red (failed). Rules that are designed to change the health state of a monitored object in Operations Manager 2005 are converted into monitors in Operations Manager 2007. These monitors change the state of a monitored object in Operations Manager 2007.

In Operations Manager 2005, rules that do not change state look for a specific event and react to that event in a defined way. An example of this type of rule is one that looks for a specific event in the event log and then generates an alert when that event is found. These types of rules are converted into Operations Manager 2007 rules. However, in Operations Manager 2005, these rules are targeted to computer groups. After they are converted, they are targeted to the software installation group.

Each rule is within a rule group, and rule groups, in turn, are usually targeted to a computer group. Rules that are not targeted to anything or that belong to rule groups that are not targeted are not converted.

Filter Rules

Operations Manager 2005 uses filter rules. There are three distinct types of filter rules:

  • Prefilter

  • Conditional filter

  • Database filter

Filters are not used to Operations Manager 2007, and these rules are dropped during conversion.


Scripts are distinct objects that can be referenced by rules in Operations Manager 2005. Scripts are often run on a timed basis for use in service discovery and monitoring, but they are also used as responses to observed conditions and as tasks. Scripts are converted into module types in Operations Manager 2007. These module types are used by one or more rules to pass configuration for script parameters.

Operations Manager 2005 scripts continue to function in Operations Manager 2007 without modification using backward-compatible script modules. Operations Manager 2007 has a redesigned scripting model, and any new scripts should be written to this new model. For more information about scripting in Operations Manager 2007, see the Operations Manager 2007 SDK documentation.

Task Conversion

Tasks in Operations Manager 2005 are actions that are started by users to diagnose or resolve a problem or to automate repetitive actions. Tasks are configured to start on Operations Manager management servers or agents in the Operations Manager 2005 Operator Console.

Tasks that are agent tasks in Operations Manager 2005 are converted into Operations Manager 2007 tasks. These tasks are then targeted to either the Software Installation class or to a Service Discovery class. Tasks in Operations Manager 2005 that are set to start against a management server rather than an Operations Manager agent are not converted. Managed code tasks and tasks that are started from the Operations Manager 2005 Operator Console are not converted.

Notification Group Conversion

The notification engine is redesigned in Operations Manager. As a result, notification groups are not contained in an Operations Manager 2007 management pack. Notification groups that are defined in an Operations Manager 2005 management pack are not converted.

Operator Conversion

Operators should not be defined in vendor management packs. However, customers can export operators as part of their Operations Manager 2005 management pack. Also, any operator that is part of a notification group used by a rule in an Operations Manager 2005 management pack is exported automatically. Operators are no longer contained in the management pack in Operations Manager 2007, and as a result, operators are not converted as part of the conversion process.

Console Scopes

Console scopes in Operations Manager 2005 are used to control user access to Operations Manager functions. Console scopes are not contained in an Operations Manager 2005 management pack file and are not converted.

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