Exchange Server 2010 Management Pack Guide

Exchange 2010 Management Pack Guide for Operations Manager 2007

Microsoft Corporation

Published: 11/9/2009

Send suggestions and comments about this document to [email protected]. Please

include the management pack guide name with your feedback.

AbstractThe Microsoft Exchange Server 2010 Management Pack includes a complete health model,

extensive protocol synthetic transaction coverage, and a full complement of diagnostics-based

alerts and service-oriented reporting, including mail flow statistics.

Alerts are classified by impact and recovery action, and are now processed by a new component

called the Correlation Engine. The Correlation Engine suppresses duplicate alerting whenever

possible to increase the alert-to-ticket ratio of front line monitoring technicians.

Most of the diagnostic information used in the Exchange 2010 Management Pack, including

events and performance counters, is specifically engineered for monitoring. Very little tuning is

required to monitor your Exchange organization. The Exchange 2010 Management Pack will

scale with your environment.

The Exchange 2010 Management Pack is engineered for organizations that include servers

running Exchange 2010. It is not based on the Exchange 2007 Management Pack. Therefore,

you will notice some differences in the way you deploy and configure the Exchange 2010

Management Pack if you have previously used the Exchange 2007 Management Pack.

This guide was written based on the 14.0.650 version of the Exchange Server 2010 Management

Pack.

1

mailto:[email protected]

Copyright

Information in this document, including URL and other Internet Web site references, is subject to

change without notice. Unless otherwise noted, the companies, organizations, products, domain

names, e-mail addresses, logos, people, places, and events depicted in examples herein are

fictitious. No association with any real company, organization, product, domain name, e-mail

address, logo, person, place, or event is intended or should be inferred. Complying with all

applicable copyright laws is the responsibility of the user. Without limiting the rights under

copyright, no part of this document may be reproduced, stored in or introduced into a retrieval

system, or transmitted in any form or by any means (electronic, mechanical, photocopying,

recording, or otherwise), or for any purpose, without the express written permission of Microsoft

Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual

property rights covering subject matter in this document. Except as expressly provided in any

written license agreement from Microsoft, the furnishing of this document does not give you any

license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, and MS-DOS, Windows, Windows Server, and Active Directory are trademarks of the

Microsoft group of companies.

All other trademarks are property of their respective owners.

2

Contents

Exchange 2010 Management Pack Guide......................................................................................5

Introduction to the Exchange 2010 Management Pack...............................................................5

Getting Started with the Exchange 2010 Management Pack......................................................6

Before You Import the Exchange 2010 Management Pack......................................................6

How to Import the Exchange 2010 Management Pack............................................................8

Creating a New Management Pack for Customizations...........................................................9

Optional Configurations.............................................................................................................10

Security Considerations.............................................................................................................11

Understanding Management Pack Operations..........................................................................11

Understanding Classes..........................................................................................................12

Understanding Alert Correlation.............................................................................................12

Appendix: Reports..................................................................................................................... 16

Appendix: Synthetic Transactions..............................................................................................17

Appendix: Scripts....................................................................................................................... 19

Appendix: Objects the Management Pack Discovers................................................................20

Appendix: Class Hierarchy........................................................................................................48

Client Access Class Hierarchy...............................................................................................49

Hub Transport Class Hierarchy..............................................................................................50

Edge Transport Class Hierarchy............................................................................................51

Unified Messaging Class Hierarchy.......................................................................................52

Mailbox Class Hierarchy........................................................................................................53

Mailbox - High Availability and Mailbox Services Class Hierarchy.........................................54

Common Classes Class Hierarchy.........................................................................................55

Roles Class Hierarchy............................................................................................................56

Groups Class Hierarchy.........................................................................................................57

Appendix: Alert Correlation Relationships.................................................................................57

Client Access - On Server Alert Correlation Relationships.....................................................59

Client Access - Server to Site Alert Correlation Relationships................................................60

Edge Transport Alert Correlation Relationships......................................................................61

Hub Transport Alert Correlation Relationships.......................................................................62

Mailbox - High Availability Alert Correlation Relationships......................................................63

Mailbox - Information Store Alert Correlation Relationships...................................................64

Performance, Disks, and Public Folders Alert Correlation Relationships...............................65

Unified Messaging Alert Correlation Relationships.................................................................66

3

Exchange 2010 Management Pack Guide

The Microsoft Exchange Server 2010 Management Pack includes a complete health model,

extensive protocol synthetic transaction coverage, and a full complement of diagnostics-based

alerts and service-oriented reporting, including mail flow statistics.

Alerts are classified by impact and recovery action, and are now processed by a new component

called the Correlation Engine. The Correlation Engine suppresses duplicate alerting whenever

possible to increase the alert-to-ticket ratio of front line monitoring technicians.

Most of the diagnostic information used in the Exchange 2010 Management Pack,

including events and performance counters, is specifically engineered for monitoring. Very little

tuning is required to monitor your Exchange organization. The Exchange 2010 Management Pack

will scale with your environment.

The Exchange 2010 Management Pack is engineered for organizations that include servers

running Exchange 2010. It is not based on the Exchange 2007 Management Pack. Therefore,

you will notice some differences in the way you deploy and configure the Exchange 2010

Management Pack if you have previously used the Exchange 2007 Management Pack.

This guide was written based on the 14.0.650 version of the Exchange Server 2010 Management

Pack.

Send suggestions and comments about this document to mailto:[email protected]. Please

include the management pack guide name with your feedback.

Introduction to the Exchange 2010 Management PackYou can find the Microsoft Exchange Server 2010 in the System Center Operations Manager

2007 Catalog (http://go.microsoft.com/fwlink/?LinkId=82105).

What's NewThe following features are new in this release of the Exchange Server 2010:

Alert correlation

Alert classification

Mail flow statistics reporting

Full protocol synthetic transaction coverage

Service-oriented reporting

Exchange aware availability modeling

5

http://go.microsoft.com/fwlink/?LinkId=82105


mailto:[email protected]

Supported ConfigurationsThe following table details the supported configurations for the Exchange Server 2010 and

Correlation Engine component.

Configuration Support

R2 Servers running Exchange 2010 (agents) are

64-bit only based on the minimum requirements

for Exchange Server 2010.

The Correlation Engine component supports

32-bit or 64-bit architectures.

Agentless monitoring Not supported.

Virtual environment Not supported.

System Center Operations Manager System Center Operations Manager 2007 or

System Center Operations Manager 2007 R2.

Getting Started with the Exchange 2010 Management PackThere are actions that you must take before you import the Microsoft Exchange Server 2010

Management Pack and steps that you must take to properly import the Exchange Server 2010

Management Pack. There is also information that you must consider when making management

pack customizations.

Review the following topics to properly deploy the Exchange Server 2010 Management Pack in

your environment.

Before You Import the Exchange 2010 Management Pack

How to Import the Exchange 2010 Management Pack

Creating a New Management Pack for Customizations

Before You Import the Exchange 2010 Management PackBefore you import the Microsoft Exchange Server 2010 Management Pack, take the following

actions:

Consider the supported configurations for the Exchange Server 2010 Management Pack. For

more information about the supported configurations, see Introduction to the Exchange 2010

Management Pack earlier in this guide.

Ensure that all Exchange 2010 computers that are managed by the Operations Manager use

LocalSystem as the Agent Action Account.

6

If you are monitoring Exchange Server 2010 Database Availability Groups (DAGs), ensure

that all DAG members are monitored by Operations Manager 2007.

Ensure that all agents on Exchange 2010 computers have Agent Proxy enabled.

Install the update specified in Microsoft Knowledge Base article 971541 if you are running

Operations Manager 2007 SP1. Install the update specified in Microsoft Knowledge Base

article 974144 if you are running Operations Manager 2007 R2. Both of these articles and

respective updates are pending release to the Microsoft Help and Support

(http://go.microsoft.com/fwlink/?LinkId=5967) Web site. These updates resolve several critical

issues that are more likely to occur when running the Exchange 2010 Management Pack.

Note:

It is critical for Exchange Server 2010 Management Pack functionality that you install

the referenced Operations Manager updates as soon as they are released. These

updates resolve serious issues affecting state rollup using dependency monitors. These

updates allow the Exchange Server 2010 Management Pack to accurately

monitor whether Exchange databases are mounted. Failing to install the respective

update on your Root Management Server and all agent computers will also result in

inaccurate availability reporting.

The Exchange Server 2010 Management Pack includes a Windows service component

called the Correlation Engine. This service determines the best alert to raise by examining the

Exchange 2010 health model through the Operations Manager Software Development Kit

(SDK) service. Consider the following:

Determine which server will host the Correlation Engine. While not strictly required, it is

highly recommended that the Correlation Engine service is installed on the Operations

Manager Root Management Server (RMS).

Download the Correlation Engine service package that matches the operating system for

selected server. The package is available in 32-bit or 64-bit versions.

Launch the Microsoft Installer (MSI) package on the selected server and complete the

installation.

When the installation is complete, the Correlation Engine is installed on the server, and

the management packs are copied to the System Center Management Packs folder. By

default, the installation directory is:

C:\Program Files\System Center Management Pack

For more information about the Correlation Engine, see Understanding Alert Correlation later in

this guide.

Files to Download

The Exchange Server 2010 Management Pack installation package includes the following files:

Microsoft.Exchange.2010.mp

Microsoft.Exchange.2010.Reports.mp

7


The installation package also contains the files required by the Correlation Engine service and the

Exchange Server 2010 Management Pack license agreement.

Recommended Additional Management Packs

To provide complete coverage for Microsoft Exchange Server 2010 and all of its dependent

services, we recommend that you also install the following management packs:

Active Directory

Internet Information Services

Domain Naming Service (DNS)

Windows Server 2008 or Windows Server 2008 R2

Note:

Unless required for other infrastructure, the Windows Clustering Management Pack is not

recommended. You will find instructions later in this guide for how to disable the Windows

Clustering Management Pack on computers running Exchange 2010 servers if the

Windows Clustering Management Pack is included in your management group.

Other Requirements

The Exchange Correlation service requires the following:

It must be installed on a computer running Windows Server 2003, or either the 32-bit or 64-bit

version of Windows Server 2008 or Windows Server 2008 R2.

It must have network connectivity to the Operations Manager Root Management Server

(RMS).

The Operations Manager Administration Tools must be installed on the computer running the

Exchange Correlation service.

How to Import the Exchange 2010 Management PackFor instructions about importing a management pack, see How to Import a Management Pack in

Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=142351).

1. Log on to the computer with an account that is a member of the Operations Manager

Administrators role for the Operations Manager 2007 management group.

2. In the Operations console, click Administration.

Note:

When you run the Operations console on a computer that is not a management

server, the Connect to Server dialog box displays. In the Server name text box,

type the name of the management server to which you want to connect.

3. Right-click the Management Packs node, and then click Import Management Packs.

4. The Import Management Packs wizard opens. Click Add, and then click Add from disk.

5. If prompted to connect to the online catalog, click No.

8



6. The Select Management Packs to import dialog box appears. Go to the directory where

your management pack file is located. By default, the location is C:\Program Files\System

Center Management Packs.

7. Select both management pack files to import from that directory, and then click Open.

8. On the Select Management Packs page, the management packs that you selected for

import are listed. An icon next to each management pack in the list indicates the status of the

selection, as follows:

a. A green check mark indicates that the management pack can be imported. A blue

exclamation point indicates that an older version of the management pack is installed.

When all of the management packs in the list display one of these icons, click Import.

b. A red error icon indicates that the management pack is dependent on one or more

management packs that are not in the Import list and are not available in the catalog. To

view the missing management packs, click Error in the Status column. To remove the

management pack with the error from the Import list, right-click the management pack,

and then click Remove.

Note:

When you click Import, any management packs in the Import list that display the

Error icon are not imported.

9. You will receive a prompt indicating that the management pack presents a security risk. This

is due to the management pack's use of agent proxying. Click Yes to allow the import.

10. The Import Management Packs page appears and shows the progress for each

management pack. Each management pack is downloaded to a temporary directory,

imported to Operations Manager, and then deleted from the temporary directory. If there is a

problem at any stage of the import process, select the management pack in the list to view

the status details. Click Close.

Discovery

Each discovery in the management pack is discovered by default. No additional configuration

should be necessary in most customer environments. See Appendix: Objects the Management

Pack Discovers later in this guide for a table of discoveries and the classes that they discover.

Creating a New Management Pack for CustomizationsMost vendor management packs are sealed so that you cannot change any of the original

settings in the management pack file. However, you can create customizations, such as overrides

or new monitoring objects, and save them to a different management pack. By default, System

Center Operations Manager 2007 saves all customizations to the Default Management Pack. As

a best practice, you should instead create a new management pack for each sealed management

pack you want to customize.

Creating a new management pack for storing overrides has the following advantages:

9

It simplifies the process of exporting customizations that were created in your test and pre-

production environments to your production environment. For example, instead of exporting

the Default Management Pack that contains customizations from multiple management

packs, you can export just the management pack that contains customizations of a single

management pack.

You can delete the original management pack without first needing to delete the Default

Management Pack. A management pack that contains customizations is dependent on the

original management pack. This dependency requires you to delete the management pack

with customizations before you can delete the original management pack. If all of your

customizations are saved to the Default Management Pack, you must delete the Default

Management Pack before you can delete an original management pack.

It is easier to track and update customizations to individual management packs.

For more information about sealed and unsealed management packs, see Management Pack

Formats (http://go.microsoft.com/fwlink/?LinkId=108355). For more information about

management pack customizations and the Default Management Pack, see About Management

Packs in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=108356).

Optional ConfigurationsThe Microsoft Exchange Server 2010 Management Pack has been deployed at Microsoft for

more than two years in a wide range of environments. This experience has led to significant

improvements to the Exchange 2010 Management Pack. It has also helped to improve the overall

monitoring capability of Exchange Server 2010. The experience of monitoring Exchange over the

past two years has helped the management pack to work effectively in most Exchange

configurations using the default configuration. While some fine tuning may be required for certain

environments, the Exchange 2010 Management Pack discovery process generally loads the

correct monitors on the various servers in an Exchange organization. For example, performance

threshold rules are based on scalable calculations and not fixed digit thresholds. In the

Exchange 2010 Management Pack, you’ll find a number of rate and percentile counters that are

explicitly designed to allow the Exchange 2010 Management Pack to scale from small

deployments to large datacenter environments.

Enabling Event Collection for Synthetic Transaction RulesThe Exchange 2010 Management Pack uses synthetic transactions, such as the running of the

Test-MapiConnectivity, Test-OwaConnectivity, and other commands, to scan your Exchange

organization for basic connection responses and to test simple operations such as logging in to a

mailbox. Whether these tests succeed or fail, their output is useful for investigating the state of

the Exchange environment. However, since there is a significant amount of output for each task,

the event output is not stored by default. The views for these tests in the Operations Console

are populated if you enable the event collection rules for each respective test.

10





Caution:

Enabling these event collection rules will dramatically increase the size of your

warehouse database. Each task creates from 4 through 12 event messages every time it

runs. Each test runs every five minutes by default. When you enable these collection

rules, make sure that you have sufficient disk space to accommodate this additional data.

To enable the event collection rules for synthetic transaction output:

1. In the Operations Console, click Authoring.

2. In the Authoring pane, expand Management Pack Objects, and then click Rules.

3. In the Rules pane, click Change Scope.

4. In the Scope Management Pack Target(s) by object dialog box, in the Look for box, type

"Exchange Server 2010."

5. Click View all targets.

6. Click Select All if it’s not disabled (it is only disabled when all rows are already selected).

7. Click OK to close the dialog box.

8. After the rules have loaded, type "Script event collection" in the Look for box near the top of

the console.

9. For each test task that you would like to enable, perform the following steps:

a. Right click on the rule and select Overrides > Override the Rule > For all objects of

class: [class name].

b. Click the Override checkbox.

c. Set the override value to True.

d. Click OK.

It will take some time for the overrides to be picked up by the agents and for events to

appear in the built-in views.

Security ConsiderationsDue to the security model under which Microsoft Exchange Server 2010 has been tested, running

the agent as anything other than LocalSystem has not been tested.

Caution:

If you run the agent as anything other than LocalSystem, then the synthetic transactions

fail to run. You may also experience other issues.

Understanding Management Pack OperationsIt is important to understand the classes and alert correlation used by the

Microsoft Exchange Server 2010 Management Pack.

Review the following topics to learn more about the classes and alert correlation for the

Exchange Server 2010 Management Pack:

11

Understanding Classes

Understanding Alert Correlation

Understanding ClassesThe Microsoft Exchange Server 2010 includes an extensive class model. Diagrams showing the

class model are provided in the Appendix: Class Hierarchy later in this guide. Consider the

following information about Client Access server classes and site-wide aggregated classes.

Client Access Protocol and Client Access Service Classes

The Client Access server role is strongly associated with Active Directory site boundaries. The

class model for client access reflects this association. For most protocol classes hosted on the

Exchange/agent computer, there is a class hosted on the Root Management Server (RMS) that

represents the health of that protocol for the site. State rolls up from that protocol on each server

to the site-wide instance.

Site-Wide Aggregated Classes

The site-wide aggregated classes use an aggregation on their dependency monitors so that the

state changes only when all of the Client Access servers detect a protocol failure for a given

protocol. This is intended to model the corrective actions taken by load balancing technologies to

divert the load to functional servers as protocols/servers fail. In the Appendix: Class Hierarchy in

this guide, these classes have the suffix "Service." These classes are represented in the "Service

State" view.

For more details about how these site-wide aggregated classes impact availability reporting, see

"Appendix: Reports" later in this guide.

Understanding Alert CorrelationAt the core of the Microsoft Exchange Server 2010 Management Pack is the Correlation Engine.

The goal of the Correlation Engine is to significantly reduce the number of alerts that may not

require an action by the administrator that is monitoring the Exchange environment by watching

the System Center Operations Manager Console.

Architecture

The Correlation Engine is a stand-alone Windows service that uses the Operations Manager SDK

interface to first retrieve the health model (or instance space) and then process state change

events. By maintaining the health model in memory, and processing state change events, the

Correlation Engine is able to determine when to raise an alert based on the state of the system.

12

In the diagram above, you can see that, in response to a problem, several monitors change state,

and the corresponding state change events are forwarded by the agent to the Root Management

Server (RMS). Once received by the RMS, they are processed by the Correlation Engine, which

may raise an alert via the RMS’s Software Development Kit (SDK) interface. This alert is then

visible on the Operations Manager Console.

Alert Classification

Exchange Server 2010 Management Pack alerts are classified into one of three categories. Use

the following guidelines to understand these alert classifications.

Key Health Indicator (KHI) KHIs are issues that affect the health of the service. Most alerts

fall into this category (for example, "A mailbox database is dismounted.")

Non-Service Impacting (NSI) NSI monitors detect problems that may affect some users,

but not every user of the system. A good example of an NSI situation is two users with the

same proxy address – mail to this address will be returned as non-deliverable, but the overall

transport system is not otherwise impaired.

Forensic Forensic monitors are used to record information that may be relevant while

troubleshooting an issue, but isn’t necessarily indicative of an eminent or existing system

failure. "CPU activity >90% for 5 minutes" is an example of a forensic issue – there may be a

process inappropriately consuming CPU cycles, or the server may have been rebooted and is

catching up on normal system activity. These monitors are visible in the Alert Context field of

the alert properties and in Health Explorer. Alerts are not raised for Forensic monitors.

Note:

State is not updated when a single forensic monitor alert is raised. However, state may

be updated based on the aggregation of current forensic monitor alerts for each

component.

Alert Severity

Exchange Server 2010 Management Pack alerts are also classified by the severity of the

alerts. Use the following guidelines to understand alert severity.

13

Error alerts Error alerts are alerts that require human intervention to restore the service to

proper operation.

Warning alerts Warning alerts provide an early warning that the system may fail (which

would then raise an Error, if appropriate).

Informational alerts Informational alerts are not raised by the Exchange 2010 Management

Pack.

Correlation Factors

The actions taken by the Correlation Engine is determined based on the several factors.

Monitor state change events Monitors, which watch for the specific diagnostics from

Exchange such as event log messages, performance counter thresholds, and PowerShell task

output events, register state change events when they detect that a problem has occurred or

cleared (red to green or green to red), or as agents become unavailable or are placed in

maintenance mode (and subsequently made available, and/or removed from maintenance mode).

Typically, alert rules are configured to fire when green to red state changes occur. In the

Exchange Server 2010 Management Pack, you’ll find that this is not the case. Specifically, alerts

are not automatically raised by monitor state changes. The Correlation Engine may determine the

best alert to raise.

Health Model The class hierarchy imported into Operations Manager by the

Exchange Server 2010 Management Pack is extensive. The class hierarchy includes class

relationships that define component dependencies throughout the system. By defining these

component dependencies in the object representation of the product, the Exchange Server 2010

Management Pack is able to better understand the health of the Exchange organization. For

example, if the Exchange Server 2010 Management Pack identifies Active Directory as offline, it

will also report that Exchange messaging is not fully functional.

Timing The Correlation Engine works in 90-second intervals. When state change events for

multiple monitors come in at the same time, it waits to see whether anything else potentially

related to the failure is detected so that it can make the most effective determination of the root

cause.

Correlation Algorithm

Overview of the Correlation Engine process

1. First, it connects to the Operations Manager SDK service to download the Health Model

hierarchy and instance state (on service startup only, or as needed if errors require it).

2. Next, it queries Operations Manager for the latest state change events related to entities in

the Exchange Management Pack.

3. If new NSI state changes are detected, then it raises alerts for them.

4. KHI monitors are then evaluated, and "chains" of red KHI monitors are isolated. These

"chains" indicate issues where a dependency has failed and is impacting dependent

processes. Recognizing these relationships is the key step.

5. Alerts are raised for the root cause monitor in the KHI chain.

14

6. It then waits 90 seconds, and then starts over at step 2 above.

Additional points of interest regarding the correlation engine process

If the "chain" of KHIs includes both error and warning monitors, then the alert is raised as an

error, regardless of the class of the root cause monitor. For example, if a top-level process

defines an error monitor to catch failure cases, and if it is correlated to a warning monitor in a

dependency, then the alert will be raised against the dependency, but it will be marked as an

error instead of a warning.

Not every class relationship is used for alert correlation. See the Appendix: Class Hierarchy

later in this guide for the specific relationships used by the Correlation Engine.

The KHI chain, including any forensic monitors, is included in the Alert Context field

available in the properties of the final alert. This allows inspection of the monitors correlated

to the given alert and, in the case of alerts firing from dependency monitors, is required to

determine the specific failure referenced by the alert.

Monitors in maintenance mode are simply skipped when evaluating the health model.

What is and is not Affected by Alert Correlation

A key point to understand about the Exchange Server 2010 Management Pack, and the

Correlation Engine in particular, is what the Correlation Engine affects, and what it doesn’t affect.

The following items are different due to the Correlation Engine:

Monitors are configured not to alert automatically on state change events. This allows the

Correlation Engine to determine the best alert to raise (as described above).

The Exchange Server 2010 Management Pack doesn't raise Exchange alerts that correspond

to the health of your environment when the Correlation Engine is stopped. If the Correlation

Engine is stopped, a general alert is raised to notify you that the Correlation Engine is not

running.

The following items are not different due to the presence of the Correlation Engine:

Overrides still work as expected; you can change certain values or disable monitors just as

you do today.

Monitors/objects in maintenance mode are skipped by the Correlation Engine. No special

consideration is required since the monitors don’t raise state change events for consumption

by the Correlation Engine.

Per-monitor alert rules were added to the Exchange Server 2010 Management Pack. Per-

monitor alert rules allow monitoring personnel to enter company-specific notes for a given

alert into the Company Knowledge field, even when the alert rules aren’t used to raise alerts

for their corresponding monitors.

Other management packs are not affected by the presence of the Correlation Engine.

In summary, keep in mind that it’s just the "monitor state change to alert" step that is enhanced by

correlation.

Operational Notes

Since the Correlation Engine needs to maintain the instance space of the management group in

memory to determine related monitors/alerts, its memory footprint is relative to the number of

15

instances in the management group. In plain terms, the more Exchange servers and databases

you have, the more memory it will require.

In observing environments at Microsoft, the Correlation Engine scales roughly at about 5

megabytes per monitored Exchange server. There are factors that can drive this number up or

down, but it’s a good starting point toward understanding the resource impact on the server

hosting the service.

As stated above, the preferred location for the service is on the RMS role given the close SDK

interaction and core functionality of raising alerts.

Appendix: ReportsThe following reports are included in the Microsoft Exchange Server 2010 Management Pack.

Allow up to 30 minutes for reports from a new management pack to appear in the Reporting

console.

Report Description

Service Availability Models availability for clients that access their

mailboxes through Microsoft Office Outlook and

Outlook Web App. It also models mailbox

database availability.

Client Access Availability Models the availability of each client access

protocol running on a Client Access server. For

each, it models availability at the server, site,

and datacenter (management group) level.

Unified Messaging Availability Models the availability of the Local Voice

Unified Messaging task.

SMTP (Client Submission) Availability Models client SMTP submission availability as

measured by synthetic transactions.

Outlook Client Performance Models client performance statistics based on

the performance data submitted to Exchange

by Outlook.

Hourly Mailflow Statistics Models statistics from message tracking logs to

provide information on mail flow latency by

hour.

Daily Mailflow Statistics Models statistics from message tracking logs to

provide information on mail flow latency by day.

Distribution Group Usage Models usage of distribution groups.

Top Users Models usage data for clients with the most

16

Report Description

messages sent, received, and failed.

Availability Reporting CalculationsDefinitions

Mailbox Database - Daily Availability A mailbox database is available when one of its

copies is mounted. The state of a mailbox database and its copies is reported by Operations

Manager. The daily availability is the percent of the day that the mailbox database is

available.

Outlook Web App - Daily Availability Both the server-level and site-level Outlook Web App

states are reported by Operations Manager monitors. The Outlook Web App Service class is

considered available when at least one Outlook Web App server is available.

Outlook – Daily Availability Both the server-level and site-level Outlook states are reported

by Operations Manager monitors. The Outlook Service class is considered available when at

least one Outlook server is available.

Calculated Availabilities

Site Mailbox Database - Daily Availability A site’s mailbox database availability is an

average of mailbox database availabilities.

Site - Daily Availability A site’s availability is its mailbox database availability minus the

average of its Outlook Web App Service class and Outlook Service class unavailability.

Datacenter - Daily Availability A datacenter’s availability is an average of site availabilities.

Monthly Availability The monthly availability of an entity is the sum of its daily availabilities

divided by the number of days in the month.

Raw Uptime vs. Availability

Raw Uptime = 1 – Downtime

Availability = Raw Uptime + Planned Maintenance

Maintenance Mode

When an entity in Operations Manager is in maintenance mode, its monitors are in either the

unplanned maintenance state or the planned maintenance state. This maintenance state is

recorded instead of the monitor’s green, yellow, or red state. Since the monitors are unloaded

while in maintenance mode, the actual availability of the component cannot be measured. Due to

this, Operations Manager planned maintenance is counted as uptime in the availability

calculation, and unplanned maintenance is counted as downtime.

Availability Database Tables

The availability data is stored in the Operations Manager data warehouse database

(OperationsManagerDW). The Service Level Agreement (SLA) report uses data from the

Exchange2010.vAvailabilityObjListV14 and Exchange2010.vAvailabilityOnObjectDailyV14 tables:

17

Exchange2010.vAvailabilityObjListV14 is a list of objects that have measured availabilities.

These objects are mailbox databases, Outlook Web Access (OWA)/Outlook servers, and the

OWA/Outlook service objects (one per site). The name of each object's site is stored in this

table.

Exchange2010.vAvailabilityOnObjectDailyV14 contains daily availabilities as percentages for

each object in Exchange2010.vAvailabilityObjListV14.

Appendix: Synthetic TransactionsThe following synthetic transitions are included in the Microsoft Exchange Server 2010

Management Pack.

Task Command Frequency

Unified

Messaging –

Remote Voice

Test-UMConnectivity -UMIPgateway:{gatewayname} -

Phone:{extension}

5 minutes

Unified

Messaging –

Local Voice

Test-UMConnectivity 5 minutes

Database

Replication

Test-ReplicationHealth 5 minutes

Search Test-ExchangeSearch 20 minutes

Remote

PowerShell –

External

Test-PowerShellConnectivity -TestType:External -

TrustAnySSLCertificate:$true

10 minutes

Remote

PowerShell –

Internal

Test-PowerShellConnectivity -TestType:Internal -

TrustAnySSLCertificate:$true

10 minutes

Mailbox

Replication

Service

Test-MRSHealth 3 minutes

Outlook – Internal Test-OutlookConnectivity -RpcTestType:Server -

TrustAnySSLCert:$true

5 minutes

Outlook –

AutoDiscovery

Test-OutlookConnectivity -Protocol:Tcp -

GetDefaultsFromAutoDiscover:$true -TrustAnySSLCert:

$true

5 minutes

Web Services Test-WebServicesConnectivity -TrustAnySSLCertificate:

$true -LightMode:$true

5 minutes

18

Task Command Frequency

Post Office

Protocol (POP)

Test-PopConnectivity -MonitoringContext:$true -

ConnectionType:2 -TrustAnySSLCertificate:$true -

LightMode:$true

5 minutes

Exchange Control

Panel - External

Test-EcpConnectivity -TestType:External -

MonitoringContext:$true -TrustAnySSLCertificate:$true -

LightMode:$true

5 minutes

Exchange Control

Panel - Internal

Test-EcpConnectivity -TestType:Internal -

TrustAnySSLCertificate:$true -LightMode:$true

5 minutes

Outlook Web

Application –

External

Test-OwaConnectivity -TestType:External -


5 minutes

Outlook Web

Application –

Internal

Test-OwaConnectivity -TestType:Internal -


5 minutes

Internet Message

Access Protocol

(IMAP)

Test-ImapConnectivity - ConnectionType:2 -


5 minutes

Outlook Web

Services

Test-OutlookWebServices 3 minutes

ActiveSync Test-ActiveSyncConnectivity - MonitoringInstance:

$ScriptContext.ManagementGroupName -


5 minutes

EdgeSync Test-EdgeSynchronization 15 minutes

Appendix: ScriptsThe following scripts are included in the Microsoft Exchange Server 2010 Management Pack.

Script Purpose

Exchange_Execute_Diagnostic_Task.js Executes synthetic transactions

through PowerShell using the

Exchange Monitoring Service.

GetSite.js Returns the Active Directory site

name used by

the Exchange server.

19

Script Purpose

MicrosoftExchangeServerRoleDiscovery.js Discovery script that creates

Exchange 2010 server role

instances.

MicrosoftExchangeOrganizationDiscovery.js Discovery script that creates site-

level "Service" entities for rollup of

state by services used by

Exchange, including but not

limited to, the Post Office Protocol

3 (POP3), Internet Messaging

Access Protocol 4 (IMAP4), and

Outlook Web App services.

MicrosoftExchangeClientAccessComponentDiscovery.js Discovery script for Client Access

server entities.

MicrosoftExchangeEdgeTransportComponentDiscovery.js Discovery script for Edge

Transport server entities.

MicrosoftExchangeHubTransportComponentDiscovery.js Discovery script for Hub Transport

server entities.

MicrosoftExchangeMailboxComponentDiscovery.js Discovery script for Mailbox server

entities.

MicrosoftExchangeMailboxDiscovery.ps1 Discovery script for Mailbox High-

Availability and Database

Availability Groups.

MicrosoftExchangeDomainControllerDiscovery.ps1 Discovery script for

Active Directory topology used by

Active Directory driver monitoring.

MicrosoftExchangeUnifiedMessagingComponentDiscovery.js Discovery script for Unified

Messaging entities.

MicrosoftExchangeMonitoringRoleServiceBaseDiscovery.js Discovery script for the Monitoring

role components, which includes

the Correlation Engine.

MicrosoftExchangeMonitoringCorrelationEngineDiscovery.js Discovery script for the

Correlation Engine.

20

Appendix: Objects the Management Pack DiscoversThe Microsoft Exchange Server 2010 Management Pack discovers the object types described in

the following table. All discovery rules are enabled by default.

Discovery Objects

Microsoft.Exchange.2010.Client

AccessRole.DiscoveryRule

Microsoft.Exchange.2010.Server



Microsoft.Exchange.2010.ClientAccessRole



Microsoft.Exchange.2010.CommonRole

Microsoft.Exchange.2010.Edge

TransportRole.DiscoveryRule




Microsoft.Exchange.2010.EdgeTransportRole




Microsoft.Exchange.2010.HubTr

ansportRole.DiscoveryRule




Microsoft.Exchange.2010.HubTransportRole




Microsoft.Exchange.2010.Mailb

oxRole.DiscoveryRule




Microsoft.Exchange.2010.MailboxRole




Microsoft.Exchange.2010.Unifie

dMessagingRole.DiscoveryRule




Microsoft.Exchange.2010.UnifiedMessagingRole

Microsoft.Exchange.2010.Unifie Microsoft.Exchange.2010.CommonRole

21

Discovery Objects


Microsoft.Exchange.2010.Organ

ization.DiscoveryRule

Microsoft.Exchange.2010.Organization



Microsoft.Exchange.2010.ClientAccessActiveSyncService



Microsoft.Exchange.2010.ClientAccessOutlookWebAccessSer

vice



Microsoft.Exchange.2010.ClientAccessExchangeControlPanel

Service



Microsoft.Exchange.2010.ClientAccessWebServicesService



Microsoft.Exchange.2010.ClientAccessAvailabilityServicesSer

vice



Microsoft.Exchange.2010.ClientAccessOfflineAddressBookSer

vice



Microsoft.Exchange.2010.ClientAccessImap4Service



Microsoft.Exchange.2010.ClientAccessPop3Service



Microsoft.Exchange.2010.ClientAccessTestConfigService



Microsoft.Exchange.2010.EdgeTransportService



Microsoft.Exchange.2010.HubTransportService



Microsoft.Exchange.2010.MailboxMapiService



Microsoft.Exchange.2010.MailboxTestConfigService



Microsoft.Exchange.2010.ClientAccessMailboxReplicationServ

icesService



Microsoft.Exchange.2010.UnifiedMessagingService

22

Discovery Objects



Microsoft.Exchange.2010.CommonRemotePowerShellService


AccessComponent.DiscoveryRu

le

Microsoft.Exchange.2010.ClientAccessActiveSync



le

Microsoft.Exchange.2010.ClientAccessAutoDiscovery



le

Microsoft.Exchange.2010.ClientAccessFileDistributionService



le

Microsoft.Exchange.2010.ClientAccessImap4



le

Microsoft.Exchange.2010.ClientAccessInformationWorker



le

Microsoft.Exchange.2010.ClientAccessOutlookWebAccess



le

Microsoft.Exchange.2010.ClientAccessExchangeControlPanel



le

Microsoft.Exchange.2010.ClientAccessPop3



le

Microsoft.Exchange.2010.ClientAccessServiceMonitoring



le

Microsoft.Exchange.2010.ClientAccessWebServices



le

Microsoft.Exchange.2010.ClientAccessAvailabilityService

Microsoft.Exchange.2010.Client Microsoft.Exchange.2010.ClientAccessOfflineAddressBook

23

Discovery Objects


le



le

Microsoft.Exchange.2010.ClientAccessUnifiedMessaging



le

Microsoft.Exchange.2010.ClientAccessTestConfig



le

Microsoft.Exchange.2010.ClientAccessMailboxReplicationServ

ice



le

Microsoft.Exchange.2010.CommonActiveDirectoryAccess



le

Microsoft.Exchange.2010.CommonAllServerRoles



le

Microsoft.Exchange.2010.CommonBestPracticeAnalyzer



le

Microsoft.Exchange.2010.CommonFileDistributionService



le

Microsoft.Exchange.2010.CommonProblemAnalysis



le

Microsoft.Exchange.2010.CommonServer



le

Microsoft.Exchange.2010.CommonServiceMonitoring



le

Microsoft.Exchange.2010.CommonRemotePowerShell

Microsoft.Exchange.2010.Client Microsoft.Exchange.2010.CommonConfigurationAuthorization

24

Discovery Objects


le



le

Microsoft.Exchange.2010.CommonProvisioningBroker



le

Microsoft.Exchange.2010.ClientAccessOutlookService



le

Microsoft.Exchange.2010.ClientAccessOutlook



le

Microsoft.Exchange.2010.ClientAccessOutlookServerService



le

Microsoft.Exchange.2010.ClientAccessOutlookLocalServer



le

Microsoft.Exchange.2010.ClientAccessOutlookPerformanceSe

rvice



le

Microsoft.Exchange.2010.ClientAccessOutlookInstancePerfor

mance



le

Microsoft.Exchange.2010.ClientAccessOutlookDirectory



le

Microsoft.Exchange.2010.CommonTransportThrottlingClient


TransportComponent.Discovery

Rule

Microsoft.Exchange.2010.EdgeTransportAgentsAddressRewrit

e



Rule

Microsoft.Exchange.2010.EdgeTransportAgentsAttachmentFilt

er

Microsoft.Exchange.2010.Edge Microsoft.Exchange.2010.EdgeTransportAgentsConnectionFilt

25

Discovery Objects


Rule

er



Rule

Microsoft.Exchange.2010.EdgeTransportAgentsContentFilter



Rule

Microsoft.Exchange.2010.EdgeTransportAgentsProtocolAnalys

is



Rule

Microsoft.Exchange.2010.EdgeTransportAgentsRecipientFilter



Rule

Microsoft.Exchange.2010.EdgeTransportAgentsSenderFilter



Rule

Microsoft.Exchange.2010.EdgeTransportAgentsSenderId



Rule

Microsoft.Exchange.2010.EdgeTransportDsn



Rule

Microsoft.Exchange.2010.EdgeTransportMessageSecurity



Rule

Microsoft.Exchange.2010.EdgeTransportQueues



Rule

Microsoft.Exchange.2010.EdgeTransportServiceMonitoring



Rule




Rule


Microsoft.Exchange.2010.Edge Microsoft.Exchange.2010.CommonBestPracticeAnalyzer

26

Discovery Objects


Rule



Rule

Microsoft.Exchange.2010.CommonExtensibleStorageEngine



Rule




Rule

Microsoft.Exchange.2010.CommonTransport



Rule

Microsoft.Exchange.2010.CommonTransportAgents



Rule

Microsoft.Exchange.2010.CommonTransportLogSearch



Rule




Rule


Microsoft.Exchange.2010.Com

monDomainController.Discovery

Rule

Microsoft.Exchange.2010.CommonADAccessDomainControlle

rService

Microsoft.Exchange.2010.Com

monDomainController.Discovery

Rule

Microsoft.Exchange.2010.CommonDomainController


ansportComponent.DiscoveryR

ule

Microsoft.Exchange.2010.HubTransportAgentsConnectionFilte

r



ule

Microsoft.Exchange.2010.HubTransportAgentsContentFilter

Microsoft.Exchange.2010.HubTr Microsoft.Exchange.2010.HubTransportAgentsMessagingPolic

27

Discovery Objects


ule

ies



ule

Microsoft.Exchange.2010.HubTransportAgentsProtocolAnalysi

s



ule

Microsoft.Exchange.2010.HubTransportAgentsRecipientFilter



ule

Microsoft.Exchange.2010.HubTransportAgentsSenderFilter



ule

Microsoft.Exchange.2010.HubTransportAgentsSenderId



ule

Microsoft.Exchange.2010.HubTransportAgentsSMS



ule

Microsoft.Exchange.2010.HubTransportDsn



ule

Microsoft.Exchange.2010.HubTransportEdgeSync



ule

Microsoft.Exchange.2010.HubTransportQueues



ule

Microsoft.Exchange.2010.HubTransportServiceMonitoring



ule

Microsoft.Exchange.2010.HubTransportStoreDriver



ule


Microsoft.Exchange.2010.HubTr Microsoft.Exchange.2010.CommonAllServerRoles

28

Discovery Objects


ule



ule




ule




ule




ule

Microsoft.Exchange.2010.CommonTransport



ule

Microsoft.Exchange.2010.CommonTransportAgents



ule

Microsoft.Exchange.2010.CommonTransportLogSearch



ule




ule




ule




ule

Microsoft.Exchange.2010.CommonConfigurationAuthorization



ule


Microsoft.Exchange.2010.HubTr Microsoft.Exchange.2010.CommonTransportThrottlingClient

29

Discovery Objects


ule


oxComponent.DiscoveryRule

Microsoft.Exchange.2010.Mailbox.ServiceMonitoring



Microsoft.Exchange.2010.MailboxSystemAttendant



Microsoft.Exchange.2010.MailboxTestConfig



Microsoft.Exchange.2010.MailboxUnifiedMessaging

































Microsoft.Exchange.2010.MailboxTransportThrottlingServer


ox.MdbOwningServerLocalEntit

Microsoft.Exchange.2010.Mailbox.DatabaseService

30

Discovery Objects

yDiscoveryRule



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyMounted



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopy



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyPerformance



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesPerformanc

e



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyCorruption



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesCorruption



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyIntegritySupp

ression



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesIntegritySu

ppression



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopySubmission



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesSubmission



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyReplication



Microsoft.Exchange.2010.Mailbox.DatabaseCopiesReplication

31

Discovery Objects

yDiscoveryRule



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyReplay



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesReplay



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ReplayService



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseRedundancy



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseSearchCopy



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ContentIndexingService



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ClusterService



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseAvailabilityGroup



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailSubmission



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.InformationStore



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.InformationStorePerformanc

e



Microsoft.Exchange.2010.Mailbox.Assistants

32

Discovery Objects

yDiscoveryRule



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.Network



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllDatabaseServices



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ManyDatabaseServices



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ClusterQuorumGroup



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ClusterFsw



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllClusterQuorumGroups



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllClusterFsws



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AcrossCluster



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllAcrossClusters



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllNetworks



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesFailed



Microsoft.Exchange.2010.Mailbox.MailboxMonitoring

33

Discovery Objects

yDiscoveryRule



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseSearchService



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopySearchable



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyEdbLogicalDi

sk



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyLogLogicalDi

sk



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.PublicFolderDatabase



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.PublicFolderDatabasePerfor

mance



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.PublicFolderDatabaseEdbL

ogicalDisk



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.PublicFolderDatabaseLogLo

gicalDisk



yDiscoveryRule


skPerformance



yDiscoveryRule


skPerformance



yDiscoveryRule


skSpace




skSpace

34

Discovery Objects

yDiscoveryRule



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailboxOnDatabase



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailboxOnDbCopy



yDiscoveryRule


ogicalDiskSpace



yDiscoveryRule


gicalDiskSpace



yDiscoveryRule


ogicalDiskPerformance



yDiscoveryRule


gicalDiskPerformance



yDiscoveryRule

Microsoft.Exchange.2010.Mailbox.VirusScan


ox.MdbOwningServerRemoteEn

tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseService



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyMounted



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopy



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyPerformance



Microsoft.Exchange.2010.Mailbox.DatabaseCopiesPerformanc

e

35

Discovery Objects

tityDiscoveryRule



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyCorruption



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesCorruption



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyIntegritySupp

ression



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesIntegritySu

ppression



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopySubmission



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesSubmission



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyReplication



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesReplication



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopyReplay



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesReplay



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ReplayService



Microsoft.Exchange.2010.Mailbox.DatabaseRedundancy

36

Discovery Objects

tityDiscoveryRule



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseSearchCopy



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ContentIndexingService



tityDiscoveryRule




tityDiscoveryRule




tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailSubmission



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.InformationStore



tityDiscoveryRule


e



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.Assistants



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.Network



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllDatabaseServices



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ManyDatabaseServices



Microsoft.Exchange.2010.Mailbox.ClusterQuorumGroup

37

Discovery Objects

tityDiscoveryRule



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.ClusterFsw



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllClusterQuorumGroups



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllClusterFsws



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AcrossCluster



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllAcrossClusters



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.AllNetworks



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopiesFailed



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailboxMonitoring



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseSearchService



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.DatabaseCopySearchable



tityDiscoveryRule


sk




sk

38

Discovery Objects

tityDiscoveryRule



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.PublicFolderDatabase



tityDiscoveryRule


mance



tityDiscoveryRule


ogicalDisk



tityDiscoveryRule


gicalDisk



tityDiscoveryRule


skPerformance



tityDiscoveryRule


skPerformance



tityDiscoveryRule


skSpace



tityDiscoveryRule


skSpace



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailboxOnDatabase



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.MailboxOnDbCopy



tityDiscoveryRule


ogicalDiskSpace




39

Discovery Objects

tityDiscoveryRule gicalDiskSpace



tityDiscoveryRule


ogicalDiskPerformance



tityDiscoveryRule


gicalDiskPerformance



tityDiscoveryRule

Microsoft.Exchange.2010.Mailbox.VirusScan


dMessagingComponent.Discove

ryRule

Microsoft.Exchange.2010.UnifiedMessaging



ryRule

Microsoft.Exchange.2010.UnifiedMessagingPerformanceRepo

rting



ryRule

Microsoft.Exchange.2010.UnifiedMessagingServiceMonitoring



ryRule

Microsoft.Exchange.2010.UnifiedMessaging.Availability.Servic

e



ryRule

Microsoft.Exchange.2010.UnifiedMessaging.Availability.Gatew

ay



ryRule

Microsoft.Exchange.2010.UnifiedMessaging.GeneralSensor.Tr

ansportFailures



ryRule

Microsoft.Exchange.2010.UnifiedMessaging.SubComponent.P

artnerTranscriptionFailures



ryRule

Microsoft.Exchange.2010.UnifiedMessaging.GeneralSensor.M

ailboxFailures



Microsoft.Exchange.2010.UnifiedMessaging.SubComponent.Pi

peline

40

Discovery Objects

ryRule



ryRule

Microsoft.Exchange.2010.UnifiedMessaging.SubComponent.P

rotectedVoiceMessage



ryRule




ryRule




ryRule




ryRule

Microsoft.Exchange.2010.CommonFileDistributionService



ryRule




ryRule




ryRule




ryRule




ryRule




ryRule




Microsoft.Exchange.2010.CommonTransportThrottlingClient

41

Discovery Objects

ryRule



ryRule

Microsoft.Exchange.2010.UnifiedMessagingService



ryRule

Microsoft.Exchange.2010.CommonRemotePowerShellService

Microsoft.Exchange.2010.Correl

ationEngineRole.DiscoveryRule

Microsoft.Exchange.2010.CorrelationEngineRole

Microsoft.Exchange.2010.Monit

oringCorrelationEngine.Discover

yRule

Microsoft.Exchange.2010.MonitoringCorrelationEngine


oxServers.InstanceGroup.Disco

veryRule

Microsoft.Exchange.2010.MailboxServers.InstanceGroup

Microsoft.Exchange.2010.AllMai

lboxAndHAServiceEntities.Insta

nceGroup.DiscoveryRule

Microsoft.Exchange.2010.AllMailboxAndHAServiceEntities.Inst

anceGroup


oxServers.ComputerGroup.Disc

overyRule

Microsoft.Exchange.2010.MailboxServers.ComputerGroup

Microsoft.Exchange.2010.AllSer

vers.InstanceGroup.DiscoveryR

ule

Microsoft.Exchange.2010.AllServers.InstanceGroup


vers.ComputerGroup.Discovery

Rule

Microsoft.Exchange.2010.AllServers.ComputerGroup


AccessServers.InstanceGroup.

DiscoveryRule

Microsoft.Exchange.2010.ClientAccessServers.InstanceGroup


AccessServers.ComputerGroup.

DiscoveryRule

Microsoft.Exchange.2010.ClientAccessServers.ComputerGrou

p


TransportServers.InstanceGrou

p.DiscoveryRule

Microsoft.Exchange.2010.EdgeTransportServers.InstanceGrou

p

42

Discovery Objects


TransportServers.ComputerGro

up.DiscoveryRule

Microsoft.Exchange.2010.EdgeTransportServers.ComputerGro

up

Microsoft.Exchange.2010.Trans

portServers.InstanceGroup.Disc

overyRule

Microsoft.Exchange.2010.TransportServers.InstanceGroup


ansportServers.InstanceGroup.

DiscoveryRule

Microsoft.Exchange.2010.HubTransportServers.InstanceGroup


ansportServers.ComputerGroup

.DiscoveryRule

Microsoft.Exchange.2010.HubTransportServers.ComputerGro

up


dMessagingServers.InstanceGr

oup.DiscoveryRule

Microsoft.Exchange.2010.UnifiedMessagingServers.InstanceG

roup


dMessagingServers.ComputerG

roup.DiscoveryRule

Microsoft.Exchange.2010.UnifiedMessagingServers.Computer

Group

Microsoft.Exchange.2010.AllEnti

ties.InstanceGroup.DiscoveryRu

le

Microsoft.Exchange.2010.AllEntities.InstanceGroup


versWithRoles.InstanceGroup.D

iscoveryRule

Microsoft.Exchange.2010.AllServersWithRoles.InstanceGroup

Microsoft.Exchange.2010.Serve

rsWithClientAccessRole.Instanc

eGroup.DiscoveryRule

Microsoft.Exchange.2010.ServersWithClientAccessRole.Instan

ceGroup


rsWithEdgeTransportRole.Insta

nceGroup.DiscoveryRule

Microsoft.Exchange.2010.ServersWithEdgeTransportRole.Inst

anceGroup


rsWithHubTransportRole.Instan

ceGroup.DiscoveryRule

Microsoft.Exchange.2010.ServersWithHubTransportRole.Insta

nceGroup


rsWithMailboxRole.InstanceGro

up.DiscoveryRule

Microsoft.Exchange.2010.ServersWithMailboxRole.InstanceGr

oup

43

Discovery Objects


rsWithUnifiedMessagingRole.In

stanceGroup.DiscoveryRule

Microsoft.Exchange.2010.ServersWithUnifiedMessagingRole.I

nstanceGroup


ationEngineServers.InstanceGr

oup.DiscoveryRule

Microsoft.Exchange.2010.CorrelationEngineServers.InstanceG

roup


ationEngineServers.ComputerG

roup.DiscoveryRule

Microsoft.Exchange.2010.CorrelationEngineServers.Computer

Group


ox.DatabaseServiceRelationshi

pDiscoveryRule

ExchangeReverseRollup_Microsoft.Exchange.2010.Mailbox.D

atabaseService.Contains.Microsoft.Exchange.2010.Mailbox.D

atabaseCopyMounted

ExchangeReverseRollup_Microsoft.Exchange.2010.Mailbox.M

anyDatabaseServices.Contains.Microsoft.Exchange.2010.Mail

box.DatabaseService

Microsoft.Exchange.2010.Mailbox.AllDatabaseServices.Contai

ns.Microsoft.Exchange.2010.Mailbox.DatabaseService


ox.DatabaseCopyEdbLogicalDis

kRelationshipDiscoveryRule


atabaseCopiesLogicalDisk.Contains.Microsoft.Exchange.2010.

Mailbox.DatabaseCopyEdbLogicalDiskPerformance



Mailbox.DatabaseCopyEdbLogicalDiskSpace

Microsoft.Exchange.2010.Mailbox.DatabaseCopyPerformance.

Contains.Microsoft.Exchange.2010.Mailbox.DatabaseCopyEdb

LogicalDiskPerformance


ox.DatabaseCopyLogLogicalDis

kRelationshipDiscoveryRule



Mailbox.DatabaseCopyLogLogicalDiskPerformance



Mailbox.DatabaseCopyLogLogicalDiskSpace


Contains.Microsoft.Exchange.2010.Mailbox.DatabaseCopyLog

LogicalDiskPerformance


ox.DatabaseCopyCorruptionRel


atabaseCopiesCorruption.Contains.Microsoft.Exchange.2010.

44

Discovery Objects

ationshipDiscoveryRule Mailbox.DatabaseCopyCorruption

Microsoft.Exchange.2010.Mailbox.DatabaseCopy.Contains.Mic

rosoft.Exchange.2010.Mailbox.DatabaseCopyCorruption


ox.DatabaseCopyIntegrityRelati

onshipDiscoveryRule


atabaseCopiesIntegritySuppression.Contains.Microsoft.Excha

nge.2010.Mailbox.DatabaseCopyIntegritySuppression


rosoft.Exchange.2010.Mailbox.DatabaseCopyIntegritySuppres

sion


ox.DatabaseCopyPerformanceR

elationshipDiscoveryRule


atabaseCopiesPerformance.Contains.Microsoft.Exchange.201

0.Mailbox.DatabaseCopyPerformance


ox.DatabaseCopyReplayRelatio

nshipDiscoveryRule


atabaseCopiesReplay.Contains.Microsoft.Exchange.2010.Mail

box.DatabaseCopyReplay


rosoft.Exchange.2010.Mailbox.DatabaseCopyReplay


rosoft.Exchange.2010.Mailbox.ReplayService


ox.DatabaseCopyReplicationRel

ationshipDiscoveryRule


atabaseCopiesReplication.Contains.Microsoft.Exchange.2010.

Mailbox.DatabaseCopyReplication


rosoft.Exchange.2010.Mailbox.DatabaseCopyReplication


ox.DatabaseCopySearchableRe

lationshipDiscoveryRule


atabaseSearchService.Contains.Microsoft.Exchange.2010.Mai

lbox.DatabaseCopySearchable

Microsoft.Exchange.2010.Mailbox.DatabaseCopySearchable.

Contains.Microsoft.Exchange.2010.Mailbox.ContentIndexingS

ervice

Microsoft.Exchange.2010.Mailbox.DatabaseCopySearchable.

Contains.Microsoft.Exchange.2010.Mailbox.DatabaseService


ox.DatabaseCopySubmissionRe



atabaseCopiesSubmission.Contains.Microsoft.Exchange.2010.

Mailbox.DatabaseCopySubmission


rosoft.Exchange.2010.Mailbox.DatabaseCopySubmission

45

Discovery Objects


ox.DatabaseCopiesFailedRelati

onshipDiscoveryRule


atabaseCopiesFailed.Contains.Microsoft.Exchange.2010.Mailb

ox.DatabaseCopy


ox.DatabaseAvailabilityGroupRe


ExchangeReverseRollup_Microsoft.Exchange.2010.Mailbox.Al

lAcrossClusters.Contains.Microsoft.Exchange.2010.Mailbox.Ac

rossCluster


lClusterFsws.Contains.Microsoft.Exchange.2010.Mailbox.Clust

erFsw


lClusterQuorumGroups.Contains.Microsoft.Exchange.2010.Ma

ilbox.ClusterQuorumGroup


lNetworks.Contains.Microsoft.Exchange.2010.Mailbox.Network


atabaseAvailabilityGroup.Contains.Microsoft.Exchange.2010.

Mailbox.AllClusterFsws


atabaseAvailabilityGroup.Contains.Microsoft.Exchange.2010.

Mailbox.ClusterService

Microsoft.Exchange.2010.Mailbox.AllAcrossClusters.Contains.


Microsoft.Exchange.2010.Mailbox.AllAcrossClusters.Contains.


Microsoft.Exchange.2010.Mailbox.DatabaseCopyMounted.Con

tains.Microsoft.Exchange.2010.Mailbox.ClusterService

Microsoft.Exchange.2010.Mailbox.DatabaseRedundancy.Cont

ains.Microsoft.Exchange.2010.Mailbox.ClusterService

Microsoft.Exchange.2010.Mailbox.DatabaseRedundancy.Cont

ains.Microsoft.Exchange.2010.Mailbox.DatabaseCopy


ox.SearchRelationshipDiscovery

Rule

Microsoft.Exchange.2010.Mailbox.ContentIndexingService.Co

ntains.Microsoft.Exchange.2010.Mailbox.InformationStorePerf

ormance

Microsoft.Exchange.2010.Mailbox.DatabaseSearchCopy.Cont

ains.Microsoft.Exchange.2010.Mailbox.ContentIndexingServic

e


ains.Microsoft.Exchange.2010.Mailbox.DatabaseCopyCorrupti

46

Discovery Objects

on


ains.Microsoft.Exchange.2010.Mailbox.DatabaseCopyIntegrity

Suppression


ains.Microsoft.Exchange.2010.Mailbox.DatabaseService


ox.InformationStoreRelationship

DiscoveryRule

Microsoft.Exchange.2010.Mailbox.Assistants.Contains.Microso

ft.Exchange.2010.Mailbox.InformationStore

Microsoft.Exchange.2010.Mailbox.DatabaseCopyMounted.Con

tains.Microsoft.Exchange.2010.Mailbox.InformationStore


Contains.Microsoft.Exchange.2010.Mailbox.InformationStoreP

erformance


e.Contains.Microsoft.Exchange.2010.Mailbox.InformationStore

Microsoft.Exchange.2010.Mailbox.MailSubmission.Contains.Mi

crosoft.Exchange.2010.Mailbox.InformationStore

Microsoft.Exchange.2010.Mailbox.ReplayService.Contains.Mic

rosoft.Exchange.2010.Mailbox.InformationStore

Microsoft.Exchange.2010.Mailbox.VirusScan.Contains.Microso

ft.Exchange.2010.Mailbox.InformationStore


ox.MailboxRelationshipDiscover

yRule

ExchangeReverseRollup_Microsoft.Exchange.2010.Mailbox.M

ailboxOnDatabase.Contains.Microsoft.Exchange.2010.Mailbox

.MailboxOnDbCopy

Microsoft.Exchange.2010.Mailbox.MailboxOnDatabase.Contai

ns.Microsoft.Exchange.2010.Mailbox.DatabaseService

Microsoft.Exchange.2010.Mailbox.MailboxOnDbCopy.Contains

.Microsoft.Exchange.2010.Mailbox.DatabaseCopyMounted


ox.PublicFolderRelationshipDisc

overyRule

Microsoft.Exchange.2010.Mailbox.PublicFolderDatabase.Cont

ains.Microsoft.Exchange.2010.Mailbox.InformationStore


mance.Contains.Microsoft.Exchange.2010.Mailbox.Information

StorePerformance


mance.Contains.Microsoft.Exchange.2010.Mailbox.PublicFold

erDatabase


47

Discovery Objects


erDatabaseEdbLogicalDiskPerformance



erDatabaseLogLogicalDiskPerformance

Microsoft.Exchange.2010.UnifiedMessagingService.Contains.

Microsoft.Exchange.2010.UnifiedMessaging

Microsoft.Exchange.2010.CommonRemotePowerShellService.

Contains.Microsoft.Exchange.2010.CommonRemotePowerSh

ell



Microsoft.Exchange.2010.ClientAccessRole

Appendix: Class HierarchyThe Microsoft Exchange Server 2010 Management Pack uses an extensive class hierarchy. This

extensive class hierarchy helps the Exchange Server 2010 Management Pack to effectively

monitor the health of your Exchange environment.

Use the following diagrams to understand the class hierarchy for the Exchange Server 2010

Management Pack:

Client Access Class Hierarchy

Common Classes Class Hierarchy

Edge Transport Class Hierarchy

Groups Class Hierarchy

Hub Transport Class Hierarchy

Mailbox - High Availability and Mailbox Services Class Hierarchy

Mailbox Class Hierarchy

Roles Class Hierarchy

Unified Messaging Class Hierarchy

48

Client Access Class Hierarchy

49

Hub Transport Class Hierarchy

50

Edge Transport Class Hierarchy

51

Unified Messaging Class Hierarchy

52

Mailbox Class Hierarchy

53

Mailbox - High Availability and Mailbox Services Class Hierarchy

54

Common Classes Class Hierarchy

55

Roles Class Hierarchy

56

Groups Class Hierarchy

Appendix: Alert Correlation RelationshipsThe Microsoft Exchange Server 2010 Management Pack provides a correlation engine to

significantly reduce the number of alerts that may not require an action by the administrator. This

57

reduction in the number of alerts is made possible by the processing of alerts by the Correlation

Engine service. For more information about alert correlation, see Understanding Alert Correlation

earlier in this guide.

Use the following diagrams to better understand alert correlation:

Client Access - On Server Alert Correlation Relationships

Client Access - Server to Site Alert Correlation Relationships

Edge Transport Alert Correlation Relationships

Hub Transport Alert Correlation Relationships

Mailbox - High Availability Alert Correlation Relationships

Mailbox - Information Store Alert Correlation Relationships

Performance, Disks, and Public Folders Alert Correlation Relationships

Unified Messaging Alert Correlation Relationships

58

Client Access - On Server Alert Correlation Relationships

59

Client Access - Server to Site Alert Correlation Relationships

60

Edge Transport Alert Correlation Relationships

61

Hub Transport Alert Correlation Relationships

62

Mailbox - High Availability Alert Correlation Relationships

63

Mailbox - Information Store Alert Correlation Relationships

64

Performance, Disks, and Public Folders Alert Correlation Relationships

65

Unified Messaging Alert Correlation Relationships

66

Date post:	07-Apr-2015
Category:	Documents
Upload:	gasmans
View:	699 times
Download:	0 times

Exchange Server 2010 Management Pack Guide

Documents