configuring native exchange 2007 scom 2007 r2

7/29/2019 Configuring Native Exchange 2007 SCOM 2007 r2

1/96

Configuring the Native Exchange 2007

MP for OpsMgr 2007 R2 (Part 1)

A configuration guide for monitoring Exchange Server 2007 with the

new native Management Pack for System Center Operations Manager(OpsMgr) 2007 R2.

Introduction

Waves of joy were felt by all the Messaging Administrator throughout the World when the native

Exchange Server 2007 Management Pack (MP) was released in June 2009. Until then, the existing MP

for Microsoft Exchange Server 2007 was more or less a disappointment since some of its functionality

had been lost in the conversion processes, when compared to its predecessor known as Microsoft

Operations Manager (MOM) 2005.

Since I dedicated a series of articles to the subject;Monitoring Exchange 2007 With System Center

Operations Manager 2007, I decided to write this one where I will uncover the new features of the native

MP, as well as the differences in the installation and configuration process.

Here are some of the key enhancements of this MP over its predecessors:

Template (wizard style) for configuring Client Access server synthetic transactions againstOutlook Web Access (OWA), Exchange ActiveSync, Web Services, POP3, and IMAP.

Template (wizard style) for configuring Exchange 2007 Intra-organizational mail flow synthetictransactions between agent-managed Exchange 2007 Mailbox servers.

New set of reports specific to Exchange 2007. Enhanced object search and filtering so that thereport search feature automatically searches for the objects that the report expects.

The management pack improves Exchange disk monitoring by providing support for mountpoints and by discovering three types of disks: Database (on the Mailbox server role), Log (on

the Mailbox server role), and Queue (on the Hub and Edge server roles).

A significant number of rules, monitors and performance collection rules that are not actionableor may be noisy are disabled (60% reduction in noise-based alerts). Note that many of these rulesare still in the management pack so that you can enable them if necessary.

Support for monitoring multiple Exchange organizations using a single OperationsManager 2007 management group.

Full support for clustered configurations using Windows Clustering technology. Improved low-privilege support. This management pack supports installing the agent with the

minimum rights required by the Operations Manager agent.

Additional and improved tasks that simplify troubleshooting and reduce the amount of time toresolve alerts.

Improved topology discovery. Improved synthetic transactions. This management pack improves the performance and support

for the Exchange 2007 synthetic transactions in several ways:
http://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.html


2/96

o The management pack supports a number of mail flow transaction types, including local,

intra-site, inter-site, cross-organization, and Internet.

o The management pack supports running the following Exchange 2007 synthetic transactions:

-Test-Mailflow

-Test-SystemHealth-Test-OwaConnectivity

-Test-ActiveSyncConnectivity

-Test-WebServicesConnectivity

-Test-PopConnectivity-Test-ImapConnectivity

-Test-MapiConnectivity

-Test-UMConnectivity

-Test-ExchangeSearch

-Test-ReplicationHealth

The discovery of Exchange 2007 server roles is disabled by default and minimal Exchange 2007monitoring is applied. This allows you to discover and monitor your servers gradually, as well as

tune the management pack as you bring more agent-managed Exchange 2007 servers into theOperations Manager environment.

The following table provides an overview of the Exchange Server 2007 MP monitoring functionality that

is enabled through Operations Manager 2007 R2:

Exchange component Monitoring functionality

Exchange Client Access ActiveSync and OWA connectivitymonitoring including synthetic transactions

Performance measuring and alerting

Exchange Edge Transport

Performance measuring and alerting

Exchange Hub Transport Performance measuring and alertingExchange Mailbox Information Store monitoring

Mail flow and MAPI connectivity monitoring Performance measuring and alerting

Exchange Unified Messaging Unified Messaging connectivity monitoringincluding synthetic transactions

Performance measuring and alertingConfiguration and Security Exchange best practices (ExBPA)Exchange Event Log monitoring Comprehensive rules for Exchange

Detailed product knowledge about events

Table 1: Exchange 2007 MP monitoring functionalities
http://go.microsoft.com/fwlink/?LinkID=137740http://go.microsoft.com/fwlink/?LinkID=137740http://go.microsoft.com/fwlink/?LinkID=137740http://go.microsoft.com/fwlink/?LinkID=137741http://go.microsoft.com/fwlink/?LinkID=137741http://go.microsoft.com/fwlink/?LinkID=137741http://go.microsoft.com/fwlink/?LinkID=137732http://go.microsoft.com/fwlink/?LinkID=137732http://go.microsoft.com/fwlink/?LinkID=137732http://go.microsoft.com/fwlink/?LinkID=137733http://go.microsoft.com/fwlink/?LinkID=137733http://go.microsoft.com/fwlink/?LinkID=137733http://go.microsoft.com/fwlink/?LinkID=137734http://go.microsoft.com/fwlink/?LinkID=137734http://go.microsoft.com/fwlink/?LinkID=137734http://go.microsoft.com/fwlink/?LinkID=137735http://go.microsoft.com/fwlink/?LinkID=137735http://go.microsoft.com/fwlink/?LinkID=137735http://go.microsoft.com/fwlink/?LinkID=137736http://go.microsoft.com/fwlink/?LinkID=137736http://go.microsoft.com/fwlink/?LinkID=137736http://go.microsoft.com/fwlink/?LinkID=137739http://go.microsoft.com/fwlink/?LinkID=137739http://go.microsoft.com/fwlink/?LinkID=137739http://go.microsoft.com/fwlink/?LinkID=151496http://go.microsoft.com/fwlink/?LinkID=151496http://go.microsoft.com/fwlink/?LinkID=151496http://go.microsoft.com/fwlink/?LinkID=148796http://go.microsoft.com/fwlink/?LinkID=148796http://go.microsoft.com/fwlink/?LinkID=148796http://go.microsoft.com/fwlink/?LinkID=148797http://go.microsoft.com/fwlink/?LinkID=148797http://go.microsoft.com/fwlink/?LinkID=148797http://go.microsoft.com/fwlink/?LinkID=148797http://go.microsoft.com/fwlink/?LinkID=148796http://go.microsoft.com/fwlink/?LinkID=151496http://go.microsoft.com/fwlink/?LinkID=137739http://go.microsoft.com/fwlink/?LinkID=137736http://go.microsoft.com/fwlink/?LinkID=137735http://go.microsoft.com/fwlink/?LinkID=137734http://go.microsoft.com/fwlink/?LinkID=137733http://go.microsoft.com/fwlink/?LinkID=137732http://go.microsoft.com/fwlink/?LinkID=137741http://go.microsoft.com/fwlink/?LinkID=137740


3/96

Solution Topology

For the purpose of writing this article, I installed the following environment on my test lab:

One thing to notice is that all the machines (virtualized on Hyper-V) are now 64-bit, since this

architecture is fully supported by OpsMgr 2007 R2.

Name Role Architecture Software

OPSMGR2K7R2 Root Management Server X64 Windows Server 2008 R2

System Center Operations Manager 2007

R2

E2K7-x64 Domain Controller

Mailbox Server

CAS Server

HUB Transport Server

x64 Windows Server 2008 SP2

Exchange Server 2007 SP2

E2K7-MBX2 Mailbox Server

Unified Messaging

SCR Target

X64 Windows Server 2008 SP2

Exchange Server 2007 SP2

E2K7EDGE Edge Server x64 Windows Server 2003 R2 SP2

Exchange Server 2007 SP1 + UR9

Table 2: List of servers

Exchange 2007 Management Pack Pre-Requisites and

Considerations

There are no special requirements for the new native Exchange 2007 MP, nevertheless Id like to mention

the following system requirements:

This MP is for System Center Operations Manager 2007 R2 and will not run on any previousversion, such as Operations Manager 207 SP1.

Install Windows PowerShell and the Operations Console on your root management server. Thisis required because the Exchange Server 2007 Management Pack workflows require WindowsPowerShell to run successfully.

Exchange Server 2007 Service Pack 1 is required (mainly because some performance counterswere renamed with this release).

64-bit platforms only!There are some limitations and considerations that you should be aware of:

The maximum tested number of simultaneous synthetic transactions on an agent-monitoredExchange server is 15. Running synthetic transactions too frequently can generate a heavy load

on the Mailbox or Client Access servers. Additionally it is possible for incorrect availability to

be calculated if the transactions are run too frequently (more frequently than every 5 minutes is

not recommended).


4/96

This management pack does not monitor Network Load Balanced clusters that you may have setup for the Exchange 2007 Client Access server role, Hub Transport server role, or Edge

Transport server role.

This management pack does not support third-party cluster technology. This management pack does not support agentless monitoring. This new Exchange Server 2007 MP for OpsMgr 2007 R2 does not support an upgrade from the

previously released, converted Exchange Server 2007 Management Pack. Running bothmanagement packs in parallel is a supported scenario, but not recommended.

Increase the size of the Windows PowerShell Event Log on managed Exchange 2007 serversrunning on Windows Server 2003 (default size is 512 KB as depicted on Figure 1). Configure

the size of the event logs on the local server and the Overwrite property to avoid error conditionsresulting from the increase in events due to running synthetic transactions (Figure 2).

Figure 1: PowerShell Event Log Properties

Figure 2: PowerShell Log full


5/96

Installation and Configuration Procedures

There will be 11 steps covered in this article in order to install and fully configure the Exchange Server

2007 MP for the environment previously described. Although some of the steps are optional, Im pretty

sure these are the most common in a typical organization:

1. Install the Operations Manager agent on all Exchange 2007 servers you want to manage, andenable agent proxy.

1.1. Install the agent manually on Edge Server.

2. Create a new management pack in which you store overrides and other customizations.3. Download and import the native Exchange 2007 MP and also recommended additional

management packs.

4. Enable Exchange 2007 Server Role discoveries to discover Exchange 2007 servers and to startmonitoring them.

5. Configure disk monitoring.6. Configure Internet Information Services (IIS) Monitoring.7. Assign Edge servers to a particular organization and site.8. Configure synthetic transactions.

8.1. Configure intra-organization mail flow.

8.2. Configure inter-organization mail flow.

8.3. Configure Client Access server synthetic transactions.9. Configure the Log Shipping Replay Queue Length Monitor for SCR and CCR Scenarios.10. Enable Remote Unified Messaging Connectivity Monitoring.11. Adjust the Best Time to Run Report Data Collection Scripts / Resource-Intensive Rules and

Monitors.

SummaryThis concludes part 1 of this 6-part article. In the next part well cover the first 3 steps of the previouslymentioned installation and configuration process.

If you would like to read the other parts in this article series please go to:

Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 2) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 3) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 4) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 5) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 6)
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part3.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part3.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part3.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.html


6/96



Adding the Exchange servers as agent-managed computers, creating acustom management pack for customizations and importing the new

native Exchange 2007 Management Pack.

Introduction - Add The Exchange Servers as Agent

Managed Computers

Adding the Exchange servers to manage as agent managed computers is pretty much the same as in the

previous versions of OpsMgr. Let us review the process;

1. Click the Administration tab and then clickConfigure computers and devices to manage onthe Actions pane. This will start the Computer and Device Management Wizard (Figure 3).

ClickNext, choose Advanced Discovery (Figure 4) and select Servers Only from the

Computers and Device Classes drop-down box.


7/96

Figure 3: Computer and Device Management Wizard


8/96

Figure 4: Advanced discovery

2. On the next window, browse for the computers you are adding (Figure 5) and clickNext. SelectUse selected Management Server Action Account (Figure 6), clickDiscovery and wait for the

discovery results (Figure 7). Figure 8 shows a brief summary that is displayed at the end of the

wizard. It is mandatory that all systems running Exchange Server 2007 that are managed by

Operations Manager use Local System as the Agent Action Account. ClickFinish.


9/96

Figure 5: Discovery Method


10/96

Figure 6: Administrator Account


11/96

Figure 7: Select Objects to Manage


12/96

Figure 8: Summary

3. If the agent installation was successful, on each Exchange server you will be able to see theSystem Center Operations Manager 2007 R2 Agent listed on the Add/Remove Programs or

Programs and Features on Windows 2008 (Figure 9). A new service is also created, the

System Center Management Service, as depicted in Figure 10.


13/96

Figure 9: Programs and Features (Add/Remove Programs)


14/96

Figure 10: System Center Management Service Properties

4. To enable Agent Proxy configuration on all managed Exchange servers, in the Administrationpane, underAdministration, Device Management, Agent Managed, right-click on each

Exchange server (Figure 11), select Properties, then the Security tab (Figure 12), and check the

box Allow this agent to act as a proxy and discover managed objects on other computers.

This step will also make exchange cluster instances to appear in the Agentless Managed section

(ensure that all physical nodes of the cluster are monitored). Repeat the process for everymanaged Exchange 2007 server in the list.


15/96

Figure 11: Agent Managed Properties


16/96

Figure 12: Enabling Agent Proxy

Installing the Agent on Edge Server

Just like in my previous article, I decided to install the Edge Server as a standalone (workgroup) server.This means that authentication against the Operations Manager server must be done with certificates,

because the agent in the workgroup cannot authenticate with the management server in the domain using

the Kerberos protocol.
http://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part2.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part2.html


17/96

Figure 13: Certificate Authentication

Although the configuration process is pretty much the same as the above mentioned article, let's quickly

review the necessary steps:

1. In this scenario, the agent must be manually installed. From the Edge server, browse to the folderwhere you installed the OpsMgr binaries on the Management server. In my case this was\\OPSMGR2K7R2\C$\Program Files\System Center Operations Manager

2007\AgentManagement\AMD64\ (Figure 14). Double ClickMOMAgent.msi to trigger the

setup process (Figure 15). ClickNext.

Figure 14: Agent installation binaries


18/96

Figure 15: Operations Manager Agent Setup

2. On the Destination Folder window (Figure 16), accept the default installation path and clickNext. On the next window (Figure 17), clickNext to specify Management Group information.

Figure 16: Destination Folder


19/96

Figure 17: Management Group Configuration

3. On the Management Group Configuration window (Figure 18), specify the ManagementGroup Name, the Management Server and the Management Server Port. ClickNext.

Figure 18: Management Group Configuration (Cont.)

4. On the Agent Action Account window (Figure 19), select Local System and clickNext. Reviewthe summary (Figure 20), clickInstall and them Finish (Figure 21).


20/96

Figure 19: Agent Action Account

Figure 20: Ready to Install


21/96

Figure 21: Finish

5. After these steps the agent will be installed, but it will not be able to communicate with theOpsMgr Management Server, since it does not have a certificate assigned yet. Both the computer

hosting the agent and the OpsMgr Management Server will require a certificate from a trusted

certification authority (CA). To enable the certificates for OpsMgr authentication, the

MOMCertImport tool (located on \SupportTools\AMD64 in the OpsMgr installation media)

must be used. Run the following command:

MOMCertImport /SubjectName

Note:You can also export the previously issued certificate to a .PFX file and run the command

MOMCertImport .pfx.

If you ever need to remove certificates imported with the MOMCertImport tool, just run

MomCertImport /Remove. For more information, please read the following article titled;

Authentication and Data Encryption for Windows Computers in Operations Manager 2007.
http://technet.microsoft.com/en-us/library/bb735408.aspxhttp://technet.microsoft.com/en-us/library/bb735408.aspx


22/96

Figure 22: Running MOMCertImport

6. If you have not previously installed any manual agent, the global setting must be changed fromreject to 'Review new manual agent installation in pending management view'. Open theOperations Console and on the Administration pane select Settings. On the right pane, expand

Server and clickSecurity (Figure 23). ClickProperties and on the General tab select Review

new manual agent installation in pending management view (Figure 24). ClickOKto finish.

Figure 23: Allowing manual agent installations


23/96

Figure 24: Global Management Server Settings - Security

7. Open the Operations Console, on the Administration pane expand Device Management andselect Pending Management. On the right pane, right click each server requiring approval and

select Approve (Figure 25). To check if the agent is successfully approved look in the Agent

Managed folder for the approved agent to see if it is there.


24/96

Figure 25: Manual Agent Install Approval

Create a New Management Pack for Customizations

The customizations and overrides of sealed management packs, such as the Exchange 2007 MP, are

usually saved in the default management pack. Best practice dictates that you should create and use a

separate management pack for that purpose. Creating a new management pack for storing overrides has

the following advantages:

It simplifies the process of exporting customizations that were created in your test and pre-production environments to your production environment.

It allows you to delete the original management pack without first needing to delete the defaultmanagement pack.

It is easier to track and update customizations to individual management packs.1. In the Operations Console, click the Administration button. In the Administration pane, right-

clickManagement Packs and then clickCreate Management Pack. The Create a

Management Packwizard displays.

2. In the General Properties page (Figure 26), type a name for the management pack in Name, thecorrect version number in Version, and a short description in Description. ClickNext and then

Create.


25/96

Figure 26: Creating a Custom MP for customizations

Besides creating this additional management pack for Exchange 2007 customizations and overrides, you

should also decide whether to create a new one for synthetic transactions. Use the following guidelines

when planning destination management packs for these operations:

Plan logical groupings of synthetic transactions. Plan to group synthetic transactions inmanagement packs so that it will be easy later for you to find a particular synthetic transaction.

When you make a change to a synthetic transaction within a management pack, the wholemanagement pack is redistributed to every server that has a transaction defined in the

management pack. If you anticipate making frequent changes to synthetic transactions, group the

transactions logically in management packs so that the only pertinent management pack areredistributed to the servers involved in those transactions.

Do not store each synthetic transaction in a separate management pack, because the number ofsuch management packs can grow into the hundreds, eventually having a negative impact on the

Operations Manager 2007 environment.

For the purpose of writing this article I only used one management pack for customizations and synthetic

transactions.

Install the Exchange Server 2007 MP

Before downloading and installing the Exchange Server 2007 MP, you might want to import somerecommended additional management packs, such as (these are the ones I used):


26/96

Windows Server Cluster Management Pack for Operations Manager 2007 v6.0.6702.0 Active Directory Management Pack for System Center Operations Manager 2007 v6.0.7065.0 Operations Manager 2007 R2 Management Pack v6.1.7533.0 Windows Server Operating System Management Pack for Operations Manager 2007 v6.0.6667.0 Windows Server Internet Information Services for System Center Operations Manager 200

v6.0.6539.0

With the recommended additional management packs already imported, download and install the latest

Microsoft Exchange Server 2007 Management Pack for System Center Operations Manager 2007 R2 (by

the time of the writing of this article it was version 6.0.6702.0). You can find the latest ManagementPacks at the System Center Operations Manager 2007 Catalog.

The installation of the downloaded .msi file is a very simple process that just extracts the required

Management Pack files to the folder you choose:

Microsoft.Exchange.Server.2007.Discovery - Contains discoveries and common monitoring thatapplies to all Exchange servers

Microsoft.Exchange.Server.2007.Library - Contains class definitions Microsoft.Exchange.Server.2007.Monitoring.Cas - Contains Client Access server (CAS) rolemonitoring Microsoft.Exchange.Server.2007.Monitoring.Edge - Contains Edge server role monitoring and

discoveries

Microsoft.Exchange.Server.2007.Monitoring.Hub - Contains Hub server role monitoring Microsoft.Exchange.Server.2007.Monitoring.Mailbox - Contains Mailbox server role monitoring Microsoft.Exchange.Server.2007.Monitoring.UM - Contains Unified Messaging server role

monitoring and discoveries

Microsoft.Exchange.Server.2007.Reports - Contains Reports for the Mailbox, Hub, and ClientAccess server roles.

Microsoft.Exchange.Server.2007.Reports.SLM - Contains Exchange 2007 reports using theOperations Manager R2 Service Level Management Reporting feature. Note that this is anunsealed management pack.

Microsoft.Exchange.Server.2007.Template - Contains the Mail Flow and Client Access serversynthetic transaction templates.

OM2007_MP_EX2007_R2.doc - The management pack guide.To import the Exchange 2007 MP, open the OpsMgr 2007 Operations Console. Click the Administration

tab, right-click the Management Packs node and then clickImport Management Packs (Figure 27).

ClickAdd, Add from diskand then clickNo on the Online Catalog Connection window. Select all the

files from the Exchange MP directory (Figure 28), clickOpen and then click the Install button. After the

import process is complete and the dialog box displays an icon next to each Management Pack that

indicates success of the importation (Figure 29), click the Close button.
http://www.microsoft.com/downloads/details.aspx?FamilyId=AC7F42F5-33E9-453D-A923-171C8E1E8E55&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=008F58A6-DC67-4E59-95C6-D7C7C34A1447&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=61365290-3c38-4004-b717-e90bb0f6c148&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=3529D233-5E3E-4B51-8F66-5D6F27005EC3&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=e9f3cd3f-9bc0-45cd-b10f-120e937ee4c4&displaylang=enhttp://go.microsoft.com/fwlink/?LinkId=82105http://go.microsoft.com/fwlink/?LinkId=82105http://www.microsoft.com/downloads/details.aspx?FamilyID=e9f3cd3f-9bc0-45cd-b10f-120e937ee4c4&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=3529D233-5E3E-4B51-8F66-5D6F27005EC3&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=61365290-3c38-4004-b717-e90bb0f6c148&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=008F58A6-DC67-4E59-95C6-D7C7C34A1447&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=AC7F42F5-33E9-453D-A923-171C8E1E8E55&displaylang=en


27/96

Figure 27: Import Management Packs

Figure 28: Select Management Packs to import


28/96

Figure 29: Import Management Packs

Summary

In this part we covered the first 3 steps of the 11 necessary, as described in part 1. Part 3 will be about the

next 4:

Enable Exchange 2007 Server Role discoveries to discover Exchange 2007 servers and to startmonitoring them.

Configure disk monitoring. Configure Internet Information Services (IIS) Monitoring. Assign Edge servers to a particular organization and site.


Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 1) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 3) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 4) Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 5)
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part3.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part3.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part1.html


29/96

Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2 (Part 6)

Configuring the Native Exchange 2007MP for OpsMgr 2007 R2 (Part 3)

How to enable Exchange 2007 server role discovery. Customizing the

Exchange 2007 Management pack with overrides; disk monitoring, IIS

monitoring and assigning Edge servers to the right Organization and Site.

Enable Exchange 2007 Server Role Discovery

After importing the Exchange 2007 MP, it will not start discovering Exchange machines immediately.

This behavior is by design so that you can first test the management pack on a limited set of servers.

There is though a lightweight registry discovery that runs automatically on all Windows servers, the

Exchange 2007 Discovery Helper, its only purpose is to discover Exchange 2007 servers in your

environment without actually starting monitoring them (allowing you to see the "big picture").

Verifying the Discovery Helper results should be the first action after importing the Exchange 2007 MP.

1. In the Operations Console, click the Monitoring button, navigate to Discovered Inventory andthen clickChange Target Type in the Actions pane. In the Look for field, typeExchange 2007

Discovery Helper, select it, and then clickOK(Figure 1). A list of Exchange 2007 servers

appears with a status ofNot Monitored (Figure 2).
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.html


30/96

Figure 1: Select Items to Target


31/96

Figure 2: Discovered Inventory

2. Next, we will need to enable Exchange 2007 Server Role Discovery. Go to the ObjectDiscoveries node located underManagement Pack Objects, in the Authoring section of the

Operations Console. In the Look for field, typeExchange 2007 Server Role and clickFind

Now. A list of Exchange 2007 Server Role Discoveries appears (Figure 3). Notice the Enabled

by default column, most of the role discoveries are disabled.


32/96

Figure 3: Object Discoveries

Although one can feel compelled to enable all the roles at once, my recommendation is to enable just the

roles you effectively have in your environment.

Discovery Name Description

Exchange 2007 CCR Clustered Mailbox Server

Role DiscoveryDiscovers CCR and SCC clustered Mailbox servers

Exchange 2007 CCR Node Role Discovery Discovers CCR node servers in a CCR cluster (the physical nodes)

Exchange 2007 Standalone CCR Node Discovery

Discovers standalone CCR node roles (nodes that are participating in log

shipping but are not part of an active Mailbox server) and standalone mailbo

roles (also includes SCR targets)

Exchange 2007 CAS Role Discovery Discovers Client Access server roles

Exchange 2007 Hub Transport Role Discovery Discovers Hub Transport server roles

Exchange 2007 Edge Role Discovery Discovers Edge Transport server roles

Exchange 2007 UM Role Discovery Discovers Unified Messaging (UM) roles Bottom of Form

Table 1: Exchange Server Role Discoveries

Note:

To discover standalone Exchange Mailbox servers you have to enable Exchange 2007 Standalone CCR

Node Discovery.

3. The process of enabling each role is the same, for example, to enable discovery of all Edgeservers, right-click the Exchange 2007 Edge Role Discovery and select Overrides | Override

the Object Discovery | For all objects of class: Exchange 2007 Discovery Helper (Figure 4).


33/96

Figure 4: Override the Object Discovery

4. In the Override Properties dialog box, set the Enabled parameter to True, choose a destinationmanagement pack and clickOK.


34/96

Figure 5: Exchange 2007 Edge Role Discovery: Override Properties

Exchange 2007 discoveries run every 24 hours by default, meaning you may have to wait until you start

seeing your Exchange servers correctly categorized.

Configure Disk Monitoring

I am sure that everyone agrees that disk monitoring is absolutely crucial to guarantee overall system

health on any Exchange 2007 environment. But doubling the monitoring will not necessarily mean betterresults... Why am I talking about double disk monitoring? Because Exchange 2007 disk monitoringdiscovers the following disks (mount points are also considered as Exchange 2007 disks):

Disks that store an Exchange 2007 mailbox database file Disks that store an Exchange 2007 mailbox log file Disks that store Exchange 2007 Hub or Edge Queue files

Since one of the additional imported management packs was Windows (the Server Operating System

MP), it is likely that you are also monitoring disk usage using this management pack, causing duplication

of disk space alerts.

To prevent duplication of alerts, it is recommended to disable Exchange disks monitoring from one of themanagement packs (Exchange 2007 or Windows Operating System). Although the same result can be


35/96

achieved by disabling the correct monitors on either of the management packs, I prefer to disable disk

monitoring from the Windows Server Operating System MP.

Please be aware that the Exchange Server 2007 MP only discovers disks that contain the Mailbox

database, log files or queue files, meaning that you might not want to disable disk monitoring for systemdisks from the Windows Server Operating System MP (assuming system disks do not contain Exchange

data files).

1. To disable disk monitoring for Exchange servers from the Windows Server Operating SystemMP, in the Authoring section of the console, go to the Monitors node, underManagementPack Objects. ClickChange Scope and in the Look for field, typeLogical Disk(Figure 6).

Select logical disk classes from all operating system versions where you are running Exchange

2007 servers and clickOK.

Figure 6: Scope Management Pack Objects: Logical Disk

2. Expand Windows Server 200x Logical Disk, expand Entity Health, and then expandAvailability to see the Logical Disk Availability and Logical Disk Free Space monitors. Right-click the Logical Disk Free Space monitor, clickOverrides | Override the Monitor | For a

group (Figure 7). Select the Exchange 2007 Computer Group, and clickOK(Figure 8).


36/96

Figure 7: Override the Monitor: Logical Disk Free Space

Figure 8: Select Object


37/96

3. In the Override Properties dialog box, set the Enabled parameter to False, and then choose adestination management pack (Figure 9). Perform the same procedure for the Logical Disk

Availability Monitor (Figure 10) as well as for the other disk monitors underPerformance:

Average Disk Seconds Per Transfer (Figure 11), Average Disk Seconds Per Read and

Average Disk Seconds Per Write (these last 2 might not be enabled by default).

Figure 9: Logical Disk Free Space: Override Properties


38/96

Figure 10: Logical Disk Availability: Override Properties


39/96

Figure 11: Average Disk Seconds Per Transfer: Override Properties

4. There is a specific monitor from the Windows Operating system MP called Logical DiskFragmentation Level (underPerformance). Although this one is not duplicated on the

Exchange 2007 MP, my recommendation is to disable it as well (Figure 12).


40/96

Figure 12: Logical Disk Fragmentation Level: Override Properties

5. Repeat steps 2, 3 and 4 for logical disk monitors belonging to any other operating systemversions.

6. After preventing duplication of disk alerts, we should tune the Exchange 2007 monitors to matchour environment thresholds. To configure Exchange 2007 Disk Monitoring, in the Operations

Console, clickAuthoring and then clickMonitors. Click the Scope button on the toolbar,

ensure that View all targets is selected and in the Look for field, typeDisk. Select Exchange2007 Mailbox Database Disk, Exchange 2007 Mailbox Log Diskand Exchange 2007 Queue

Disk, and then clickOK(Figure 13).


41/96

Figure 13: Scope Management Pack Objects: Disk

7. Expand Exchange 2007 Mailbox Database Disk, expand Availability and right-clickExchange 2007 MDB Disk Free Space Monitor. Select Overrides | Override the Monitor |

For all objects of class: Exchange 2007 Mailbox Database Disk(Figure 14).


42/96

Figure 14: Override the Monitor: Exchange 2007 MDB Disk Free Space Monitor

8. In the Overrides Properties window, adjust the parameters to fit your environment (Figure 15).Note that you can set a megabyte warning or error threshold, as well as a percentage free space

threshold (the alert will only be raised if*both* the parameters are exceeded). By applying

overrides to this monitor, you can do it once for all Exchange 2007 disks with mailbox databases

on them.9. Repeat steps 7 and 8 for the disk monitors from the Exchange 2007 Mailbox Log Diskand

Exchange 2007 Queue Diskclasses.


43/96

Figure 15: Exchange 2007 MDB Disk Free Space Monitor: Override Properties

Configure Internet Information Services (IIS)

Monitoring

A similar situation to the one described in the previous section happens with service alerts for the WWW

and IIS Admin Services on Client Access servers, since both the Exchange 2007 MP and the IIS

Management Pack contain those monitors. To prevent duplication, we'll disable these monitors in theExchange Server 2007 MP.

1. To disable WWW and IIS Admin Service monitors go to the Monitors node, underManagement Pack Objects in the Authoring section of the Operations Console. Set your scope

to Exchange 2007 Client Access Role and then expand Entity Health, expand Availability andexpand Client Access Server Core Services Rollup.

Right clickExchange 2007 IIS Admin Service Monitor on CAS and then clickOverrides |

Disable the Monitor | For all objects of class: Exchange 2007 Client Access Role (Figure 16).

2. Repeat last step forExchange 2007 WWW Publishing Service Monitor (Figure 17).


44/96

Figure 16: Disable the Monitor: Exchange 2007 IIS Admin Service Monitor on CAS


45/96

Figure 17: Disable the Monitor: Exchange 2007 WWW Publishing Service Monitor

Assign Edge Servers to a Particular Organization andSite

By default, the Exchange 2007 MP assigns all Edge Transport servers to a separate organization,Default-

Edge Organization, and site calledDefault-Edge Site. This is what shows up in the topology view (Figure

18).


46/96

Figure 18: Exchange 2007 Topology before reassigning Edge

If you prefer visualizing Edge Transport servers under the same organization and site of your choice,

overrides can be used.

1. Go to the Object Discoveries node located underManagement Pack Objects, in theAuthoring section of the Operations Console. In the Look for field, typeExchange 2007 Site

Edge and clickFind Now. Right-click the Exchange 2007 Site Edge on Edge Discovery and

select Overrides | Override the Object Discovery | For all objects of class: Exchange 2007Edge Transport Role (Figure 19).


47/96

Figure 19: Override the Object Discovery: Exchange 2007 Site Edge on Edge Discovery

2. In the Override Properties dialog box, there are 2 parameters that can be configured: AD SiteName and Forest DNS Name. Modify them accordingly to match your environment, select a

destination management pack and clickOK(Figure 20). If you enter the same organization and

site names as existing organizations and sites discovered by other Exchange roles, the Edge

Transport servers will join those existing sites in the topology view (Figure 21).


48/96

Figure 20: Exchange 2007 Site Edge on Edge Discovery: Override Properties


49/96

Figure 21: Exchange 2007 Topology after assigning Edge

Summary

And this concludes the 3rdpart of the article, with 7 configuration steps (out of 11) already covered. Part 4

will be dedicated to 1 step only: configuring mail flow and CAS synthetic transactions.

If you would like to be notified of when Rui Silva releases the next part in this article series please sign up

to our MSExchange.org Real-Time Article Update newsletter.



Configuring the Native Exchange 2007MP for OpsMgr 2007 R2 (Part 4)

How to configure synthetic transactions in the Exchange 2007 MP to

monitor normal flow of intra and inter Organization email. Configuring

Client Access Server Synthetic Transactions.

Configure Synthetic Transactions
http://www.msexchange.org/pages/newsletter.asphttp://www.msexchange.org/pages/newsletter.asphttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part1.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.htmlhttp://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part1.htmlhttp://www.msexchange.org/pages/newsletter.asphttp://www.msexchange.org/pages/newsletter.asp


50/96

This section will cover the configuration process for 2 types of synthetic transactions:

Mail flow synthetic transactionsTo monitor the health (availability and latency) of severalmail flow processes, the Exchange Server 2007 MP supports several variations of mail flow

synthetic transactions on Mailbox servers:

- Local mail flow: a server sends mail to itself (enabled by default on each agent-managed

Exchange Server 2007 Mailbox server)- Intra-organization mail flow: a server sends mail within an organization

- Inter-organization mail flow (a server sends mail to another organization/mailbox, which could

also be used to send mail via the Internet as long as the recipient is able to generate a deliveryreceipt)

CAS synthetic transactionsThis type of synthetic transactions run on Client Access serversand perform transactions against the Client Access server itself and also the back-end Mailbox

servers within the same site. Examples of these transactions are to check Exchange ActiveSync,

Outlook Web Access, and Web Services connectivity.

The collected results from both types of synthetic transactions are represented in the Monitoring pane of

the Operations Console (Figure 1).

You can also see synthetic transactions (represented by the perspective icon that looks like a pair ofglasses) in the Exchange 2007 Topology View (Figure 2):


51/96

Figure 1: Monitoring Mail Flow


52/96

Figure 2: Synthetic transactions in Topology View

Configure Intra-Organization Mail Flow

Configuring mail flow using a Wizard is one of the new features of the native Exchange 2007 MP.

Although it is still possible to configure intra-organization mail flow synthetic transactions using

overrides, it is way better to use the provided template, imported with the Exchange Server 2007

Management Pack.

1. To configure mail flow synthetic transactions click the Authoring button in the OperationsConsole, clickManagement Pack Templates, and then clickAdd Monitoring Wizard on theActions pane (Figure 3).

Figure 3: Management Pack Templates

2. On the Select Monitoring Type page, select Exchange 2007 Intra-Organization Mail FlowMonitoring, and clickNext (Figure 4).

3. On the General Properties page, type the Name for the object, optionally type a Descriptionand select a destination management pack from the list. ClickNext (Figure 5).


53/96

Figure 4: Select Monitoring Type


54/96

Figure 5: General Properties

4. On the Source Server page, select the Exchange organization and search the Source serverfrom the list of available servers, and then clickNext (Figure 6).

5. On the Test Settings page, specify the Test frequency value or accept the default. Ensure thatthe test frequency you specify (between 5 and 60 minutes) is at least two times greater than the

Time-out value (between 1 and 30 minutes) and clickNext (Figure 7).


55/96

Figure 6: Source Server


56/96

Figure 7: Test Settings

6. On the Target Servers page, clickAdd. The source server and the target server must be in thesame Exchange organization and site. On the Select Target Servers page, search for available

target servers, select the Mailbox server you want, and then clickAdd. ClickOKand then click

Next (Figure 8).

7. On the Summary page, review the settings, and clickCreate (Figure 9).


57/96

Figure 8: Target Servers


58/96

Figure 9: Summary

Configure Inter-Organization Mail Flow (Cont.)

We will now configure inter-organization mail flow transactions or mail flow transactions to the Internet.

This method will work for any destination mail service that is able to generate a delivery receipt and

accepts SMTP addresses. Perform the following steps to configure inter-organization mail flow:

1. To configure inter-organization and Internet mail flow transactions, go to Object DiscoveriesunderManagement Pack Objects in the Authoring node in the Operations Console. Ensure

that your console is not scoped to a subset of management pack objects. In the Look for box,type Cross and clickFind now.

2. Right-click the Exchange 2007 Mailflow Cross Organization Discovery, clickOverrides |Override the Object Discovery | For a specific object of class: Exchange 2007 Mailbox Role

(Figure 10).

3. Select the Exchange 2007 Mailbox server you want to use as the source server, and clickOK(Figure 11).


59/96

Figure 10: Override the Object Discovery: Exchange 2007 Mail Flow Cross Organization Discovery


60/96

Figure 11: Select Object

4. On the Override Properties dialog box, change the Target Addresses parameter. Thedestination mail service must be able to generate a delivery receipt. Choose a destination

management pack to save the override, and clickOK(Figure 12). This synthetic transactionruns every 30 minutes by default.


61/96

Figure 12: Exchange 2007 Mail Flow Organization Discovery: Override Properties

A discovery will now run that generates a new instance of an inter-organization mail flow perspective.

(This discovery runs every 24 hours by default.) To check that the perspective was created, go to the Mail

Flow State view, which will show all instances of mail flow perspectives.

Configure Client Access Server Synthetic Transactions

Microsoft Office Outlook Web Access, Exchange ActiveSync, Exchange Web Services, POP3 and IMAP

services are tested by running some PowerShell cmdlets, supported by the Exchange 2007 MP:

Test-OwaConnectivity Test-ActiveSyncConnectivity Test-WebServicesConnectivity. Test-PopConnectivity Test-ImapConnectivity

These cmdlets require a special test mailbox on each Exchange Server 2007 Mailbox server managed byOperations Manager.


62/96

To create the test mailbox, on each Exchange 2007 Mailbox server, open the Exchange Management

Shell, locate the Scripts directory under the installation path for Exchange Server 2007 (usually \Program

Files\Microsoft\Exchange Server\Scripts) and execute the scriptNew-TestCasConnectivityUser.ps1

(Figure 13).

Figure 13: New-TestCASConnectivityUser.ps1

To monitor external Outlook Web Access URL, you must set an external URL on your Outlook Web

Access virtual directory, by running a PowerShell cmdlet or by using the Exchange Management

Console:

Exchange Management Shell (Figure 14):

Set-OwaVirtualDirectory "\owa (Default Web site)" -externalurl:"https:///owa"

Exchange Management Console (Figure 15):

Open the Exchange Management Console, select Server Configuration, select Client Access,and then click the Outlook Web Access tab.

In the work pane, select the virtual directory that you want to modify, and then clickProperties.

In the virtual directory properties dialog box, select the tab that contains the properties that youwant to modify. ClickOKto save your changes and close the properties window.


63/96

Figure 14: Setting the OWA external URL by using the Command Shell


64/96

Figure 15: OWA (Default Web Site) Properties

After preparing all the Exchange 2007 CAS to be monitored, use the following procedure to configure

client access synthetic transactions.

1. Click the Authoring button in the Operations Console, and then clickAdd Monitoring Wizardfrom the Actions pane. On the Select Monitoring Type page, select Exchange 2007 ClientAccess Server Monitoring, and clickNext (Figure 16).

2. On the General Properties page, type the Name for the object, optionally type a Description,select a destination management pack from the list and clickNext (Figure 17).


65/96

Figure 16: Select Monitoring Type


66/96

Figure 17: General Properties

3. On the Source Server page, select the Exchange organization where the tests will occur,search a Source server from the list of available servers and clickNext (Figure 18). The

management pack runs the synthetic transaction on the source server you designate.


67/96

Figure 18: Source Server

4. On the Test Settings page, specify the Test frequency value (between 5 and 60 minutes).Ensure that the test frequency you specify is more than two times greater than the Time-out

value (between 10 and 1,200 seconds) you specify (take into account the fact that the test

frequency is measured in minutes and the test time-out is measured in seconds). Select one or

more Test types, and then clickNext (Figure 19).


68/96

Figure 19: Test Settings

5. On the Target Servers page, clickAdd to search for Exchange 2007 mailbox servers that hoststhe user mailbox used in the transaction test. Available target servers are limited to Exchange

2007 mailbox servers residing in the same Active Directory site as the Client Access server

specified as the source server and are monitored by this management group. ClickNext (Figure

20).6. On the Summary page, review the settings, and clickCreate (Figure 21).


69/96

Figure 20: Target Servers


70/96

Figure 21: Summary

Summary

Wizard-style configuration of synthetic transactions was one of the great improvements of the native

Exchange 2007 MP. With 8 steps already covered in the past 4 parts, the next part will have the final 3

steps to conclude the configuration process:

Configuring the Log Shipping Replay Queue Length Monitor for SCR and CCR Scenarios. Enabling Remote Unified Messaging Connectivity Monitoring. Adjust the Best Time to Run Report Data Collection Scripts / Resource-Intensive Rules and

Monitors




71/96



Configuring the Exchange 2007 MP to monitor SCR/CCR Log Shippingand Unified Messaging servers, adjusting resource intensive operations to

minimize impact on Exchange servers.

9. Configuring the Log Shipping Relay Queue Length

Monitor for SCR and CCR Scenarios

The Exchange 2007 MP contains monitors to check the Log Shipping Replay Queue Lengths for both

cluster continuous replication (CCR) and standby continuous replication (SCR) scenarios. This monitor,

by default, raises an alert if the number of transaction logs waiting to be committed is greater than 15 logsand has been waiting for more than 5 minutes.

You should configure an override for this monitor, especially if you are using SCR, since the threshold is

optimized for CCR configurations.

1. To override the Log Shipping ReplayQueueLength Monitor, click the Authoring button inthe Operations Console, and then clickMonitors, underManagement Pack Objects. Set the

scope toExchange 2007 Log Shipping. Expand Entity Health, and then expand Performance to

expose the 2 pertinent monitors.

2. Right clickLog ShippingReplayQueueLenght Monitor, select Overrides | Override theMonitor | For all objects of class: Exchange 2007 Log Shipping (Figure 1). If you want to

specify the override only for some servers (if you have both CCR and SCR), select instead For aspecific object of class: Exchange Log Shipping.


72/96

Figure 1: Override the Monitor: Log Shipping ReplayQueueLenght Monitor

3. On the Override Properties dialog box, configure the Threshold parameter with a valueappropriate for your environment (Figure 2). You can use the performance data collected by the

Exchange 2007 Reply Queue Length Collection rule to help determine the appropriate value.

4. Repeat previous steps forLog Shipping CopyQueueLenght Monitor (Figure 3).


73/96

Figure 2: Log Shipping ReplayQueueLenght Monitor: Override Properties


74/96

Figure 3: Log Shipping CopyQueueLenght Monitor: Override Properties

9.1 Enable Remote Unified Messaging Connectivity

Monitoring

You need to modify the parameters of the script that executes Test-UMConnectivity to provide a

telephone number and an IP gateway, in order to monitor remote voice connectivity.

The rule that performs remote connectivity checks must be provisioned with 2 necessary parameters:

Extension number: the cmdlet must know which telephone number to call and it must be anumber that will be answered by a Unified Messaging server (Figure 4). This phone number

should preferably be the subscriber access number, which provides access to users to the

Outlook Voice Access and directory search to unauthenticated callers. The Phone number can

also be the number answered by Auto Attendant, if youre testing a server dedicated to Auto

Attendant only.

Name of the IP gateway: the cmdlet must know the identity of an IP gateway that connects it tothe telephone network.
http://technet.microsoft.com/en-us/library/aa997953%28EXCHG.80%29.aspxhttp://technet.microsoft.com/en-us/library/aa997953%28EXCHG.80%29.aspx


75/96

Figure 4: Subscriber Access Number

After you have identified the appropriate UM IP Gateway and Phone parameters, you must use the

following steps to enable the rule and to create an override for the script parameters:

1. In the Operations Manager Operations Console, click the Authoring tab, expand ManagementPack Objects and the select Rules. In the Look For box, enterExchange 2007 Test UM

Connectivity, and then clickFind Now.

2. Right-click the rule Exchange 2007 Test UM Connectivity Remote Voice Collection, selectOverrides | Override the Rule | For all objects of class: Exchange 2007 Unified Messaging

Role (Figure 5).


76/96

Figure 5: Override the Rule: Exchange 2007 Test UM Connectivity

3. In the Override Properties dialog box (Figure 6), select the Override column for the EnabledParameter name, and then check that the Override Setting is set to True. Select the Override

column for the Phone parameter name, and then insert the appropriate number as identified

previously. Finally override the UM IP Gateway parameter with the name of your UM IP

Gateway. Select a destination management pack and clickOK.


77/96

Figure 6: Override Properties: Exchange 2007 Test UM Connectivity Remote Voice Collection

4. You must also override the Exchange 2007 Test UM Connectivity Remote Voice Monitor inthe same way as you did the rule (Figure 7). Use exactly the same override values as you used

for the rule, otherwise the cmdlet will run twice (Figure 8).


78/96

Figure 7: Override the Monitor: Exchange 2007 Test UM Connectivity Remote Voice Monitor


79/96

Figure 8: Exchange 2007 Test UM Connectivity Remote Voice Monitor: Override Properties

9.2 Adjust the Best Time to Run Report Data

Collection Scripts/Resource- Incentive Rules and

Monitors

There are certain resource intensive operations, such as the Report Data Collection Scripts and a few

Rules and Monitors that you should know their scheduled time to run and perform some adjustments, as

these could impact normal Exchange servers operation.

The Exchange Server 2007 Reporting Management Pack collects information on a daily basis to report on

a set of objects on the Exchange 2007 Mailbox Servers. To mitigate the impact on the Exchange servers,

the report data collection scripts use a Sync Time parameter to ensure that the scripts only run during an

assigned time period, with a default time-out value of 10 minutes. The script run times are also distributed

to ensure that only one script runs at a time.

By default, the report collection scripts run according to the schedule below.


80/96

Rule TargetDefault Run

Time

Exchange 2007 Database File Growth Exchange 2007 Database 7:10 PM

Exchange 2007 Top N Mailboxes by Message Count Exchange 2007 Mailbox Role 7:20 PM

Exchange 2007 Top N Mailboxes by Size Exchange 2007 Mailbox Role 7:25 PM

Exchange 2007 Top N Public Folders by Message

Count

Exchange 2007 Public Folder

Database 7:30 PM

Exchange 2007 Top N Public Folders by SizeExchange 2007 Public Folder

Database7:35 PM

Exchange 2007 Average Mailbox Size per Database Exchange 2007 Mailbox Database 7:40 PM

Exchange 2007 Mailbox Count per Database Exchange 2007 Mailbox Database 7:45 PM

Table 1: Schedule of the report collection scripts

1. To change the time that the Report Data Collection Scripts run, in the Operations ManagerOperations Console, click the Authoring tab, expand Management Pack Objects and the select

Rules. In the Look For box, enter the name of the rule you want to reschedule (Exchange 2007

Database File Growth in this example), and then clickFind Now.2. Right-click the rule Exchange 2007 Database File Growth, select Overrides | Override the

Rule | For all objects of class: Exchange 2007 Database (Figure 9).

3. In the Override Properties dialog box, modify the Sync Time parameter to the new time,choose a destination management pack and clickOK(Figure 10).

Figure 9: Override the Rule: Exchange 2007 Database Growth


81/96

Figure 10: Exchange 2007 Database Growth: Override Properties

The next table lists a set of rules, monitors, and synthetic transactions that run according to a schedule and

are resource-intensive, meaning they could also impact CPU utilization on the Exchange server when they

are running.

Rule/Monitor Type Run On ServerDefault Sync

Time

Exchange 2007 Test Active Sync Connectivity Monitor Monitor CAS Server 12:01 AM

Exchange 2007 Test Active Sync Connectivity Collection Rule CAS Server 12:01 AM

Exchange 2007 MDB Disk Free Space Monitor Monitor Mailbox Server 12:01 AM

Exchange 2007 Log Disk Free Space Monitor Monitor Mailbox Server 12:02 AM

Exchange 2007 Test IMAP Connectivity Monitor Monitor CAS Server 12:03 AM

Exchange 2007 Test IMAP Connectivity Collection Rule CAS Server 12:03 AM

Exchange 2007 Test Local Mail Flow Monitor Monitor Mailbox Server 12:03 AM

Exchange 2007 Test Local Mail Flow Collection Rule Mailbox Server 12:03 AM

Exchange 2007 Test MAPI Connectivity Monitor Monitor Mailbox Server 12:04 AM

Exchange 2007 Test MAPI Connectivity Collection Rule Mailbox Server 12:04 AMExchange 2007 Test OWA Connectivity Internal Monitor Monitor CAS Server 12:05 AM


82/96

Exchange 2007 Test OWA Connectivity Internal Collection Rule CAS Server 12:05 AM

Exchange 2007 Test OWA Connectivity External Monitor Monitor CAS Server 12:07 AM

Exchange 2007 Test OWA Connectivity ExternalCollection

Rule CAS Server 12:07 AM

Exchange 2007 Test Remote Mail Flow Monitor Monitor Mailbox Server 12:08 AM

Exchange 2007 Test Remote Mail Flow Collection Rule Mailbox Server 12:08 AM

Exchange 2007 Test POP3 Connectivity Monitor Monitor CAS Server 12:09 AM

Exchange 2007 Test POP3 Connectivity Collection Rule CAS Server 12:09 AM

Exchange 2007 Test Web Services Connectivity Monitor Monitor CAS Server 12:11 AM

Exchange 2007 Test Web Services Connectivity Collection Rule CAS Server 12:11 AM

Exchange 2007 Test Cross Org Mail Flow Monitor Monitor Mailbox Server 12:12 AM

Exchange 2007 Test Cross Org Mail Flow Collection Rule Mailbox Server 12:12 AM

Exchange 2007 Test System Health Rule All Server 7:00 PM

Exchange 2007 Queue Disk Free Monitor Monitor Hub/Edge Server None

Table 2

Just like the report data collection rules, to mitigate the impact on the Exchange servers, these objects usea Sync Time parameter to minimize the number of simultaneously running rules or monitors. The script

run times are also distributed to ensure that only one script runs at a time.

To change the time that the rule, monitor, or synthetic transactions run, override the Sync Time for the

one you want to change. When you override the Sync Time for a rule, ensure that you use the same

override for the corresponding monitor, so that rules and corresponding monitors do not run twice. This

does not apply to rules that do not have corresponding monitors.

As an example, I will detail the required steps to change the Exchange 2007 MDB Disk Free Space

Monitor:

1. In the Operations Manager Operations Console, click the Authoring tab, expand ManagementPack Objects and the select Monitors. In the Look For box, enter the name of the monitor youwant to reschedule (Exchange 2007 MDB Disk Free Space Monitorin this example), and then

clickFind Now.

2. Right-click the rule Exchange 2007 MDB Disk Free Space Monitor, select Overrides |Override the Monitor | For all objects of class: Exchange 2007 Mailbox Database Disk

(Figure 11 Figure 9).3. In the Override Properties dialog box, modify the Sync Time parameter to the new time,

choose a destination management pack and clickOK(Figure 12).


83/96

Figure 11: Override the Monitor: Exchange 2007 MDB Disk Free Space Monitor


84/96

Figure 12: Exchange 2007 MDB Disk Free Space Monitor: Override Properties

Summary

It took 5 parts to go through all of the 11 configuration steps of the native Exchange MP, but we are not

over yet. The next and final part of this series will cover co-existence and migration scenarios for theprevious converted Exchange Management Pack. Common Troubleshooting and Reports will be the last

topics covered in the article.




85/96



Additional steps in the Exchange 2007 MP configuration process:migration options for the previous version of the converted Exchange

management pack, common troubleshooting and reporting.

Co-Existence with the Previous Version of Exchange

Server 2007 MP

If you are using the previously released version of the Exchange Server 2007 converted management

pack, please be aware that a direct upgrade is not possible to this new, native version of the MicrosoftExchange Server 2007 Management Pack.

There are some migration options though for you to consider. The following table (from theofficialdocumentation) illustrates the possible options, as well as the pros and cons of each scenario:

Option Pros Cons

Delete the previously

released, converted

management pack. Then

import the native Exchange

Server 2007 Management

Pack.

The simplest approach.

You delete the converted

Exchange Server 2007

Management Pack and thenimport the native Exchange

Server 2007 Management

Pack.

In this scenario, you lose all the historical data of

the converted management pack, includingreporting data.

Keep the previously

released, converted

management pack and use asecond management group

and multi-homing for the

new, native management

pack.

You keep the history fromthe converted management

pack, including reporting

data.

A more complex approach with the overhead of

setting up a second management group for thenative management pack and multi-homing the

Exchange 2007 agents to report to both

management groups. Disable the Exchange 2007

synthetic transactions from one of the managementgroups because synthetic transactions consume

CPU, disk IO, and memory resources on the

Exchange 2007 servers. Eventually, you should

disable the converted management pack synthetic

transactions because the native management packsynthetic transactions use fewer resources on the

Exchange 2007 servers.

Keep the previously

released, converted

management pack and plan

a gradual introduction ofthe new, native

management pack by

enabling server role

discoveries on a server-by-

server basis.

You keep the history from

the converted management

pack, including reportingdata. There is less

complexity because you

only use one management

group.

An increasingly complex end-to-end migration

solution because, although you avoid using asecond management group, you incur management

overhead on a server-by-server basis to enable

server role discoveries of the native management

pack. As you enable servers to be discovered by

the native management pack, you must disable thediscoveries for the same servers in the converted

management pack. There is additional

administrative overhead to run the Operations

Manager Remove-disabledMonitoringObject

cmdlet to remove the converted management packs

objects from the management group in order to

avoid running synthetic transactions from both

management packs at the same time.
http://technet.microsoft.com/en-us/library/dd772509.aspxhttp://technet.microsoft.com/en-us/library/dd772509.aspxhttp://technet.microsoft.com/en-us/library/dd772509.aspxhttp://technet.microsoft.com/en-us/library/dd772509.aspxhttp://technet.microsoft.com/en-us/library/dd772509.aspxhttp://technet.microsoft.com/en-us/library/dd772509.aspx


86/96

Table 1: Migration options for the previous Exchange 2007 MP

As you have hopefully realized by now, in order to keep historical data from the old Exchange MP, the 2

supported scenarios are quite complex. Fortunately, the Operations Manager Product Team has made

available a new unsealed management pack that will automatically disable the monitoring from the oldMP to avoid duplication of monitoring.

The provided management pack,Microsoft.Exchange.2007.Disable.xml, will disable all the rules,

monitors and synthetic transactions in the old converted Exchange 2007 MP.

To obtain the management pack and for more related information, please read their blog post:New

Exchange 2007 Management Pack and Keeping Old Management Pack Data.

Common Troubleshooting Issues

There are some common problems you may get right after you import and start using the native Exchange2007 MP. I will mention a few and give you the solution.

1. No Exchange 2007 Servers Discovered

If no Exchange 2007 servers are discovered, you might want to make the discovery run more frequently

than the default (the discoveries run only once every 24 hours by default). You can change the frequency

of the Exchange 2007 Discovery Helper Discovery in Object Discoveries located underManagement

Pack Objects in the Authoring section ofthe Operations Console (Figure 1).

Of course, If you are really desperate and do not mind server downtime, you can always opt for a more

radical approach: restart the HealthService on each monitored server and then restart the OpsMgr RMS.
http://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspxhttp://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspxhttp://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspxhttp://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspxhttp://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspxhttp://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspx


87/96

Figure 1: Override Properties: Exchange 2007 Discovery Helper Discovery

To further troubleshoot the discovery process, go the Discovered Inventory underMonitoring section.

ClickChange Target Type on the Actions pane, select Agent and click OK. Select the server that isn't

correctly being discovered, from the list of available agent-managed servers, and then run Show Running

Rules and Monitors for this Health Service from the list of available Tasks.

The task will produce the output depicted on Figure 2. Copy the Task Output section to Notepad and

search for a workflow calledMicrosoft.Exchange2007.ServerRole.CcrNode.Standalone.Discovery. This

will confirm that the agent is running the discovery workflow.


88/96

Figure 2: Show Running Rules and Monitors for this Health Service

2. No Standalone Exchange 2007 Mailbox servers discovered

Standalone Exchange 2007 mailbox servers are discovered by enabling the Exchange 2007 Standalone

CCR Node Discovery. Configure the corresponding override (Figure 3) and restart the HealthService oneach mailbox server.


89/96

Figure 3: Exchange 2007 Standalone CCR Node Discovery: Override Properties

3. "No Exchange 2007 Mailbox Servers were found" message when configuring Intra-Organization

Mail Flow Synthetic Transaction

When configuring Intra-Organization Mail Flow synthetic transaction using the provided template, you

get the error message depicted on Figure 4.

Make sure the Exchange 2007 Management Pack has already discovered mailbox servers. You can wait a

while or check if the discovery process is correctly configured (see previous paragraph).


90/96

Figure 4: No Exchange 2007 Mailbox Servers were found

4. Erroneous IIS alerts on physical nodes of clusters

The IIS Management Pack, by default, checks the service statuses regardless of the startup type. This can

result in erroneous alerts on the physical nodes of clusters that have IIS stopped. We recommend

disabling the IIS Service monitors for the physical nodes of the cluster, so t

configuring native exchange 2007 scom 2007 r2

Documents