Installing and Configuring the Exchange 2003 Management Pack

Installing and Configuringthe Exchange 2003 Management Pack

Dale KoetkeJyoti Kulkarni

Copyright

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and 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.

2003 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Outlook, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Published: May 2003Applies To: Exchange Server 2003

Editor: Alison HirschProduction:: Sean Pohtilla

Table of Contents

INTRODUCTION...........................................................................................................1

Who Should Read This Book?......................................................................................2What Requirements Are Necessary to Complete the Procedures In This Book?..........2

FEATURE OVERVIEW................................................................................................3

Reports...........................................................................................................................4Obtaining Reports......................................................................................................5

INSTALLATION.............................................................................................................7

Importing the Exchange 2003 Management Pack.........................................................7Installing the Exchange 2003 Management Pack Report Update.................................7

CONFIGURATION........................................................................................................9

Servers Updated from Exchange 2000 to Exchange 2003............................................9Mailbox Access Account Configuration.......................................................................9

Creating the Mailbox Access Account.....................................................................10Storing Mailbox Access Account Credentials.........................................................11Creating the Agent Mailbox Account......................................................................13

Service Verification Script Configuration...................................................................15Exchange Traffic Analysis Reports Configuration.....................................................16Mail Flow Verification Scripts Configuration.............................................................17Disk Capacity Planning...............................................................................................19Collecting OS Server Information...............................................................................20Configuring Exchange Mail Queue Thresholds..........................................................20Using Exchange Reports and Views with Exchange Clusters....................................21Best Practices in Configuration...................................................................................22

DEFAULT NOTIFICATION GROUP.......................................................................24

A

SCRIPT DEPENDENCIES..........................................................................................27

B

REPORT DEPENDENCIES........................................................................................35

C

REPORT UPDATES.....................................................................................................45

D

Additional Resources.......................................................................................................49

Introduction

This document describes the purpose, features, configuration, and default notification group of the Microsoft® Exchange 2003 Management Pack.

The Exchange 2003 Server component of Microsoft Operations Manager 2003 Application Management Pack – Microsoft Exchange 2003 Management Pack – is designed to aid you in achieving the highest possible server availability. A key feature of this Exchange 2003 Management Pack is that you can monitor all of your servers running Exchange from a single console or Web page. The Exchange 2003 Management Pack monitors the performance, availability, and security of Microsoft Exchange Server 2003, alerting you to events that have a direct impact on server availability while filtering out events that require no action. Through alerts, knowledge base solutions, and reports, the Exchange 2003 Management Pack helps you correct problems before a catastrophic failure occurs. The Exchange 2003 Management Pack also includes reports that allow you to summarize server availability and analyze trends.

Some of the features of the Exchange 2003 Management Pack are listed below:

Provides a complete Microsoft Exchange solution by monitoring access to Microsoft Active Directory® directory service, Exchange Information Store service, Extensible Storage Engine (ESE), message transport, Exchange clustering, Microsoft Office Outlook® Web Access, and Internet protocols (such as Simple Mail Transfer Protocol, or SMTP; Post Office protocol, or POP; and Internet Message Access Protocol, or IMAP). Detects, alerts, and automatically responds to critical events. The Exchange 2003 Management Pack helps indicate, correct, and in many cases, prevent possible Exchange service outages.

Monitors critical Exchange performance counters. Using performance thresholds and related alert definitions to highlight performance conditions that may indicate service problems or even possible denial of service attacks, Exchange 2003 Management Pack allows you to identify issues before they become critical. Contains an array of scripts to monitor single and cross-server usage, performance, reliability, and configuration. Monitors all configurations of servers running Exchange 2003, including stand–alone servers and servers in clusters, as well as front-end and back-end servers. Increases the availability and performance of your Microsoft Exchange installation. Exchange 2003 Management Pack reduces your total cost of ownership (TCO) by enabling proactive Exchange management.

Who Should Read This Book?Enterprise Exchange Administrators

The Exchange 2003 Management Pack is designed to help e-mail administrators of all experience levels monitor and manage Exchange deployments.

What Requirements Are Necessary to Complete the Procedures In This Book?

For the latest information on hardware and software requirements, see the Microsoft Operations Manager documentation at http://www.microsoft.com/mom/.

http://www.microsoft.com/mom/

Feature Overview 3

Feature Overview

The Exchange 2003 Management Pack monitors events that are placed in the application event log by various components of Exchange, such as Active Directory access, Exchange Information Store, Extensible Storage Engine (ESE), Message Transfer Agent (MTA), Outlook Web Access, Internet protocols, and monitor servers running Exchange in a cluster environment.

The Exchange 2003 Management Pack quickly brings any service outages or configuration problems to your attention, increasing the security, availability, and performance of your Microsoft Exchange installation. It also monitors all key Microsoft Exchange performance metrics to alert you to critical performance issues. Using the Microsoft Operations Manager reporting feature, you can analyze and graph performance data to understand usage trends, to perform accurate load balancing, and to manage system capacity.

The Exchange 2003 Management Pack proactively manages your Exchange installation to avoid costly service outages. For example, the Exchange 2003 Management Pack monitors the following components and operations in your organization:

Vital performance monitor data, which can indicate that the server running Exchange, is running low on resources. Important warning and error events from servers running Exchange 2003 and alerts operators of those events. Disk capacity and alerts operators when disk capacity is running low. Provides knowledge as to which Exchange files are on the affected drives. Exchange services that are expected to be running on a specific server. Exchange database can actually be reached by a MAPI client logon. This verifies both the Exchange database and Active Directory functionality. High queue lengths that are caused by an inability to send e-mail to a destination server.

Monitors and alerts operators to a high number of simultaneous connections, indicating a denial–of–service attack. Errors or resource shortages affecting service levels.

The Exchange 2003 Management Pack features saved public views that are Exchange-specific. These views provide a quick look at the health of your Exchange implementation. The Exchange 2003 Management Pack also includes many Exchange-specific reports.

ReportsThe Exchange 2003 Management Pack includes a variety of reports to help you quickly identify and correct Exchange issues. With these reports, you can analyze and graph performance data to understand usage trends, perform accurate load balancing, and manage system capacity.

Exchange reports cover the following: Exchange 2000 and 2003 Health Monitoring and Operations Reports

You can use the monitoring and operations reports to analyze database sizes, disk usage, mailboxes, server availability, and the configuration of Exchange servers. For example, you can list database sizes for Exchange servers, where database size (in MB) is presented for each server, storage group, and database. The Disk Usage report provides data about servers running Exchange based on disk performance counters, presenting daily averages for each counter. The report on server availability provides the percentage of server availability for Exchange servers during a specified time period and also lists the reasons for unavailability. The Server Configuration report provides configuration information including computer and operating systems configuration and local disks information. The Exchange 2003 Outlook Client Monitoring report gives you the results of analysis data collected by Exchange 2003 servers monitoring Outlook clients for the end user’s experience in terms of response times and errors.

Note Exchange Health Monitoring and Operations reports are only available for servers running Exchange 2000 Server and Exchange

Feature Overview 5

Server 2003. The other Exchange reports are applicable to servers running Exchange 5.5 or later.

Exchange 2000 and 2003 Protocol Usage Reports

The protocol usage reports obtain data about usage and activity levels for the various mail protocols used by Exchange, such as POP3, IMAP4, and SMTP. You can also obtain usage and activity level reports for Exchange components such as the Information Store, Mailbox Store, Public Folder Store, MTA, and Outlook Web Access. These reports use key performance counters for operations conducted within a specific time period.

Exchange 2000 and 2003 Traffic Analysis Reports

The traffic analysis reports summarize Exchange mail traffic patterns by message count and size for both Recipient and Sender domains. For example, the Mail Delivered: Top 100 Sender Domains by Message Size report provides a list of the top 100 sender domains sorted by message size during a specific time period, as reported in the Exchange message tracking logs.

Exchange Capacity Planning Reports

By analyzing your daily client logons and messages sent and received, as well as work queues, these capacity planning reports show the Exchange server resource usage and help you plan for current and future capacity needs.

Exchange Mailbox and Folder Sizes Reports

You can use these reports to monitor the size of Exchange mailboxes and folders and to determine your highest growth areas.

Exchange Performance Analysis Report

The Queue Sizes report summarizes Exchange performance counters and helps you analyze queue performance.

Exchange 5.5 Reports

You can run a number of Exchange 5.5 specific reports to obtain data about operations such as average time for mail delivery, as well as pending replication synchronizations and remaining replication updates. There are also several Exchange 5.5 traffic analysis reports available.

For more information about Exchange reports, see Appendix B “Report Dependencies” and Appendix C “Report Updates.”

6 Installing and Configuring the Exchange 2003 Management Pack

Obtaining ReportsTo obtain reports, do the following:

Note You must have Microsoft Operations Manager and MOM Reporting installed to complete this procedure. For more information on installing Microsoft Operations Manager and MOM Reporting, see “Installation.”

To obtain reports1. From the Start menu, point to Programs, point to Microsoft

Operations Manager, and then click MOM Reporting.2. In the console tree, right-click the report you want, and then

select Report Help.

Note You can also refer to online Help topics under the topic Report Descriptions in the subtopic Exchange Server.

Installation

Installing the Exchange 2003 Server Management Pack requires two more steps after Microsoft Operations Manager itself is installed. You must first import the Exchange 2003 Management Pack, and then install the updated Exchange 2003 reports.

Important The Microsoft Operations Manager server and all Microsoft Operations Manager agents on monitored servers must be running at least the Microsoft Operations Manager Service Pack 1. The import of the Exchange 2003 Server Management Pack will fail on versions prior to this.

Importing the Exchange 2003 Management Pack

You can import the Exchange 2003 Management Pack from the Microsoft Operations Manager Administrator Console. To import the Exchange 2003 Management Pack, do the following steps:

To import the Exchange 2003 Management Pack1. Copy Exchange Management Pack.akm from the

Exchange 2003 Management Pack download to the Microsoft Operations Manager consolidator server.

2. On the Start menu, point to Programs, point to Microsoft Operations Manager, and then click Microsoft Operations Manager Administrator Console.

3. In the Microsoft Operations Manager Administrator Console, navigate to the Console Root by clicking Microsoft Operations Manager, and then clicking Rules.

4. Right–click Processing Rule Groups, and then select Import Management Pack.

5. Select Exchange Management Pack.akm.6. Click Import.

Installing the Exchange 2003 Management Pack Report Update

The update must be installed on1. The server with the Microsoft Operations Manager consolidator2. The server that has SQL with the Microsoft Operations Manager

(OnePoint) database if it is separate from the consolidator, and3. Each client machine which has Microsoft Operations Manager

Reporting installed.

The Exchange Management Pack Report Update.exe tool replaces the Eearept.mdb file that is installed by Microsoft Operations Manager; it contains the reports for use by Microsoft Access. Completing this procedure also updates and adds new SQL views and stored procedures in the Microsoft Operations Manager database.

To install the Exchange 2003 Management Pack Report Update.exe, complete the following procedure.

To install Exchange Management Pack Report Update.exe From the Exchange 2003 Management Pack download, run the Management Pack Report Update.exe to update the reports with the Exchange 2003 versions of the reports.

For a complete list of all of the report names before and after this report update is run, see Appendix C “Report Updates.”

Configuration

To maximize the benefits of the Exchange 2003 Management Pack, some configuration is necessary to use certain components. The configurations described in this section are:

Servers updated from Exchange 2000 to Exchange 2003 Mailbox access account configuration Service verification scripts Exchange traffic analysis reports Mail flow verification script Disk capacity planning Collect OS server information script Configuring Exchange mail queue thresholds Using Exchange reports with Exchange clusters

Servers Updated from Exchange 2000 to Exchange 2003

For Exchange 2000 servers monitored by the Exchange 2000 Management Pack, and then updated to Exchange 2003, most of the configuration done for the Exchange 2000 Management Pack also works for the Exchange 2003 Management Pack.

Only one step of the configuration needs to be re-run when the server is upgraded. Re-run the SetCredentialUtility.exe to store the credentials on the server again. You do not need to wait for the Exchange MOM 9986 event. This action is required because Exchange 2003 non-administrator users are not permitted to log in to the server, and it is the SetCredentialUtility.exe which changes the local logon policy to allow the Mailbox Access Account to be able to logon.

Mailbox Access Account ConfigurationTo use the rules that rely on a MAPI logon to Exchange, you must create at least one mailbox—the account for which is called the Agent Mailbox Account—on each server running Exchange that is being monitored. To access these mailboxes, the Exchange Management Pack needs to have a single domain user account—the Mailbox Access Account—that can access all the agent mailboxes on all the servers. You also need to grant the Mailbox Access Account the role of Exchange View Only Administrator to collect mailbox statistics information about the Exchange server for the Top 100 Mailboxes reports.

The rules that require a MAPI logon to Exchange and thus need this configuration are those that use an agent mailbox account on each server running Exchange. The rules and the reports associated with them, are as follows:

Processing Rule Group: Server Availability\MAPI Logon Check and Availability Reporting

Rule Name: Check store availability – MAPI logon\ Report: Exchange Server Availability

Processing Rule Group: Server Availability\Mail Flow VerificationRule Name: Send mail flow messagesRule Name: Receive mail flow messages

Processing Rule Group: Report Collection Rules\Mailbox Statistics Analysis

Rule Name: Report Collection Rules – Mailbox Statistics AnalysisReports: Mailbox reports in “Exchange Mailbox and Folder Sizes” folder

Processing Rule Group: Report Collection Rules\Public Folder Statistics Analysis

Rule Name: Report collection – public folder statisticsReports: Public Folder reports in “Exchange Mailbox and Folder Sizes” folder

Note Scripts in the Exchange 2003 Management Pack use the mailbox access account to access the test mailboxes. These scripts do not require Outlook to be installed on the server running Exchange. For more information, see Microsoft Knowledge Base article 266418, “XCCC: Microsoft Does Not Recommend Installing Exchange 2000 Server and Outlook 2000 or Later on the Same Computer” (http://support.microsoft.com/?kbid=266418 ) .

http://support.microsoft.com/?kbid=266418

Configuration 11

Creating the Mailbox Access AccountThe steps below describe how to create a mailbox access account, and how to grant it the role of Exchange View Only Administrator.

To create the mailbox access account1. On a computer with Exchange Administration Tools installed,

open Active Directory Users and Computers. 2. In the console tree, expand the domain. Right-click the folder that

will contain the mail-enabled user, point to New, and then click User.

3. In the New Object-User dialog box, in First name, Initials, Last name, and User logon name, type the user's information, and then click Next.

4. In Password, type a password for the new user. Confirm the new password by re-typing the password in Confirm Password. Select the password options that apply, and then click Next.

5. Click to clear the Create an Exchange mailbox check box. The alias, server, and mailbox store selections appear dimmed. Click Next, verify the information for the new user, and then click Finish.

To grant the role of Exchange View Only Administrator to the mailbox access account1. On the Start menu on the Exchange Server, point to Programs,

point to Microsoft Exchange, and then click System Manager. 2. In the console tree, right-click the organization or administrative

group for which you want to delegate administrative permissions, and then click Delegate control.

3. On the Welcome to the Exchange Administration Delegation Wizard page, click Next.

4. On the Users or Groups page, click Add to grant a new user or group administrative permissions.

5. In Delegate Control, click Browse, and then select a group or user from the list that appears (you must select the domain user account that you just added as a mailbox access account).

Note By selecting where to browse from the Look in drop-down list, you can display the list of users and groups from the entire Active Directory, or


only the list for a particular domain. You can also type the name of the user or group in the Name box. You must type one name at a time.

6. After you have selected the domain user account, in the Delegate Control dialog box, in the Role list, select the following administrative permission for the group or user:

a. Exchange View Only Administrator: This option can view Exchange configuration information.

Note To change the role of an existing user or group, select the user or group, click Edit, and then choose the new role. To remove a user or group, select the user or group, and then click Remove.

7. To assign the permissions, click Next, and then click Finish.

Storing Mailbox Access Account CredentialsTo inform the Exchange 2003 Management Pack of the mailbox access account, perform the following steps:

Note Exchange 2000 servers that have been upgraded to Exchange 2003 require a re-running of the SetCredentialUtility.exe. You do not need to wait for an Exchange MOM 9986 event in this case.

To store mailbox access account credentials1. After you create the mailbox access accounts, wait until all

servers running Exchange that are being monitored by Microsoft Operations Manager receive the event with source “Exchange MOM” and 9986 indicating that the Management Pack has generated the keys to encrypt the mailbox access account credentials. This may take approximately 10–15 minutes. You can use the view Monitor\Public Views\Exchange 2003\Server Configuration and Security\Servers Ready For SetCredentialUtility to watch for these events.

Note In the case where the Microsoft Operations Manager Service Pack 1 agent has been uninstalled and reinstalled on an Exchange server, the Exchange MOM 9986 event will not occur because the encryption keys were already stored. Furthermore, if the SetCredentialUtility.exe was already run, those credentials are still stored on the Exchange server despite the agent uninstall/reinstall process.

If the Exchange MOM 9986 event has otherwise not occurred, there are a number of possible reasons. First, ensure that the script Exchange 2003 -

Configuration 13

Publish ExMP Data is scheduled to run. This script is called from either of the two following rules in the processing rule group “Microsoft Exchange Server 2003\Availability Monitoring”:

1. Publish data for Agent Mailbox impersonation: This rule is triggered by the occurrence of the event with source Exchange MOM and id 9987, which is created by the MAPI scripts (for example, MAPI Logon or Mail Flow Verification).

2. Daily Agent Mailbox data generation: This rule is run every 24 hours at 2:00 a.m.

If the Exchange MOM 9986 event is not found, there are several explanations:

1. The Availability Monitoring processing rule group is disabled.

2. Any of the rules in the Availability Monitoring processing rule group are disabled.

3. There was a failure in Exchange 2003 - Publish ExMP Data script or the COM component EMPKP.PubKeyPublisher called by this script. If the script or the COM component fails, it will either generate an event with source Exchange MOM and id 10000 or 10001. The events will specify the exact nature of the problem encountered. The most common case is EMPKP.EXE not registered. If the script and the COM component execute successfully, Exchange MOM 9986 will be created and SetCredentialUtility.exe can be run.

2. On the Microsoft Operations Manager server, log on with local administrator credentials to all servers running Exchange. (For example, log on as a Domain Administrator.)

3. Create a list in a text file of all the servers running Exchange that Microsoft Operations Manager monitors. For example, use Notepad to create a file called c:\ExServerList.txt. In the file, list the server names and end the list with a period (.) as shown:

ServerAServerBServerC

.Note In the case of a cluster of servers running Exchange, these should be the names of the physical servers, not the Exchange virtual servers.

4. Get the credential storage utility SetCredentialUtility.exe that came with the Exchange 2003 Management Pack download.

5. Run SetCredentialUtility.exe –E <filename>

For example: SetCredentialUtility.exe –E C:\ExServerList.txt


You are prompted for the domain name (this must a fully qualified name), username, and password for the Mailbox Access Account. Here is an example of running this utility:

Please provide the credential of your Mailbox Access AccountDomain [100 characters max]: DomainA.SiteOne.comUser [100 characters max]: JohnSmithPassword [120 characters max]: *************Confirm password...Password [120 characters max]: *************

The credential storage utility stores these for use by the Microsoft Operations Manager agents on Exchange servers.

Creating the Agent Mailbox Account The following rules require the configuration of an agent mailbox account on each server running Exchange:

Processing Rule Group: Server Availability\MAPI Logon Check and Availability Reporting

Rule Name: Check store availability – MAPI logon\ Report: Exchange Server AvailabilityAgent Mailboxes used: <servername>MOM<optional suffix>

Processing Rule Group: Server Availability\Mail Flow VerificationRule Name: Send mail flow messagesRule Name: Receive mail flow messagesAgent Mailbox used: only <servername>MOM

Processing Rule Group: Report Collection Rules\Mailbox Statistics Analysis

Rule Name: Report Collection Rules – Mailbox Statistics AnalysisReports: Mailbox reports in “Exchange Mailbox and Folder Sizes” folderAgent Mailbox used: only <servername>MOM

Processing Rule Group: Report Collection Rules\Public Folder Statistics Analysis

Rule Name: Report collection – public folder statisticsReports: Public Folder reports in “Exchange Mailbox and Folder Sizes” folderAgent Mailbox used: only <servername>MOM

Note Do not create agent mailboxes on front-end Exchange servers.

Configuration 15

To create and configure an agent mailbox account1. On a computer with the Exchange System Manager installed,

start the Active Directory Users and Computers snap-in (dsa.msc). Create a user account and mailbox on each server running Exchange with the logon name that includes the name of the server running Exchange as <servername>MOM. If this is an Exchange cluster, the server name is the name of the Exchange virtual server. For example, if the server name is ExServer1, the test account is ExServer1 MOM. Set a password for this account.

Note If you have multiple database files on a server, you can add more agent mailbox accounts with logon name <servername>MOM# where # can be any number or word. The first agent mailbox account must be named <servername>MOM because it is the only mailbox used by the mail flow verification and the mailbox and public folder analyses. If you have multiple database files on a server, you can add more agent mailbox accounts with logon name <servername>MOM#, where # can be any number or word.

Also, the total length of the agent mailbox account name cannot exceed 20 characters.

2. Choose the following during account creation:

User cannot change password

Password never expires

Account is disabled

Note Do not clear the Create an Exchange mailbox check box.

3. Once the account is created, on the View menu, select Advanced Features.

4. Right-click this new agent mailbox account and select Properties, and then click the Exchange Advanced tab. If this tab is not present, ensure that Advanced Features was selected in the previous step.

5. Click Mailbox Rights, and then click Add.6. Add the mailbox access account, and then click OK.7. In the Permissions box, give the mailbox access account Full

Mailbox Access.8. In the Mailbox Rights tab, select the Self account.9. In Permissions, click Associated External Account and then

click OK.


10. Click the Security tab, and select the Mailbox Access Account. (It may be necessary to add the mailbox access account if it is not listed in the accounts. Select the mailbox access account from the list of all accounts.)

11. With the mailbox access account selected, in the Permissions box, under the Allow column, check the Receive As and Send As check boxes and click OK.

Note The Agent Mailbox cannot be set to be hidden in the Global Address Book (GAL) because it is not possible to log in to an account in that state.

Service Verification Script Configuration Periodically, the Service Verification Script runs to determine whether a list of services specified in a registry key on the Exchange server is running.

Note You can configure service verification using the Exchange Management Pack Configuration Utility, which is available for download at http://www.microsoft.com/downloads/.

Processing Rule Group: Server Availability\Verify Exchange ServicesRule Name: Service verification. Check services script.

Specify the Exchange-related services to be monitored in the following registry key on each of the managed Exchange servers:

To create the registry key1. You must create the following key in the registry editor.

Caution Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange MOM2. In this key, create the entry Monitored Services as a string. Fill

this string with a comma-delimited list of the services for which you would like to receive notification if the services are not running.

Example setting for this entry:

MSExchangeIS, MSExchangeSA, MSExchangeMTA, SMTPSVC, POP3SVC, IMAP4SVC

http://www.microsoft.com/downloads/

Configuration 17

Note In a cluster configuration, you must add this entry on each cluster node.

Exchange Traffic Analysis Reports Configuration

The Exchange 2003 Management Pack includes a timed event rule that collects information from the message tracking logs and analyzes it to assemble the Exchange Traffic Analysis reports, which detail various aspects of the messaging traffic. This event rule analyzes the message tracking log for the previous day.

Processing Rule Group: Server Utilization Logging: Reporting and Views\Report Collection Scripts

Rule Name: Report Collection - Message Tracking Log DataReports: Reports in the “Exchange 2000 and 2003 Traffic Analysis” folder

To produce the Exchange Traffic Analysis report, you must configure the monitored Exchange 2003 servers to enable message tracking for Exchange as follows:

To enable message tracking1. On the Start menu, point to Programs, point to Microsoft

Exchange, and then click System Manager. 2. In the console tree, double-click Server, right-click a server

name, and then click Properties. 3. To record the subject of any message sent to, from, or through

the server, on the General tab, select the Enable subject logging and display check box.

4. To log information about the sender, the time the message was sent or received, the message size and priority, or the message recipients, select the Enable message tracking check box.

5. To change the directory in which the log file is stored, click Change, and enter the new directory name in which the Message Tracking Log Files will be stored.

If you allow log files to accumulate on the server, they can consume a large portion of disk space and affect performance. You should remove log files periodically; however, be sure to leave log files on


the server long enough for you to review files if a problem occurs with your message flow. As an additional step, you can move the log files to a server that can accommodate the size requirements.

To specify how long log files remain on a server1. On the Start menu, point to Programs, point to Microsoft

Exchange, and then click System Manager. 2. In the console tree, double-click Servers, right-click a server

name, and then click Properties. 3. On the General tab, select the Remove log files check box. 4. In Remove log files older than (days), type the number of days

that you want a file to be stored in the Exchsrvr\<servername>.log directory before it is removed.

Note In some cases, Exchange is not able to resolve the sender for a piece of mail from the message tracking log event 1031 “Not available” used to track sent mail. Two Exchange traffic analysis reports: ”SMTP Out - Top 100 Senders by Count” and “SMTP Out - Top 100 Senders by Size.” show that the sender is not available.

This inability to resolve the sender occurs when the mail was sent to a distribution list that is configured as "Do not send delivery reports" on the Exchange Advanced tab of the Distribution List properties dialog box. (In this case, Active Directory attributes reportToOriginator and reportToOwner are both false.)

Furthermore, if "Send delivery reports to group owner" is selected for a distribution list, all mail sent to this distribution list has the owner of the list appearing as the sender in the message tracking log. The default for distribution lists is "Send delivery reports to message originator", and in this case Exchange will report the real sender in the message tracking log.

Mail Flow Verification Scripts ConfigurationThese scripts periodically send mail and verify that the mail has been received. You must configure the sending and receiving servers to know where to send mail and from where to expect mail.

Note You can also configure mail flow verification by using the Exchange Management Pack Configuration Utility, which is available for download at http://www.microsoft.com/exchange/mom

Processing Rule Group: Server Availability\Mail Flow VerificationRule Name: Send mail flow messagesRule Name: Receive mail flow messages

http://www.microsoft.com/exchange/mom

Configuration 19

The mail flow verification script uses the mailbox access account (named <servername>MOM) created in the previous procedure. For each server participating in the mail flow verification (as senders, receivers, or both), follow these configuration steps:

Note Any rule that you customize should ideally have its own processing rule group. This ensures that the rule is not overwritten when you upgrade Exchange 2003 Management Pack.

To configure a mail flow verification script1. Configure the time interval to send/receive mail according to your

Exchange installation (the default is 15 minutes):a. In Microsoft Exchange Server 2003, click Availability

Monitoring, click Verify Mail Flow, click Event Processing Rules, and then click Send Mail Flow Messages.

b. In Send Mail Flow Messages, click Properties. c. Click the Data Provider tab.d. Select the desired provider with the type Timed Event, and

synchronize the provider at 0:00.

Note The default settings (every 15 minutes synchronized at 00:09) provide a high level of monitoring without interfering with other scripts such as MAPI logon. If you want to change the frequency with which this script runs, it is important to choose one of the existing providers. In general, you should never create a new provider unless you are doing so while creating an entirely new rule.

e. Repeat the same process for the event processing rule Receive mail flow messages. Select a timed event with the same frequency as the one selected for Send mail flow messages, but synchronize one minute later.

2. Configure the number of failed attempts to receive mail before generating an alert (the default is four attempts):a. In the current processing rule group folder, right-click the

event processing rule named Receive mail flow messages, and click Properties.

b. Click the Responses tab.c. Select Exchange 2003 - Mail flow receiver, and click Edit.d. In the Launch Script dialog box, double-click the parameter,

and enter a value greater than or equal to 1. e. Click OK in all the dialog boxes.


3. Configure the registry to specify the server that will send and/or receive mail.

Caution Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

a. In each server (or virtual server) running Exchange, create the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange MOM\Mail Flow\<Servername> If this is in a clustered configuration, the “Servername” should be the Exchange virtual server. Create this same key (and the values in Steps 3b and 3c) on each physical node of the cluster.

b. Under this key, create a string value named SendTo as string and set its data to a comma-delimited list containing the server names to which mail will be sent. If the server is not going to send mail, keep this registry value empty.

c. Under the same key, create a string value named ExpectedFrom as string and set its data to a comma-delimited list containing the server names from which mail is expected. If the server is not expecting mail from other servers, keep this registry value empty.

To configure <servername>MOM mailboxes to only receive mail from intended sources

Although it is not necessary, you can configure the <servername>MOM mailboxes so that they only receive mail from the other test mailboxes that are expected to send mail to them. 1. On the Start menu, point to Programs, point to Administrative

Tools, and then click Active Directory Users and Computers. 2. In the console tree, expand the domain. Double-click Users, or

double-click the node that contains the recipient information you want to modify.

3. In the details pane, double-click the mailbox-enabled user you want to modify.

4. On the Exchange General tab, click Delivery Restrictions.

Configuration 21

5. In the Delivery Restrictions dialog box, under Message restrictions, select Only from, and then click Add.

6. In the Select Recipient dialog box, under Name, select the recipients whose e-mail the mailbox-enabled user can receive, and then click Add. Repeat this step for each recipient.

Note Test mailboxes not used in mail flow verification—specifically those named with any additional suffix (for example, <servername>MOM1)—can be similarly configured to not accept any mail by following the same steps and leaving blank the “Only from” list in step 5.

Disk Capacity PlanningYou can conduct disk capacity planning by using views of the disk space used. The data for these views comes from the Logical Disk performance monitor counters. Disk capacity planning is only necessary in Microsoft Windows® 2000 Server (including service packs). These counters are permanently enabled in Windows Server™ 2003.

To enable disk capacity planning1. From the command prompt, type diskperf –y to enable counters

on all monitored Exchange servers. 2. Reboot the server for this change to take effect.

Note In the Exchange 2003 Management Pack, alerts regarding low disk space use Windows Management Instrumentation (WMI) rather than performance counters to get disk space data.

Collecting OS Server InformationNo configuration is necessary for this rule.

Processing Rule Group: Server Utilization Logging: Reporting and Views\Report Collection Scripts\Windows Server Configuration

Rule Name: Report Collection – Windows Server Configuration InformationReport: Exchange Server Configuration


Configuring Exchange Mail Queue ThresholdsDepending on the amount of mail traffic through your Exchange deployment, you may want to adjust the following rules in the “Mail Queue Thresholds” processing rule group. Adjusting the rules ensures that they are sensitive to large queues yet they do not issue an alert from typical fluctuations.

Exchange 2003: SMTP: Categorizer Queue > 50 Exchange 2003: SMTP: Local Queue > 50 Exchange 2003: SMTP: Local Retry Queue > 50 Exchange 2003: SMTP: Messages Pending Routing > 50 Exchange 2003: SMTP: Messages in SMTP Queue Directory > 500 Exchange 2003: SMTP: Remote Queue > 500 Exchange 2003: SMTP: Remote Retry Queue > 500 Exchange Information Store service Queue of Messages to MTA > 50 Information Store Queue of Messages from MTA > 25 Information Store Transport Temp Table Entries > 600 MTA Queue Length per Connection > 50 MTA Work Queue > 50 Mailbox Store: Receive Queue > 25 Mailbox Store: Send Queue > 25

Other performance counter threshold rules in the Exchange 2003 Management Pack do not need to be adjusted. To select appropriate Exchange mail queue thresholds, record the queue fluctuations over an extended time period (for example, a week) and observe the typical fluctuations. The queue threshold can then be set to be just over these fluctuations.

Note In general, it is a best practice is to make a copy of the rules that need to be modified. Then, make changes in the copy, rather than changing the rules directly in the Exchange 2003 Management Pack.

Configuration 23

Using Exchange Reports and Views with Exchange Clusters

The Exchange reports included in the Exchange 2003 Management Pack require that the names of the Exchange virtual servers be included in the Managed Computer Rule as managed servers. The reports need to recognize the Exchange virtual servers as an Exchange server.

Also, note that for clustered servers, Exchange 2003 Public Views of performance data show such data listed under the names of the physical servers, not the Exchange virtual servers.


Best Practices in ConfigurationThis section discusses best practice scenarios when configuring the Exchange 2003 Management Pack.

Event log replication in a cluster configuration

In a clustered configuration, we recommend that you disable event log replication to prevent duplicate alerts from the physical cluster nodes. For more information about this configuration, see the Microsoft Knowledge Base article 224969, “HOW TO: Configure Event Log Replication in Windows 2000 Cluster Servers” ( http://support.microsoft.com/?kbid=224969 ) .

Making changes to the Management Pack

It should not be necessary to significantly change the configuration or rules or scripts in the Exchange 2003 Management Pack. However, if you need to do this, the best practice is to make copies of rules, change them outside the Microsoft Exchange Server 2003 processing rule group, and disable the original rules. Be sure to record the rules you have disabled because re-importing the Management Pack will cause your changes to be overwritten by the new Management Pack.

Additional views of performance counters

Processing Rule Groups: Microsoft Exchange 2003 Server\Report Collection Rules\Mailbox Statistics Analysis” and Microsoft Exchange 2003 Server\Report Collection Rules\Public Folder Statistics Analysis

The mailbox and public folder analyses send the results to the corresponding reports as performance counters with an object of the name “McExchDG”. Over time, hundreds of counters may accumulate, which may delay getting a view of all performance counters on a server. Views exist for most Exchange 2003 performance counters in the Management Pack. In general, it is a good practice to create additional views for other frequently used performance counters rather than get the list of all performance counters for a given server.

Full-text indexing and CPU measurements

http://support.microsoft.com/?kbid=224969

Configuration 25

Total CPU measurements may not be indicative of a CPU resource bottleneck because full-text indexing consumes all CPU resources which would otherwise be unused. If you use full-text indexing, you might want to disable the %CPU rule located in Microsoft Windows 2000 Operating System\Windows 2000 - All Computers\Threshold Performance Counters for Windows 2000 to prevent false alerts of high CPU utilization.

Default event collection

The rules in the Management Pack “Default Event Collection for Microsoft Windows NT® and 2000” collects all events from monitored servers. Make sure to disable these rules for normal operations.

Service availability reports

Consider whether you want to use the service availability reports (“Windows NT/2000: Service Availability by Computer”, “Windows NT/2000: Service Availability by Server” and “Windows NT/2000: Service Availability by Service”). These reports can consume a large amount of space in the Microsoft Operations Manager database. If they are not needed, disable collecting the service availability events by clearing the Enable Service Checking and Reporting check box on the Service Availability tab of the Global Agent Settings dialog box.

MAPI logon check functionality

Processing Rule Group: Availability\MAPI Logon Check and Availability Reporting

Rule: Check store availability – MAPI logon

The MAPI logon check functionality generates data for the “Exchange Server Availability” report. This is done by the script (Exchange 2003 - MAPI logon verification) recording events each time there is a successful logon to the Exchange store. This event has the source “Exchange MOM” and is number 9980. Since these events are recorded every five minutes, they can amount to a significant fraction of all events in the Microsoft Operations Manager database. If you only want to use the MAPI logon check functionality for monitoring and not for reporting, you can request that the script not record these success events by changing the value of the parameter LogPerfData for this script. The values for this parameter are:


0 = record success events 1 = record performance data instead of success events -1 = record neither success events nor performance data

When the value is non-zero, there is no data for the “Exchange Service Availability” report, and it is empty. When this parameter is 1, then the counter named “Exchange MP \ MAPI Logon Status” is populated with the value of the event number that would have been created otherwise (for example, 9980, 9981, and so forth.)

Default Notification Group

The default notification group for processing rule responses within the Exchange Management Pack is Mail Administrators. For information about adding operators to this notification group, see the Microsoft Operations Manager online help.

Configuration 29

Appendix

AScript Dependencies

The following table shows the rules and dependencies for various Exchange 2003 scripts in the Exchange 2003 Management Pack.

Script name Rule name Processing rule group

Requires test mailbox

Requires other configuration

Dependencies of this script

Exchange 2003 - Collect Mailbox Statistics

Report Collection - Mailbox Statistics

Microsoft Exchange Server 2003\Report Collection Rules\Mailbox Statistics Analysis

Yes Must store the mailbox access account credentials

WMI, COM objects from ExchMBStat.exe

Exchange 2003 - Collect Public Folder Statistics

Report Collection - Public Folder Statistics

Microsoft Exchange Server 2003\Report Collection Rules\Public Folder Statistics Analysis


WMI, COM objects from ExchPFStat.exe

Exchange 2003 - Mail flow receiver

Receive mail flow messages

Microsoft Exchange Server 2003\Server Availability Monitoring\Verify Mail Flow\

Yes Must set mail flow recipient registry key;must store the mailbox

WMI, LDAP, COM objects from ExchMFS.exe





access account credentials

Exchange 2003 - Mail flow sender

Send mail flow messages

Microsoft Exchange Server 2003\Server Availability Monitoring\Verify Mail Flow\

Yes Must set mail flow sender registry key; must store the mailbox access account credentials

WMI, LDAP, COM objects from ExchMFS.exe

Exchange 2003 - MAPI logon verification

Check mailbox store availability - MAPI logon test

Microsoft Exchange Server 2003\Server Availability Monitoring\MAPI Logon Check and Availability Reporting


WMI, LDAP, COM objects from ExchML.exe

Exchange 2003 - Publish ExMP Data

Daily Agent Mailbox data generation

Microsoft Exchange Server 2003\Server Availability Monitoring\

No Must store the mailbox access account credentials

COM objects from ExchKP.exe

Exchange 2003 - Check for existence of mailboxes on front-end servers

Check for existence of mailboxes on Front-End Servers.

Microsoft Exchange Server 2003\Health Monitoring and Performance Thresholds\ Server Configuration and Security Monitoring

No No WMI, LDAP, CDOEXM

Exchange 2003 - Check local

Check free disk space.

Microsoft Exchange Server

No May need to set

WMI, LDAP

Script Dependencies 33





disks free space

2003\Health Monitoring and Performance Thresholds\Free Disk Space Thresholds

custom thresholds

Exchange 2003 - Check mailbox store status

Check for unmounted mailbox store.

Microsoft Exchange Server 2003\ Availability Monitoring\Database Mounted Check\

No No WMI, CDOEXM

Exchange 2003 - Check service(s) state

Service verification. Check services script.

Microsoft Exchange Server 2003\ Availability Monitoring\Verify Exchange Services\

No Must set registry key

WMI

Exchange 2003 - Check 'services to monitor' registry key

Service verification. Check Services to monitor registry key.

Microsoft Exchange Server 2003\ Availability Monitoring\Verify Exchange Services\

No No n/a

Exchange 2003 - Check test mailbox existence for MAPI logon

Check agent mailbox existence.

Microsoft Exchange Server 2003\Server Availability Monitoring\MAPI Logon Check and Availability Reporting

No No. Shipped disabled by default; same task performed by a more general script (Exchange 2003 - Verify Test Mailboxes)

Needs "Exchange 2003 - Check server availability through MAPI logon" script running

Exchange 2003 Check the Microsoft No No n/a






- Check value of HeapDeCommitFreeBlockThreshold Registry Key

value of the HeapDeCommitFreeBlockThreshold Registry Key.

Exchange Server 2003\Health Monitoring and Performance Thresholds\ Server Configuration and Security Monitoring

Exchange 2003 - Collect database size per server

Report Collection - Database Size per Server

Microsoft Exchange Server 2003\Report Collection Rules\Database Size Analysis

No No WMI, LDAP

Exchange 2003 - Collect Message Tracking Log Statistics.

Report Collection - Message Tracking Log Data

Microsoft Exchange Server 2003\Report Collection Rules\Message Tracking Log Analysis

No Must have message tracking enabled

WMI, COM objects from Mcexchdg.dll

Exchange 2003 - Collect number of mailboxes per server

Report Collection - Number of Mailboxes per server

Microsoft Exchange Server 2003\Report Collection Rules\Mailboxes Per Server Analysis

No No WMI, LDAP

Exchange 2003 - Collect operating system server Information

Report Collection - Windows Server Configuration Information

Microsoft Exchange Server 2003\Report Collection Rules\Windows Server Configuration

No No WMI

Exchange 2003 - Collect Server Information

Report Collection - Exchange 2003 Server Configuration

Microsoft Exchange Server 2003\Report Collection Rules\Exchange Server

No No WMI, LDAP






Information ConfigurationExchange 2003 - Verify Circular Logging settings are correct for each Storage Group

Verify Circular Logging setting for each Storage Group.


No No WMI, CDOEXM

Exchange 2003 - Verify IIS Lockdown was run

Verify that the IIS lockdown wizard started.


No No n/a

Exchange 2003 - Verify Log Files Are Being Truncated (by age modified)

Verify that the Log Files are being truncated by backup (by age modified).


No No WMI, CDOEXM

Exchange 2003 - Verify Message Tracking is Enabled

Verify that Message Tracking is enabled.

Microsoft Exchange Server 2003\Health Monitoring and Performance Thresholds\ Server

No No WMI, CDOEXM






Configuration and Security Monitoring

Exchange 2003 - Verify Message Tracking Log shares are locked down

Verify Message Tracking Log shares are locked down.


No No WMI

Exchange 2003 - Verify remote Simple Mail Transfer Protocol (SMTP) queues.

Verify remote Simple Mail Transfer Protocol (SMTP) queues.

Microsoft Exchange Server 2003\Health Monitoring and Performance Thresholds\SMTP Remote Queues Thresholds

No No WMI, LDAP

Exchange 2003 - Verify required Windows hotfixes

Verify required Windows hotfixes.

Microsoft Exchange Server 2003\ Health Monitoring and Performance Thresholds\\Verify Windows Hotfixes\

No Need to specify required hotfixes

WMI

Exchange 2003 - Verify SMTP VS Cannot Anonymously Relay

Verify that SMTP Virtual Server cannot anonymously relay (SPAM prevention).

Microsoft Exchange Server 2003\Health Monitoring and Performance Thresholds\ Server Configuration and Security

No No WMI, LDAP, CDOEXM






MonitoringExchange 2003 - Verify Test Mailboxes

Verify Test Mailboxes

Microsoft Exchange Server 2003\Availability Monitoring\Verify Agent Mailbox Configuration\

No No WMI, LDAP

Exchange 2003 - Verify URLScan ISAPI Filter is Installed and Running

Verify that the URLScan ISAPI filter is installed and running.


No No WMI, IIS

BReport Dependencies

The following table shows the dependencies that the reports in the Exchange 2003 Management Pack have on the rules and scripts in the Exchange 2003 Management Pack.

Folder Report name Rule group name Rule name Associated script

Exchange 2000 and 2003 Health Monitoring and Operations

Exchange Databases Sizes

Microsoft Exchange Server 2003\Report Collection Rules\Database Size Analysis\

Report Collection - Database Size per Server

Exchange 2003 - Collect database size per server


Exchange Disk Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\Server Resource Utilization\Disk Performance Logging

Average Disk Queue Length (All Disks), Disk Writes / second (All disks), Disk Reads / second (All disks)

N/A

Exchange 2000 and 2003 Health

Exchange Mailboxes

Microsoft Exchange Server 2003\Report Collection Rules\

Report Collection - Number of

Exchange 2003 - Collect number of


Monitoring and Operations

Mailboxes Per Server Analysis

Mailboxes per server

mailboxes per server


Exchange Server Availability

Microsoft Exchange Server 2003\ Availability Monitoring\ MAPI Logon Check and Availability

Check mailbox store availability - MAPI logon test

Exchange 2003 - MAPI logon verification


Exchange Server Configuration

Microsoft Exchange Server 2003\Report Collection Rules\Exchange Server Configuration

Report Collection - Exchange 2000 Server Configuration Information

Exchange 2003 - Collect Server Information

Exchange 2003 Outlook Client Monitoring


Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Client Monitoring

and

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Remote Procedure Calls

Client: Latency > 10 sec RPCsClient: Latency > 2 sec RPCsClient: Latency > 5 sec RPCsClient: RPCs FailedClient: RPCs Failed: All other errorsClient: RPCs Failed: Server Too BusyClient: RPCs Failed: Server UnavailableClient: RPCs attempted

N/A

Report Dependencies 41


Client: RPCs succeededClient: Total reported latencyRemote Procedure Call (RPC) Packet Latency

Exchange 2000 and 2003 Protocol Usage

Exchange IMAP4 Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\IMAP4 Utilization

"IMAP4: Logons / second" & "IMAP4: Unique Identifier (UID) commands / second"

N/A


Exchange Information Store Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Mailbox Store

Remote Procedure Call (RPC) Operations / second,Remote Procedure Call (RPC) Requests

N/A


Exchange Mailbox Store Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Mailbox Store

Mailbox Store: Messages Delivered / minute,Mailbox Store: Messages Sent / minute,

N/A



Mailbox Store: Messages Submitted / minute


Exchange MTA Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Message Transfer Agent

Message Transfer Agent (MTA): Message Bytes / second,Message Transfer Agent (MTA): Messages Processed / second

N/A


Exchange POP3 Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\POP3 Utilization

POP3: Logons (USER rate) / second,POP3: Messages Retrieved (RETR) / second

N/A


Exchange Public Store Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Public Folder Store

Public Folder Store: Messages Delivered / minute,Public Folder Store: Messages Sent / minute,Public Folder Store: Messages

N/A



Submitted / minute (RTM),Public Folder Store: Messages Submitted / minute (SP1+)


Exchange SMTP Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\SMTP Utilization

SMTP: Messages Received / second,SMTP: Messages Delivered / second, SMTP: Messages Sent / second

N/A


Exchange Web Mail Usage

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Outlook Web Access Utilization

Outlook Web Access: Message Opens / second,Outlook Web Access: Message Sends / second

N/A

Exchange 2000 and 2003 Traffic Analysis

Mail Delivered - Top 100 Recipient Mailboxes by Count



Exchange 2003 - Collect Message Tracking Log Statistics

Exchange Mail Microsoft Exchange Report Exchange 200



2000 and 2003 Traffic Analysis

Delivered - Top 100 Recipient Mailboxes by Size

Server 2003\Report Collection Rules\Message Tracking Log Analysis

Collection - Message Tracking Log Data

3 - Collect Message Tracking Log Statistics


Mail Delivered - Top 100 Sender Domains by Count





Mail Delivered - Top 100 Sender Domains by Size





SMTP Out - Top 100 Recipient Mailboxes by Count





SMTP Out - Top 100 Recipient Mailboxes by Size





SMTP Out - Top 100 Sender Domains by Count





SMTP Out - Top 100 Sender Domains by

Microsoft Exchange Server 2003\Report Collection Rules\Message Tracking Log

Report Collection - Message Tracking Log

Exchange 2003 - Collect Message Tracking Log



Size Analysis Data Statistics

Exchange Capacity Planning

Active Client Logons by Day

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Mailbox Store Utilization

Mailbox Store: Active Client Logons,Public Folder Store: Active Client Logons

N/A


Client Logons by Day

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\Mailbox Store Utilization

Mailbox Store: Client Logons,Public Folder Store: Client Logons

N/A


Message Recipients Delivered Per Minute by Day

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\ Mailbox Store Utilization

Mailbox Store: Message Recipients Delivered / minute

N/A


Messages Sent Per Minute by Day

Microsoft Exchange Server 2003\Performance Counter Logging Rules\ Exchange Utilization and Performance\ Mailbox Store Utilization

Mailbox Store: Messages Sent / minute

N/A


MTA Messages Per Second by Day

Microsoft Exchange Server 2003\Performance Counter Logging Rules\

Message Transfer Agent (MTA): Messages

N/A



Exchange Utilization and Performance\Message Transfer Agent Utilization

Processed / second


MTA Work Queue Length by Day

Microsoft Exchange Server 2003\Server Utilization Logging: Reporting and Views\Mail Queue Logging\Message Transfer Agent Utilization

Message Transfer Agent (MTA) Work Queue (sample)

N/A

Exchange Mailbox and Folder Sizes

Highest Growth Mailboxes





Highest Growth Public Folders





Top 100 Mailboxes by Message Count





Top 100 Mailboxes by Size





Top 100 Public Folders by Message Count







Top 100 Public Folders by Size




Exchange Performance Analysis

Exchange Performance Analysis Queue Sizes

Microsoft Exchange Server 2003\Server Utilization Logging: Reporting and Views\Mail Queue Logging\Mail Queue Logging

Mailbox Store: Receive Queue (sample),Mailbox Store: Send Queue (sample),Public Folder Store: Public Replication Queue,Public Folder Store: Public Send Queue,Public Folder Store: Receive Queue

N/A

CReport Updates

Some report names have been revised to indicate that they now apply to both Exchange 2000 and Exchange 2003. “Exchange 2003 Client Monitoring” is a new report that relies on features in Exchange 2003. The following table provides the report names before and after an Exchange 2003 report update.

Report names prior to running Exchange 2003 Management Pack Report Update.exe

Report names after update for Exchange 2003

Exchange Capacity Planning Exchange Capacity Planning

MTA Work Queue Length by Day MTA Work Queue Length by Day



Messages Sent Per Minute by Day Messages Sent Per Minute by Day

Client Logons by Day Client Logons by Day

Active Client Logons by Day Active Client Logons by Day

MTA Messages Per Second by Day MTA Messages Per Second by Day

Exchange Mailbox and Folder Sizes Exchange Mailbox and Folder Sizes

Top 100 Mailboxes by Size Top 100 Mailboxes by Size

Top 100 Mailboxes by Message Count Top 100 Mailboxes by Message Count

Top 100 Public Folders by Size Top 100 Public Folders by Size

Top 100 Public Folders by Message Count Top 100 Public Folders by Message Count



Highest Growth Mailboxes Highest Growth Mailboxes

Highest Growth Public Folders Highest Growth Public Folders

Exchange Performance Analysis Exchange Performance Analysis

Queue Sizes Queue Sizes

Exchange 2000 Health Monitoring and Operations


Exchange 2000 Database Sizes Exchange Database Sizes

Exchange 2000 Disk Usage Exchange Disk Usage

Exchange 2000 Mailboxes Exchange Mailboxes

Exchange 2000 Server Availability Exchange Server Availability

Exchange 2000 Server Configuration Exchange Server Configuration

Exchange 2003 Outlook Client Monitoring

Exchange 2000 Protocol Usage Exchange 2000 and 2003 Protocol Usage

Exchange 2000 Mailbox Store Usage Exchange Mailbox Store Usage

Exchange 2000 Public Store Usage Exchange Public Store Usage

Exchange 2000 Information Store Usage Exchange Information Store Usage

Exchange 2000 SMTP Usage Exchange SMTP Usage

Exchange 2000 MTA Usage Exchange MTA Usage

Exchange 2000 Web Mail Usage Exchange Web Mail Usage

Exchange 2000 POP3 Usage Exchange POP3 Usage

Exchange 2000 IMAP4 Usage Exchange IMAP4 Usage

Exchange 2000 Traffic Analysis Exchange 2000 and 2003 Traffic Analysis

SMTP Out - Top 100 Senders by Count SMTP Out - Top 100 Senders by Count

SMTP Out - Top 100 Senders by Size SMTP Out - Top 100 Senders by Size

SMTP Out - Top 100 Recipient Domains by Count

SMTP Out - Top 100 Recipient Domains by Count

SMTP Out - Top 100 Recipient Domains by Size

SMTP Out - Top 100 Recipient Domains by Size



Mail Delivered - Top 100 Recipient Mail Delivered - Top 100 Recipient

Report Updates 51



Mailboxes by Size Mailboxes by Size





DAdditional Resources

For more information on the latest tips and tools for using and deploying this management pack, see the Exchange 2003 Management Pack for Microsoft Operations Manager web site at http://www.microsoft.com/exchange/mom

For more information about Exchange 2000 Management Pack, see http://www.microsoft.com/exchange/mom/

For more information about Microsoft Operations Manager, see http://www.microsoft.com/mom/

For more information about Exchange, see http://www.microsoft.com/exchange/

To download a self-extracting executable program of all Exchange Product Team technical articles, see http://go.microsoft.com/fwlink/? LinkId=10687

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

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

http://www.microsoft.com/exchange/

http://www.microsoft.com/mom/

http://www.microsoft.com/exchange/mom/

http://www.microsoft.com/exchange/mom

Installing and Configuring the Exchange 2003 Management Pack

Documents

Transcript of Installing and Configuring the Exchange 2003 Management Pack