Monitoring Exchange 2010 with OpsMgr 2012

This is a step by step guide on how to configure the monitoring for Exchange Server 2010 with System Center Operations Manager 2012. 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.

Perquisites – Before you import the Microsoft Exchange Server 2010 Management Pack, take the following actions:

  • 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 2010 database availability groups (DAGs), ensure that all DAG members are monitored by Operations Manager 2012 (agent must be installed)
  • Ensure that all agents on Exchange 2010 computers have Agent Proxy enabled.
  • Determine which server will host the Correlation Engine. While not strictly required, it’s strongly recommended that the Correlation Engine be installed on the root management server emulator.

Step 1 – Installing the Exchange correlation Engine and configure Agent proxying
As mentioned before determine which server will host the Correlation Engine. While not strictly required, it’s strongly recommended that the Correlation Engine be installed on the root management server emulator.

Do the following steps on the RMS Emulator
1. Download the MP software from the Microsoft site
2. Choose the proper version (X64)
3. Launch the MSI Package and run the installation and follow the installation
It’s known that SCOM 2012 has known issues wit the correlation engine. See for more information. To stop the event flooding stop the Exchange correlation engine and change the above settings.


To enable Agent Proxy configuration on all managed Exchange servers, in the
1. Administration pane, under Administration, Device Management, Agent Managed
2. Right-click on each Exchange server, select Properties, then the Security tab
3. 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 every managed Exchange 2010 server in the list.


Step 2 – Import the Exchange 2010 Management Pack
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Right-click the Management Packs node, and then click Import Management Packs.
4. The Import Management Packs wizard opens. Click Add, and then click Add from disk.
5. If prompted to connect to the online catalog, click No.
6. The Select Management Packs to import dialog box appears. Go to the directory where your management pack file is located as extracted in Step 1. By default, the location is C:\Program Files\System Center Management Packs.
7. Select both management pack files to import from that directory, and then click Open.
8. On the Select Management Packs page, the management packs that you selected for import are listed.
9. You will receive a prompt indicating that the management pack presents a security risk. This is due to the management pack’s use of agent proxying. Click Yes to allow the import.
10. The Import Management Packs page appears and shows the progress for each management pack. Each management pack is downloaded to a temporary directory, imported to Operations Manager, and then deleted from the temporary directory. If there is a problem at any stage of the import process, select the management pack in the list to view the status details. Click Close.


Step 3 – Create Test Mailboxes for Synthetic Transaction Tests
The Exchange 2010 Management Pack can run synthetic transactions to help you measure the performance of monitored objects in your Exchange organization. The Exchange 2010 Management Pack uses the Test-OwaConnectivity, Test-ActiveSyncConnectivity, and Test-WebServicesConnectivity cmdlets to test Microsoft Office Outlook Web App, Exchange ActiveSync, and Exchange Web Services connectivity from Client Access servers to Mailbox servers.

1. Open the Exchange Management Shell.
2. In the Shell, change directory to the C:\ Program Files\Microsoft\Exchange Server\V14\Scripts folder by running the following command:
Set-Location C:\Program Files\Microsoft\Exchange Server\V14\Scripts
3. Run the test-user script using the following command:
4. Follow the on-screen installation instructions in the Shell to create the test mailbox. You’ll be prompted to enter a temporary secure password for creating test users. You’ll also be prompted to specify the Mailbox server where you want the test user created.
5. Repeat this process on all Exchange 2010 Mailbox servers in each Active Directory site that you want to test.

Possible issue:
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


Step 4 – 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.
1. In the Operations console, click Administration.
2. Right Click Management Packs
3. Create new management pack
4. Give the MP a name example: “Custom – Exchange 2010

Known Issue 1
After setting up the Exchange management pack, installing the correlation engine the SCOM server gives errors like “The Microsoft Exchange Monitoring Correlation Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs”.

Exchange 2010 Monitoring with SCOM 2012 – Correlation Service Issue

Known Issue 2
When you run the .\new-testcasconnectivityuser.ps1 script from the C:\Program Files\Microsoft\Exchange Server\v14\scripts directory you get the following error:

CreateTestUser : Mailbox could not be created.
Verify that OU ( Users ) exists and that password meets complexity requi  rements.  At C:\Program Files\Microsoft\Exchange Server\v14\scripts\new-TestCasConnectivityUser.ps1:267 char:31  +       $result = CreateTestUser <<<<  $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $  UMExtension $Prompt      + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,CreateTestUser

The error you got usually turns up if there are multiple OUs in the AD domain called Users. Resolution: Open the script new-TestCasconnectivityUser.ps1 with notepad or any other texteditor and search for the section $OrganizationalUnit = “Users” Replace ´Users´ with ´domain.local/Users´ (replace domain.local with your domain) or to a path to some OU of your choice.