Get documents about "Installing and Configuring the Exchange 2003 Management Pack
Document Sample
Installing and Configuring
the Exchange 2003
Management Pack
Contents
Introduction 3
Feature Overview 4
Reports .................................................................................................... 5
Obtaining Reports ...................................................................................................... 6
Installation 9
Importing the Exchange 2003 Management Pack ................................. 9
Installing the Exchange 2003 Management Pack Report Update.......... 9
Configuration 11
Servers Updated from Exchange 2000 to Exchange 2003 .................. 11
Mailbox Access Account Configuration ................................................. 11
Creating the Mailbox Access Account ..................................................................... 12
Storing Mailbox Access Account Credentials ......................................................... 13
Creating the Agent Mailbox Account ....................................................................... 15
Service Verification Script Configuration ............................................... 17
Exchange Traffic Analysis Reports Configuration .................................. 17
Mail Flow Verification Scripts Configuration.......................................... 19
Disk Capacity Planning .......................................................................... 21
Collecting OS Server Information .......................................................... 21
Configuring Exchange Mail Queue Thresholds...................................... 22
Using Exchange Reports and Views with Exchange Clusters ................ 22
Best Practices in Configuration ............................................................. 23
Default Notification Group 25
Script Dependencies 29
Report Dependencies 35
Report Updates 43
Additional Resources 45
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.
4 Installing and Configuring the Exchange 2003 Management Pack
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.
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.
4
Feature Overview 5
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.
Reports
The 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 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
5
6 Installing and Configuring the Exchange 2003 Management Pack
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.‖
Obtaining Reports
To 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 reports
1. From the Start menu, point to Programs, point to Microsoft Operations Manager,
and then click MOM Reporting.
6
Feature Overview 7
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.
7
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 Pack
1. 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 on
1. The server that has SQL with the Microsoft Operations Manager (OnePoint) database
if it is separate from the consolidator, and
2. Each server with the Microsoft Operations Manager consolidator and Microsoft
Operations Manager Reporting installed, and
10 Installing and Configuring the Exchange 2003 Management Pack
3. 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.‖
10
Configuration 11
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 Configuration
To 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
11
12 Installing and Configuring the Exchange 2003 Management Pack
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 Verification
Rule Name: Send mail flow messages
Rule Name: Receive mail flow messages
Processing Rule Group: Report Collection Rules\Mailbox Statistics Analysis
Rule Name: Report Collection Rules – Mailbox Statistics Analysis
Reports: 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 statistics
Reports: 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).
Creating the Mailbox Access Account
The 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 account
1. 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.
12
Configuration 13
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 account
1. 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:
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 Credentials
To 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.
13
14 Installing and Configuring the Exchange 2003 Management Pack
To store mailbox access account credentials
1. 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 - 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:
ServerA
ServerB
ServerC
.
14
Configuration 15
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 Account
Domain [100 characters max]: DomainA.SiteOne.com
User [100 characters max]: JohnSmith
Password [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 Availability
Agent Mailboxes used: <servername>MOM<optional suffix>
Processing Rule Group: Server Availability\Mail Flow Verification
Rule Name: Send mail flow messages
Rule Name: Receive mail flow messages
Agent Mailbox used: only <servername>MOM
Processing Rule Group: Report Collection Rules\Mailbox Statistics Analysis
Rule Name: Report Collection Rules – Mailbox Statistics Analysis
Reports: Mailbox reports in ―Exchange Mailbox and Folder Sizes‖ folder
Agent Mailbox used: only <servername>MOM
Processing Rule Group: Report Collection Rules\Public Folder Statistics Analysis
Rule Name: Report collection – public folder statistics
Reports: Public Folder reports in ―Exchange Mailbox and Folder Sizes‖ folder
Agent Mailbox used: only <servername>MOM
15
16 Installing and Configuring the Exchange 2003 Management Pack
Note Do not create agent mailboxes on front-end Exchange servers.
To create and configure an agent mailbox account
1. 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.
16
Configuration 17
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 Services
Rule 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 key
1. 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 MOM
2. 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
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.
17
18 Installing and Configuring the Exchange 2003 Management Pack
Processing Rule Group: Server Utilization Logging: Reporting and Views\Report Collection
Scripts
Rule Name: Report Collection - Message Tracking Log Data
Reports: 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 tracking
1. 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 server
1. 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.
18
Configuration 19
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 Configuration
These 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 Verification
Rule Name: Send mail flow messages
Rule Name: Receive mail flow messages
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 script
1. 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
19
20 Installing and Configuring the Exchange 2003 Management Pack
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.
20
Configuration 21
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.
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 Planning
You 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 planning
1. 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 Information
No 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 Information
Report: Exchange Server Configuration
21
22 Installing and Configuring the Exchange 2003 Management Pack
Configuring Exchange Mail Queue Thresholds
Depending 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.
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.
22
Configuration 23
Best Practices in Configuration
This 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
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.
23
24 Installing and Configuring the Exchange 2003 Management Pack
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.)
24
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.
Appendix
A
Script 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 Requires other Dependencies of
test configuration this script
mailbox
Exchange 2003 - Report Microsoft Exchange Yes Must store WMI, COM
Collect Mailbox Collection - Server 2003\Report the mailbox objects from
Statistics Mailbox Collection access ExchMBStat.exe
Statistics Rules\Mailbox account
Statistics Analysis credentials
Exchange 2003 - Report Microsoft Exchange Yes Must store WMI, COM
Collect Public Collection - Server 2003\Report the mailbox objects from
Folder Statistics Public Folder Collection access ExchPFStat.exe
Statistics Rules\Public Folder account
Statistics Analysis credentials
Exchange 2003 - Receive mail Microsoft Exchange Yes Must set mail WMI, LDAP, COM
Mail flow receiver flow messages Server 2003\Server flow recipient objects from
Availability registry key; ExchMFS.exe
Monitoring\Verify Mail must store
Flow\ the mailbox
access
account
credentials
30 Installing and Configuring the Exchange 2003 Management Pack
Script name Rule name Processing rule group Requires Requires other Dependencies of
test configuration this script
mailbox
Exchange 2003 - Send mail flow Microsoft Exchange Yes Must set mail WMI, LDAP, COM
Mail flow sender messages Server 2003\Server flow sender objects from
Availability registry key; ExchMFS.exe
Monitoring\Verify Mail must store
Flow\ the mailbox
access
account
credentials
Exchange 2003 - Check mailbox Microsoft Exchange Yes Must store WMI, LDAP, COM
MAPI logon store availability Server 2003\Server the mailbox objects from
verification - MAPI logon Availability access ExchML.exe
test Monitoring\MAPI account
Logon Check and credentials
Availability Reporting
Exchange 2003 - Daily Agent Microsoft Exchange No Must store COM objects
Publish ExMP Data Mailbox data Server 2003\Server the mailbox from ExchKP.exe
generation Availability access
Monitoring\ account
credentials
Exchange 2003 - Check for Microsoft Exchange No No WMI, LDAP,
Check for existence of Server 2003\Health CDOEXM
existence of mailboxes on Monitoring and
mailboxes on Front-End Performance
front-end servers Servers. Thresholds\ Server
Configuration and
Security Monitoring
Exchange 2003 - Check free disk Microsoft Exchange No May need to WMI, LDAP
Check local disks space. Server 2003\Health set custom
free space Monitoring and thresholds
Performance
Thresholds\Free Disk
Space Thresholds
Exchange 2003 - Check for Microsoft Exchange No No WMI, CDOEXM
Check mailbox unmounted Server 2003\
store status mailbox store. Availability
Monitoring\Database
Mounted Check\
30
Script Dependencies 31
Script name Rule name Processing rule group Requires Requires other Dependencies of
test configuration this script
mailbox
Exchange 2003 - Service Microsoft Exchange No Must set WMI
Check service(s) verification. Server 2003\ registry key
state Check services Availability
script. Monitoring\Verify
Exchange Services\
Exchange 2003 - Service Microsoft Exchange No No n/a
Check 'services to verification. Server 2003\
monitor' registry Check Services Availability
key to monitor Monitoring\Verify
registry key. Exchange Services\
Exchange 2003 - Check agent Microsoft Exchange No No. Shipped Needs
Check test mailbox Server 2003\Server disabled by "Exchange 2003
mailbox existence existence. Availability default; same - Check server
for MAPI logon Monitoring\MAPI task availability
Logon Check and performed by through MAPI
Availability Reporting a more logon" script
general script running
(Exchange 20
03 - Verify
Test
Mailboxes)
Exchange 2003 - Check the value Microsoft Exchange No No n/a
Check value of of the Server 2003\Health
HeapDeCommitFr HeapDeCommit Monitoring and
eeBlockThreshold FreeBlockThres Performance
Registry Key hold Registry Thresholds\ Server
Key. Configuration and
Security Monitoring
Exchange 2003 - Report Microsoft Exchange No No WMI, LDAP
Collect database Collection - Server 2003\Report
size per server Database Size Collection
per Server Rules\Database Size
Analysis
Exchange 2003 - Report Microsoft Exchange No Must have WMI, COM
Collect Message Collection - Server 2003\Report message objects from
Tracking Log Message Collection tracking Mcexchdg.dll
Statistics. Tracking Log Rules\Message enabled
Data Tracking Log Analysis
31
32 Installing and Configuring the Exchange 2003 Management Pack
Script name Rule name Processing rule group Requires Requires other Dependencies of
test configuration this script
mailbox
Exchange 2003 - Report Microsoft Exchange No No WMI, LDAP
Collect number of Collection - Server 2003\Report
mailboxes per Number of Collection
server Mailboxes per Rules\Mailboxes Per
server Server Analysis
Exchange 2003 - Report Microsoft Exchange No No WMI
Collect operating Collection - Server 2003\Report
system server Windows Server Collection
Information Configuration Rules\Windows
Information Server Configuration
Exchange 2003 - Report Microsoft Exchange No No WMI, LDAP
Collect Server Collection - Server 2003\Report
Information Exchange 2003 Collection
Server Rules\Exchange
Configuration Server Configuration
Information
Exchange 2003 - Verify Circular Microsoft Exchange No No WMI, CDOEXM
Verify Circular Logging setting Server 2003\Health
Logging settings for each Storage Monitoring and
are correct for Group. Performance
each Storage Thresholds\ Server
Group Configuration and
Security Monitoring
Exchange 2003 - Verify that the Microsoft Exchange No No n/a
Verify IIS IIS lockdown Server 2003\Health
Lockdown was run wizard started. Monitoring and
Performance
Thresholds\ Server
Configuration and
Security Monitoring
Exchange 2003 - Verify that the Microsoft Exchange No No WMI, CDOEXM
Verify Log Files Are Log Files are Server 2003\Health
Being Truncated being truncated Monitoring and
(by age modified) by backup (by Performance
age modified). Thresholds\ Server
Configuration and
Security Monitoring
32
Script Dependencies 33
Script name Rule name Processing rule group Requires Requires other Dependencies of
test configuration this script
mailbox
Exchange 2003 - Verify that Microsoft Exchange No No WMI, CDOEXM
Verify Message Message Server 2003\Health
Tracking is Tracking is Monitoring and
Enabled enabled. Performance
Thresholds\ Server
Configuration and
Security Monitoring
Exchange 2003 - Verify Message Microsoft Exchange No No WMI
Verify Message Tracking Log Server 2003\Health
Tracking Log shares are Monitoring and
shares are locked locked down. Performance
down Thresholds\ Server
Configuration and
Security Monitoring
Exchange 2003 - Verify remote Microsoft Exchange No No WMI, LDAP
Verify remote Simple Mail Server 2003\Health
Simple Mail Transfer Monitoring and
Transfer Protocol Protocol (SMTP) Performance
(SMTP) queues. queues. Thresholds\SMTP
Remote Queues
Thresholds
Exchange 2003 - Verify required Microsoft Exchange No Need to WMI
Verify required Windows Server 2003\ Health specify
Windows hotfixes hotfixes. Monitoring and required
Performance hotfixes
Thresholds\\Verify
Windows Hotfixes\
Exchange 2003 - Verify that SMTP Microsoft Exchange No No WMI, LDAP,
Verify SMTP VS Virtual Server Server 2003\Health CDOEXM
Cannot cannot Monitoring and
Anonymously anonymously Performance
Relay relay (SPAM Thresholds\ Server
prevention). Configuration and
Security Monitoring
Exchange 2003 - Verify Test Microsoft Exchange No No WMI, LDAP
Verify Test Mailboxes Server
Mailboxes 2003\Availability
Monitoring\Verify
Agent Mailbox
33
34 Installing and Configuring the Exchange 2003 Management Pack
Script name Rule name Processing rule group Requires Requires other Dependencies of
test configuration this script
mailbox
Configuration\
Exchange 2003 - Verify that the Microsoft Exchange No No WMI, IIS
Verify URLScan URLScan ISAPI Server 2003\Health
ISAPI Filter is filter is installed Monitoring and
Installed and and running. Performance
Running Thresholds\ Server
Configuration and
Security Monitoring
34
B
Report 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 Exchange Microsoft Exchange Report Collection - Exchange 2003
and 2003 Health Databases Sizes Server 2003\Report Database Size per - Collect
Monitoring and Collection Server database size
Operations Rules\Database Size per server
Analysis\
Exchange 2000 Exchange Disk Microsoft Exchange Average Disk N/A
and 2003 Health Usage Server Queue Length (All
Monitoring and 2003\Performance Disks),
Operations Counter Logging Disk Writes /
Rules\Server Resource second (All disks),
Utilization\Disk Disk Reads /
Performance Logging second (All disks)
Exchange 2000 Exchange Microsoft Exchange Report Collection - Exchange 2003
and 2003 Health Mailboxes Server 2003\Report Number of - Collect
Monitoring and Collection Rules\ Mailboxes per number of
Operations Mailboxes Per Server server mailboxes per
Analysis server
36 Installing and Configuring the Exchange 2003 Management Pack
Folder Report name Rule group name Rule name Associated
script
Exchange 2000 Exchange Server Microsoft Exchange Check mailbox Exchange 2003
and 2003 Health Availability Server 2003\ store availability - - MAPI logon
Monitoring and Availability Monitoring\ MAPI logon test verification
Operations MAPI Logon Check and
Availability
Exchange 2000 Exchange Server Microsoft Exchange Report Collection - Exchange 2003
and 2003 Health Configuration Server 2003\Report Exchange 2000 - Collect Server
Monitoring and Collection Server Information
Operations Rules\Exchange Server Configuration
Configuration Information
Exchange 2003 Exchange 2000 Microsoft Exchange Client: Latency > N/A
Outlook Client and 2003 Health Server 10 sec RPCs
Monitoring Monitoring and 2003\Performance Client: Latency > 2
Operations Counter Logging Rules\ sec RPCs
Exchange Utilization Client: Latency > 5
and sec RPCs
Performance\Client
Client: RPCs Failed
Monitoring
Client: RPCs
Failed: All other
and errors
Client: RPCs
Microsoft Exchange Failed: Server Too
Server Busy
2003\Performance Client: RPCs
Counter Logging Rules\ Failed: Server
Exchange Utilization Unavailable
and
Client: RPCs
Performance\Remote
attempted
Procedure Calls
Client: RPCs
succeeded
Client: Total
reported latency
Remote Procedure
Call (RPC) Packet
Latency
36
Report Dependencies 37
Folder Report name Rule group name Rule name Associated
script
Exchange 2000 Exchange IMAP4 Microsoft Exchange "IMAP4: Logons / N/A
and 2003 Usage Server second" & "IMAP4:
Protocol Usage 2003\Performance Unique Identifier
Counter Logging Rules\ (UID) commands /
Exchange Utilization second"
and
Performance\IMAP4
Utilization
Exchange 2000 Exchange Microsoft Exchange Remote Procedure N/A
and 2003 Information Store Server Call (RPC)
Protocol Usage Usage 2003\Performance Operations /
Counter Logging Rules\ second,
Exchange Utilization Remote Procedure
and Call (RPC)
Performance\Mailbox Requests
Store
Exchange 2000 Exchange Mailbox Microsoft Exchange Mailbox Store: N/A
and 2003 Store Usage Server Messages
Protocol Usage 2003\Performance Delivered /
Counter Logging Rules\ minute,
Exchange Utilization Mailbox Store:
and Messages Sent /
Performance\Mailbox minute,
Store Mailbox Store:
Messages
Submitted /
minute
Exchange 2000 Exchange MTA Microsoft Exchange Message Transfer N/A
and 2003 Usage Server Agent (MTA):
Protocol Usage 2003\Performance Message Bytes /
Counter Logging Rules\ second,
Exchange Utilization Message Transfer
and Agent (MTA):
Performance\Message Messages
Transfer Agent Processed /
second
37
38 Installing and Configuring the Exchange 2003 Management Pack
Folder Report name Rule group name Rule name Associated
script
Exchange 2000 Exchange POP3 Microsoft Exchange POP3: Logons N/A
and 2003 Usage Server (USER rate) /
Protocol Usage 2003\Performance second,
Counter Logging Rules\ POP3: Messages
Exchange Utilization Retrieved (RETR) /
and second
Performance\POP3
Utilization
Exchange 2000 Exchange Public Microsoft Exchange Public Folder N/A
and 2003 Store Usage Server Store: Messages
Protocol Usage 2003\Performance Delivered /
Counter Logging Rules\ minute,
Exchange Utilization Public Folder
and Store: Messages
Performance\Public Sent / minute,
Folder Store Public Folder
Store: Messages
Submitted /
minute (RTM),
Public Folder
Store: Messages
Submitted /
minute (SP1+)
Exchange 2000 Exchange SMTP Microsoft Exchange SMTP: Messages N/A
and 2003 Usage Server Received /
Protocol Usage 2003\Performance second,
Counter Logging Rules\ SMTP: Messages
Exchange Utilization Delivered /
and second, SMTP:
Performance\SMTP Messages Sent /
Utilization second
Exchange 2000 Exchange Web Microsoft Exchange Outlook Web N/A
and 2003 Mail Usage Server Access: Message
Protocol Usage 2003\Performance Opens / second,
Counter Logging Rules\ Outlook Web
Exchange Utilization Access: Message
and Sends / second
Performance\Outlook
38
Report Dependencies 39
Folder Report name Rule group name Rule name Associated
script
Web Access Utilization
Exchange 2000 Mail Delivered - Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic Top 100 Recipient Server 2003\Report Message Tracking - Collect
Analysis Mailboxes by Collection Log Data Message
Count Rules\Message Tracking Log
Tracking Log Analysis Statistics
Exchange 2000 Mail Delivered - Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic Top 100 Recipient Server 2003\Report Message Tracking - Collect
Analysis Mailboxes by Size Collection Rules\ Log Data Message
Message Tracking Log Tracking Log
Analysis Statistics
Exchange 2000 Mail Delivered - Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic Top 100 Sender Server 2003\Report Message Tracking - Collect
Analysis Domains by Count Collection Log Data Message
Rules\Message Tracking Log
Tracking Log Analysis Statistics
Exchange 2000 Mail Delivered - Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic Top 100 Sender Server 2003\Report Message Tracking - Collect
Analysis Domains by Size Collection Log Data Message
Rules\Message Tracking Log
Tracking Log Analysis Statistics
Exchange 2000 SMTP Out - Top Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic 100 Recipient Server 2003\Report Message Tracking - Collect
Analysis Mailboxes by Collection Log Data Message
Count Rules\Message Tracking Log
Tracking Log Analysis Statistics
Exchange 2000 SMTP Out - Top Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic 100 Recipient Server 2003\Report Message Tracking - Collect
Analysis Mailboxes by Size Collection Log Data Message
Rules\Message Tracking Log
Tracking Log Analysis Statistics
39
40 Installing and Configuring the Exchange 2003 Management Pack
Folder Report name Rule group name Rule name Associated
script
Exchange 2000 SMTP Out - Top Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic 100 Sender Server 2003\Report Message Tracking - Collect
Analysis Domains by Count Collection Log Data Message
Rules\Message Tracking Log
Tracking Log Analysis Statistics
Exchange 2000 SMTP Out - Top Microsoft Exchange Report Collection - Exchange 2003
and 2003 Traffic 100 Sender Server 2003\Report Message Tracking - Collect
Analysis Domains by Size Collection Log Data Message
Rules\Message Tracking Log
Tracking Log Analysis Statistics
Exchange Active Client Microsoft Exchange Mailbox Store: N/A
Capacity Logons by Day Server Active Client
Planning 2003\Performance Logons,
Counter Logging Rules\ Public Folder
Exchange Utilization Store: Active Client
and Logons
Performance\Mailbox
Store Utilization
Exchange Client Logons by Microsoft Exchange Mailbox Store: N/A
Capacity Day Server Client Logons,
Planning 2003\Performance Public Folder
Counter Logging Rules\ Store: Client
Exchange Utilization Logons
and
Performance\Mailbox
Store Utilization
Exchange Message Microsoft Exchange Mailbox Store: N/A
Capacity Recipients Server Message
Planning Delivered Per 2003\Performance Recipients
Minute by Day Counter Logging Rules\ Delivered / minute
Exchange Utilization
and Performance\
Mailbox Store
Utilization
Exchange Messages Sent Per Microsoft Exchange Mailbox Store: N/A
Capacity Minute by Day Server Messages Sent /
40
Report Dependencies 41
Folder Report name Rule group name Rule name Associated
script
Planning 2003\Performance minute
Counter Logging Rules\
Exchange Utilization
and Performance\
Mailbox Store
Utilization
Exchange MTA Messages Per Microsoft Exchange Message Transfer N/A
Capacity Second by Day Server Agent (MTA):
Planning 2003\Performance Messages
Counter Logging Rules\ Processed /
Exchange Utilization second
and
Performance\Message
Transfer Agent
Utilization
Exchange MTA Work Queue Microsoft Exchange Message Transfer N/A
Capacity Length by Day Server 2003\Server Agent (MTA) Work
Planning Utilization Logging: Queue (sample)
Reporting and
Views\Mail Queue
Logging\Message
Transfer Agent
Utilization
Exchange Highest Growth Microsoft Exchange Report Collection - Exchange 2003
Mailbox and Mailboxes Server 2003\Report Mailbox Statistics - Collect
Folder Sizes Collection Mailbox
Rules\Mailbox Statistics
Statistics Analysis
Exchange Highest Growth Microsoft Exchange Report Collection - Exchange 2003
Mailbox and Public Folders Server 2003\Report Public Folder - Collect Public
Folder Sizes Collection Rules\Public Statistics Folder
Folder Statistics Statistics
Analysis
Exchange Top 100 Mailboxes Microsoft Exchange Report Collection - Exchange 2003
Mailbox and by Message Count Server 2003\Report Mailbox Statistics - Collect
Folder Sizes Collection Mailbox
41
42 Installing and Configuring the Exchange 2003 Management Pack
Folder Report name Rule group name Rule name Associated
script
Rules\Mailbox Statistics
Statistics Analysis
Exchange Top 100 Mailboxes Microsoft Exchange Report Collection - Exchange 2003
Mailbox and by Size Server 2003\Report Mailbox Statistics - Collect
Folder Sizes Collection Mailbox
Rules\Mailbox Statistics
Statistics Analysis
Exchange Top 100 Public Microsoft Exchange Report Collection - Exchange 2003
Mailbox and Folders by Server 2003\Report Public Folder - Collect Public
Folder Sizes Message Count Collection Rules\Public Statistics Folder
Folder Statistics Statistics
Analysis
Exchange Top 100 Public Microsoft Exchange Report Collection - Exchange 2003
Mailbox and Folders by Size Server 2003\Report Public Folder - Collect Public
Folder Sizes Collection Rules\Public Statistics Folder
Folder Statistics Statistics
Analysis
Exchange Exchange Microsoft Exchange Mailbox Store: N/A
Performance Performance Server 2003\Server Receive Queue
Analysis Analysis Utilization Logging: (sample),
Queue Sizes Reporting and Mailbox Store:
Views\Mail Queue Send Queue
Logging\Mail Queue (sample),
Logging Public Folder
Store: Public
Replication Queue,
Public Folder
Store: Public Send
Queue,
Public Folder
Store: Receive
Queue
42
C
Report 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 Report names after update for Exchange 2003
Management Pack Report Update.exe
Exchange Capacity Planning Exchange Capacity Planning
MTA Work Queue Length by Day MTA Work Queue Length by Day
Message Recipients Delivered Per Minute by Day Message Recipients Delivered Per Minute 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
44 Installing and Configuring the Exchange 2003 Management Pack
Report names prior to running Exchange 2003 Report names after update for Exchange 2003
Management Pack Report Update.exe
Exchange 2000 Health Monitoring and Operations Exchange 2000 and 2003 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 Mailboxes by Mail Delivered - Top 100 Recipient Mailboxes by
Count Count
Mail Delivered - Top 100 Recipient Mailboxes by Mail Delivered - Top 100 Recipient Mailboxes by
Size Size
Mail Delivered - Top 100 Sender Domains by Count Mail Delivered - Top 100 Sender Domains by
Count
Mail Delivered - Top 100 Sender Domains by Size Mail Delivered - Top 100 Sender Domains by Size
44
D
Additional 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
