Changing the Rollup Algorithm for Site Service Components

適用於: Operations Manager 2007

The site service components of the Exchange Server 2007 Management Pack represent the health of the particular Exchange service delivered within the site, for example, Outlook Web Access (OWA). A dependency rollup monitor determines the state of the site service component, depending on the state of the Client Access servers within the site. By default, the dependency rollup monitor uses a worst-of algorithm to determine the state of the site service component. This means that if any Client Access server within the site is in a red state, the site server component itself is in the red state.

Depending on how you have implemented Exchange 2007 (using load balanced servers, for example), you might want to change the dependency monitor to use a different algorithm for determining the state of the site service component―for example, to use a best-of algorithm for a health rollup. Using the best-of algorithm means that the state of the site service component reflects the best state of any Client Access server within the site.

To change the default rollup algorithm for the OWA Site Service component

  1. In the Authoring section of the Operations console, go to the Monitors section. Set your scope to Exchange 2007 OWA Service Component.

  2. Expand Entity Health, and then expand Availability. The CAS to OWA Site Service Rollup Monitor appears.

  3. Right-click the monitor and click Overrides, click Override the Monitor, and then click For all objects of type: Exchange 2007 OWA Service Component (you can also override using single instances or a group).

  4. You can change the Rollup Algorithm Parameter Name to what is most appropriate for your implementation. For example, a “Best health state” algorithm would mean that if any Client Access server OWA transactions in a site were in a green state, the Site Service Component would also be in that state.

  5. Ensure you do not save the override in the default management pack, and click OK.

You might also want to change the rollup algorithm for other site service components. This can be accomplished in a similar way.

For Client Access servers (CAS) site services, the health rollup works as follows: if a particular synthetic transaction fails, the site service component changes to an error state. In other words, site service health reflects the health of the synthetic transactions only.

By default, no CAS synthetic transactions are enabled. In order to have the CAS site services monitored, you must set up at least one CAS synthetic transaction. For instructions, see Configuring Client Access Server Synthetic Transactions.