How Health Rolls Up

  • Article

Applies To: Exchange Server, Operations Manager 2007 R2

The following diagram shows how the health states of components roll up in this management pack. The Microsoft Exchange Server 2007 Management Pack categorizes the Exchange 2007 server components into a layered structure, where the health of one layer can depend on the health of the lower level. The top level of this model contains the Exchange 2007 messaging service. If the underlying service components are not healthy, the Exchange 2007 Messaging Service will not be healthy.

how health rolls up

Note

In general, this management pack rolls up only Availability Health through all levels in the diagram. Performance Health will roll up to the Server Role level, but not beyond that.

The top level consists of the Exchange 2007 Service, which represents the health of all the Exchange 2007 components. The level below this is the Exchange organization. The management pack supports monitoring of one or more organizations.

The next level is Sites. These correspond to Active Directory sites with agent-managed Exchange 2007 servers in them. No other sites will be discovered or shown by the management pack.

The next level is a service layer corresponding to the different Exchange 2007 services that are implemented within the site. Examples of these are Exchange ActiveSync, MAPI, and Outlook Web Access (OWA) services. This level provides a health rollup of all servers that deliver the particular service within the site.

The next level consists of the Exchange 2007 server roles.

Note

The health rollup from the Client Access servers (CAS) server role to the CAS-related site services is based only on synthetic transactions. For example, the Outlook Web Access service changes state to red only if any Test-OwaConnectivity synthetic transactions fail.

The same is true for the MAPI service; it will only reflect the health of Mail Flow transactions within that particular site.

Note

By default, no Client Access server synthetic transactions are enabled, which means that the services will be shown as “Not Monitored”. In order to have the Client Access server site services monitored, you must set up at least one Client Access server synthetic transaction per site with agent-managed Exchange 2007 Client Access servers. For instructions, see How to Configure Client Access Server Synthetic Transactions Using the Exchange 2007 Client Access Server Monitoring Template.

The server roles might host different components. For example, the Mailbox Server role hosts several components:

  • ExBPA: Represents the state of running the Exchange Best Practice Analyzer.

  • ESE: The extensible storage (database) engine.

  • Common components: Represents the state of the monitoring that applies to all Exchange server roles (such as monitoring Active Directory access).

  • You will also see all the mailbox and public folder databases discovered.

  • Under ESE, you can see a number of disks that are discovered. These are disks that have Exchange database, log, or queue files on them.

  • Synthetic transactions are represented using the Perspectives icon 78452a5f-3adc-4ce3-8527-6274d6503e1d. Synthetic transactions that run between two Exchange servers (such as Mail Flow) will show up under both servers in the Topology view.