Monitoring Exchange 2010 with OpsMgr 2007 R2

这几天在做SCOM的监控测试，主要针对AD和Exchange Server的监控。发现用SCOM2007R2监控Exchange2010的资料不是很多，找到两篇不错的文章，转载过来，分享下。

原文链接：http://www.toolzz.com/?p=102

This is a step by step guide on how to configure the monitoring for Exchange Server 2010 with System Center Operations Manager 2007 R2.
Normally the Microsoft Exchange 2010 MP will not automatically start monitoring all features. This article is discusses how to enable these features and to start monitoring of Exchange 2010 the proper way

1. Introduction
The Exchange 2010 MP help to monitor the enviroment efficienter with fewer people. The following scenarios are monitored:
-Service Availability
-Availibility of mounted disks and databases
-Outlook Client Performance
-Client Access Availability
-Unified Messaging Availability
-SMTP (Client Submission) Availability
-Hourly Mailflow Statistics
-Daily Mailflow Statistics
-Distribution Group UsageMaintaining and operating an Exchange 2010 infrastructure includes not only day-to-day administrative tasks, but also checking procedures which are vital for an healthy Exchange 2010 environment.

2. Exchange 2010 Management Pack Prerequisites
Consider the supported configurations for the Exchange Server 2010 Management Pack. For more information about the supported configurations, see Introduction to the Exchange 2010 Management Pack earlier in this guide.-Ensure that all Exchange 2010 computers that are managed by the Operations Manager use LocalSystem as the Agent Action Account.
- If you are monitoring Exchange Server 2010 Database Availability Groups (DAGs), ensure that all DAG members are monitored by Operations Manager 2007.
- Ensure that all agents on Exchange 2010 computers have Agent Proxy enabled.
- Install the update specified in Microsoft Knowledge Base article 971541 if you are running Operations Manager 2007 SP1. Install the update specified in Microsoft Knowledge Base article 974144 if you are running Operations Manager 2007 R2. Both of these articles and respective updates are pending release to the Microsoft Help and Support (http://go.microsoft.com/fwlink/?LinkId=5967) Web site. These updates resolve several critical issues that are more likely to occur when running the Exchange 2010 Management Pack.If for instance the Edge servers are in a DMZ and in a workgroup follow on of these articles to monitor these servers.
http://www.toolzz.com/?cat=32
http://www.toolzz.com/?cat=35

3. Step 1 – Installing the Exchange corralation Engine
The Exchange Server 2010 Management Pack includes a Windows service component called the Correlation Engine. This service determines the best alert to raise by examining the Exchange 2010 health model through the Operations Manager Software Development Kit (SDK) service. Consider the following:

o Determine which server will host the Correlation Engine. While not strictly required, it is highly recommended that the Correlation Engine service is installed on the Operations Manager Root Management Server (RMS).

o Download the Correlation Engine service package that matches the operating system for selected server. The package is available in 32-bit or 64-bit versions.

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

Do the following steps on the RMS Server
- Download the MP software from the Microsoft sitehttp://www.microsoft.com/downloads/details.aspx?FamilyID=7150bfed-64a4-42a4-97a2-07048cca5d23&displaylang=en
- Choose the proper version (X86 or X64)
- Launch the MSI Package and run the installation

4. Step 2 – Import the Exchange MP
Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.
- In the Operations console, click Administration.
- Right-click Management Packs , click Import Management Packs.
- Click Add, and then click Add from disk.
- If prompted to connect to the online catalog, click No.
- Go to the directory where your management pack file (default location is C:\Program Files\System Center Management Packs).
- Select both management pack files to import from that directory, click Open.
- Import the management
- You will receive a prompt indicating a security risk. This is due use of agent proxying. Click Yes to import
- Click Close.

5. Step 3 – Configure the MP in OpsMgr

Creating a New Management Pack for Customizations.
The Microsoft Exchange 2010 MP does not work properly out of the box, therefore we recommend to create an override management pack and save overrides for Exchange in this management pack.
- In the Operations console, click Administration.
- Right Click Management Packs
- Create new management pack
- Give the MP a name example: “Custom – Exchange 2010 – Custom event alerts for Exchange 2010″

new-TestCasConnectivityUser.ps1 fails with Verify that OU ( Users ) exists
When trying to run the new-TestCasConnectivityUser.ps1 script the latter might fail with the following error
CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requirements.
The first thing you need to do is making sure that the password does meets complexity requirements however if you did and still having the failure you most probably have multiple OUs with name “Users” and that is why the script is failing. The solution for this is to specify the OU in the command by running the following

.\new-TestCasConnectivityUser.ps1 -OU domain.com/users

1. Step 4 -Enabling Event Collection for Synthetic Transaction Rules
The Exchange 2010 Management Pack uses synthetic transactions, such as the running of the Test-MapiConnectivity, Test-OwaConnectivity, and other commands, to scan your Exchange organization for basic connection responses and to test simple operations such as logging in to a mailbox.
- Open the Operations Console, click Authoring.
- Open the Authoring pane, expand Management Pack Objects, and then click Rules.
- Open the Rules pane, click Change Scope.
- Open the Scope Management Pack Target(s), Look for box, type “Exchange Server 2010.”
- Click View all targets.
- Click Select All if it’s not disabled (it is only disabled when all rows are already selected).
- Click OK to close the dialog box.
- After the rules have loaded, type “Script event collection” in the Look for box.

For each test task that you would like to enable, perform the following steps:
- Right click on the rule and select Overrides > Override the Rule > For all objects of class: [class name].
- Save the override (Example “Custom – Exchange 2010 – Custom event alerts for Exchange 2010″)
- Click the Override checkbox.
- Set the override value to True.
- Click OK.

We have enabled the following scripts
-ActiveSync – Script event collection: Execute: Test-ActiveSyncConnectivity (Internal) diagnostic cmdlet. (Report Collection)
-Client Access Availability Service – Script event collection: Execute: Test-OutlookWebServices diagnostic cmdlet.
-Common Services – Script event collection: Execute: Test-ServiceHealth diagnostic cmdlet.
-Content Indexing Service – Script event collection: Execute: Test-ExchangeSearch cmdlet.
-Disk – Script event collection: Execute: Get site name.
-ECP – Script event collection: Execute: Test-EcpConnectivity (Internal) diagnostic cmdlet. (Report Collection)
-ECP – Script event collection: Execute: Test-EcpConnectivity (External) diagnostic cmdlet. (Report Collection)
-EdgeSync – Script event collection: Execute: Test-EdgeSyncEhf diagnostic cmdlet. (Report Collection)
-EdgeSync – Script event collection: Execute: Test-EdgeSynchronization diagnostic cmdlet. (Report Collection)
-ExBPA – Script event collection: Execute: Test-SystemHealth diagnostic cmdlet.
-IMAP4 – Script event collection: Execute: Test-IMAPConnectivity diagnostic cmdlet.
-Mailbox Monitoring – Script event collection: Execute set-CasConnectivityCredentials cmdlet.
-Mailbox Monitoring – Script event collection: Execute: Test-MAPIConnectivity diagnostic cmdlet. (Report Collection)
-Mailbox Replication Service – Script event collection: Execute: Test-MRSHealth diagnostic cmdlet. (Report Collection)
-Outlook Server Availability – Script event collection: Execute: Test-OutlookConnectivity diagnostic cmdlet (Enterprise Internal)
-Outlook Server Availability – Script event collection: Execute: Test-OutlookConnectivity diagnostic cmdlet (Internal)
-Outlook Service Availability – Script event collection: Execute: Test-OutlookConnectivity diagnostic cmdlet (AutoDiscover)
-OWA – Script event collection: Execute: Test-OwaConnectivity (External) diagnostic cmdlet. (Report Collection)
-OWA – Script event collection: Execute: Test-OwaConnectivity (Internal) diagnostic cmdlet. (Report Collection)
-Remote PowerShell – Script event collection: Execute: Test-PowerShellConnectivity (Internal) diagnostic cmdlet. (Report Collection)
-Replay Service – Script event collection: Execute: Test-ReplicationHealth diagnostic cmdlet. (Report Collection)
-WebServices – Script event collection: Execute: Test-WebServicesConnectivity (Internal) diagnostic cmdlet.

See http://technet.microsoft.com/en-us/library/ff360256.aspx for more information

NOTE: There are some issues with scripts these not working scripts are not added. See the link for more information

2. Step 5 – Enabling External Outlook Web Access Connectivity Monitoring
Microsoft Outlook fat client, Exchange ActiveSync, and Exchange Web Services are tested by PowerShell cmdlets: Test-OwaConnectivity, Test-ActiveSyncConnectivity, and Test-WebServicesConnectivity.
These cmdlets require a special test mailbox on each Exchange Server 2010 Mailbox server managed by Operations Manager. If this script is has not runned you get the error like the example below.

To create this test mailbox, execute this script on all Mailbox servers;
-Open the Exchange Management Shell,
-Locate the Scripts directory under the installation path for Exchange Server 2010 (usually \Program Files\Microsoft\Exchange Server\Scripts) and execute the script New-TestCasConnectivityUser.ps1).

-Repeat this process on each Exchange Server 2010 Mailbox server that is to be tested.
!! If it works go to step 6

3. Step 5 – fix the TestCasConnectivityUser.ps1 (Optional)
NOTE; If the script fails follow the following steps
When we tried to run new-TestCasConnectivityUser.ps1 to create some mailboxes for the tests we ran into tho following problems.

We got an errormessage saying “CreateTestUser : Mailbox could not be created. Verify that OU ‘Users’ exists and that password meets complexity require”The OU exists, was not duplicate and the password is OK. After some investigation this is an error in the script.To solve this copy the follow the following steps.
-Create a new OU in Active Directory (Exchange2010)
-locate the script (default \Program Files\Microsoft\Exchange Server\Scripts)
-Edit the new-TestCasConnectivityUser.ps1.
-Goto line 164 -> $OrganizationalUnit = “Users”
-Change it to $OrganizationalUnit = “Exchange2010″

4. Step 6 – Set the OWA Adress to test webmail connectivity
To successfully test you’re OWA connection it’s important to set the “Outlook Web Access URL” properly. This is done via the following script on all the CAS servers.
-Open the Exchange Management Shell,
-Locate the Scripts directory under the installation path for Exchange Server 2010 (usually \Program Files\Microsoft\Exchange Server\Scripts)
-Set-OwaVirtualDirectory “<Server name>/owa (Default Web site)” -externalurl:https://<Fully Qualified Domain Name>/owa
Example “Set-OwaVirtualDirectory “EXCA001/owa (Default Web site)” -externalurl:https://DEMO.COM/owa”

Do this on all CAS Servers

The proper OWA settings

5. After these steps check if everything works
Walk through the Exchange MP view to check if all scripts are working