Configuring the Native Exchange 2007 MP for OpsMgr 2007 R2

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part1.html[/CODE]

[IMG]http://www.msexchange.org/img/upl/ruijmsilva1115971479189.jpg[/IMG]
[B][B]Rui Silva[/B][/B]
[SIZE=3][B]
PART-1[/B][/SIZE]

[B]Introduction[/B]

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; [URL="http://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part1.html"]Monitoring Exchange 2007 With System Center Operations Manager 2007[/URL], 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:

[LIST][*]Template (wizard style) for configuring Client Access server synthetic transactions against Outlook Web Access (OWA), Exchange ActiveSync, Web Services, POP3, and IMAP.[*]Template (wizard style) for configuring Exchange 2007 Intra-organizational mail flow synthetic transactions between agent-managed Exchange 2007 Mailbox servers.[*]New set of reports specific to Exchange 2007. Enhanced object search and filtering so that the report search feature automatically searches for the objects that the report expects.[*]The management pack improves Exchange disk monitoring by providing support for mount points 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 actionable or may be noisy are disabled (60% reduction in noise-based alerts). Note that many of these rules are still in the management pack so that you can enable them if necessary.[*]Support for monitoring multiple Exchange organizations using a single Operations Manager 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 to resolve alerts.[*]Improved topology discovery.[*]Improved synthetic transactions. This management pack improves the performance and support for the Exchange 2007 synthetic transactions in several ways:
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:
- [URL="http://go.microsoft.com/fwlink/?LinkID=137740"]Test-Mailflow[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137741"]Test-SystemHealth[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137732"]Test-OwaConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137733"]Test-ActiveSyncConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137734"]Test-WebServicesConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137735"]Test-PopConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137736"]Test-ImapConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=137739"]Test-MapiConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=151496"]Test-UMConnectivity[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=148796"]Test-ExchangeSearch[/URL]
- [URL="http://go.microsoft.com/fwlink/?LinkID=148797"]Test-ReplicationHealth[/URL][*]The discovery of Exchange 2007 server roles is disabled by default and minimal Exchange 2007 monitoring 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 the Operations Manager environment.[/LIST]
The following table provides an overview of the Exchange Server 2007 MP monitoring functionality that is enabled through Operations Manager 2007 R2:

[B]Exchange component[/B]
[B]Monitoring functionality[/B]
Exchange Client Access

[LIST][*] ActiveSync and OWA connectivity monitoring including synthetic transactions[*] Performance measuring and alerting[/LIST]
Exchange Edge Transport

[LIST][*] Performance measuring and alerting[/LIST]
Exchange Hub Transport

[LIST][*] Performance measuring and alerting[/LIST]
Exchange Mailbox

[LIST][*] Information Store monitoring[*] Mail flow and MAPI connectivity monitoring[*] Performance measuring and alerting[/LIST]
Exchange Unified Messaging

[LIST][*] Unified Messaging connectivity monitoring including synthetic transactions[*] Performance measuring and alerting[/LIST]
Configuration and Security

[LIST][*] Exchange best practices (ExBPA)[/LIST]
Exchange Event Log monitoring

[LIST][*] Comprehensive rules for Exchange[*] Detailed product knowledge about events[/LIST]
[B]Table 1: [/B]Exchange 2007 MP monitoring functionalities
[B]Solution Topology[/B]

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.

[B]Name[/B]
[B]Role[/B]
[B]Architecture[/B]
[B]Software[/B]
[B]OPSMGR2K7R2[/B]
Root Management Server
X64
Windows Server 2008 R2
System Center Operations Manager 2007 R2
[B]E2K7-x64[/B]
Domain Controller
Mailbox Server
CAS Server
HUB Transport Server
x64
Windows Server 2008 SP2
Exchange Server 2007 SP2
[B]E2K7-MBX2[/B]
Mailbox Server
Unified Messaging
SCR Target
X64
Windows Server 2008 SP2
Exchange Server 2007 SP2
[B]E2K7EDGE[/B]
Edge Server
x64
Windows Server 2003 R2 SP2
Exchange Server 2007 SP1 + UR9
[B]Table 2: [/B]List of servers
[B]Exchange 2007 Management Pack Pre-Requisites and Considerations[/B]

There are no special requirements for the new native Exchange 2007 MP, nevertheless I’d like to mention the following system requirements:

[LIST][*] This MP is for System Center Operations Manager 2007 R2 and will not run on any previous version, such as Operations Manager 207 SP1.[*] Install Windows PowerShell and the Operations Console on your root management server. This is required because the Exchange Server 2007 Management Pack workflows require Windows PowerShell to run successfully.[*] Exchange Server 2007 Service Pack 1 is required (mainly because some performance counters were renamed with this release).[*] 64-bit platforms only![/LIST]
There are some limitations and considerations that you should be aware of:

[LIST][*] The maximum tested number of simultaneous synthetic transactions on an agent-monitored Exchange 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).[*] This management pack does not monitor Network Load Balanced clusters that you may have set up 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 both management packs in parallel is a supported scenario, but not recommended. [*] Increase the size of the Windows PowerShell Event Log on managed Exchange 2007 servers running on Windows Server 2003 (default size is 512 KB as depicted on [B]Figure [/B][B]1[/B]). Configure the size of the event logs on the local server and the Overwrite property to avoid error conditions resulting from the increase in events due to running synthetic transactions ([B]Figure [/B][B]2[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0041260388405044.jpg[/IMG]
[B]Figure 1:[/B] PowerShell Event Log Properties
[B][IMG]http://www.msexchange.org/img/upl/image0061260388405044.jpg[/IMG]
Figure 2:[/B] PowerShell Log full
[B]Installation and Configuration Procedures[/B]

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, I’m pretty sure these are the most common in a typical organization:

[LIST=1][*] Install the Operations Manager agent on all Exchange 2007 servers you want to manage, and enable agent proxy.

1.1. Install the agent manually on Edge Server.[*] Create a new management pack in which you store overrides and other customizations.[*] Download and import the native Exchange 2007 MP and also recommended additional management packs.[*] [LEFT]Enable Exchange 2007 Server Role discoveries to discover Exchange 2007 servers and to start monitoring them.[/LEFT][*] Configure disk monitoring.[*] Configure Internet Information Services (IIS) Monitoring. [*] Assign Edge servers to a particular organization and site. [*] 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.[*] Configure the Log Shipping Replay Queue Length Monitor for SCR and CCR Scenarios.[*] Enable Remote Unified Messaging Connectivity Monitoring.[*] Adjust the Best Time to Run Report Data Collection Scripts / Resource-Intensive Rules and Monitors.[/LIST]
[B]Summary[/B]

This concludes part 1 of this 6-part article. In the next part we’ll cover the first 3 steps of the previously mentioned installation and configuration process

[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part2.html[/CODE]

[SIZE=3][B]PART-2[/B][/SIZE]

[B]Introduction - Add The Exchange Servers as Agent Managed Computers[/B]

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;

[LIST=1][*] Click the [B]Administration[/B] tab and then click [B]Configure computers and devices to manage[/B] on the [B]Actions[/B] pane. This will start the Computer and Device Management Wizard (Figure 3). Click [B]Next[/B], choose [B]Advanced Discovery[/B] (Figure 4) and select [B]Servers Only[/B] from the [B]Computers and Device Classes[/B] drop-down box. [/LIST]
[IMG]http://www.msexchange.org/img/upl/image0021263239628452.jpg[/IMG]
[B]Figure 3[/B][B]: [/B]Computer and Device Management Wizard
[IMG]http://www.msexchange.org/img/upl/image0041263239628467.jpg[/IMG]
[B]Figure 4[/B][B]:[/B] Advanced discovery

[LIST=1][*] On the next window, browse for the computers you are adding (Figure 5) and click [B]Next[/B]. Select [B]Use selected Management Server Action Account[/B] (Figure 6), click [B]Discovery[/B] 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. Click [B]Finish[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0061263239628467.jpg[/IMG]
[B]Figure 5[/B]: Discovery Method
[IMG]http://www.msexchange.org/img/upl/image0081263239628467.jpg[/IMG]
[B]Figure 6[/B]: Administrator Account
[IMG]http://www.msexchange.org/img/upl/image0101263239732889.jpg[/IMG]
[B]Figure 7[/B][B]:[/B] Select Objects to Manage
[IMG]http://www.msexchange.org/img/upl/image0121263239732889.jpg[/IMG]
[B]Figure 8[/B]: Summary

[LIST=1][*] If the agent installation was successful, on each Exchange server you will be able to see the System Center Operations Manager 2007 R2 Agent listed on the [B]Add/Remove Programs[/B] or [B]Programs and Features[/B] on Windows 2008 (Figure 9). A new service is also created, the [B]System Center Management Service[/B], as depicted in Figure 10.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0141263239732889.jpg[/IMG]
[B]Figure 9[/B][B]:[/B] Programs and Features (Add/Remove Programs)
[IMG]http://www.msexchange.org/img/upl/image0161263239732905.jpg[/IMG]
[B]Figure 10[/B][B]:[/B] System Center Management Service Properties

[LIST=1][*] To enable Agent Proxy configuration on all managed Exchange servers, in the [B]Administration[/B] pane, under [B]Administration[/B], [B]Device Management[/B], [B]Agent Managed[/B], right-click on each Exchange server (Figure 11), select [B]Properties[/B], then the [B]Security[/B] tab (Figure 12), and check the box [B]Allow this agent to act as a proxy and discover managed objects on other computers[/B]. This step will also make exchange cluster instances to appear in the [B]Agentless Managed[/B] section (ensure that all physical nodes of the cluster are monitored). Repeat the process for every managed Exchange 2007 server in the list.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0181263239838686.jpg[/IMG]
[B]Figure [/B][B]11: [/B]Agent Managed Properties
[IMG]http://www.msexchange.org/img/upl/image0201263239838686.jpg[/IMG]
[B]Figure 12[/B][B]:[/B] Enabling Agent Proxy
[B]Installing the Agent on Edge Server[/B]

Just like in my previous [URL="http://www.msexchange.org/articles_tutorials/exchange-server-2007/monitoring-operations/monitoring-exchange-2007-system-center-operations-manager-2007-part2.html"]article[/URL], 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.
[IMG]http://www.msexchange.org/img/upl/image0221263239838686.jpg[/IMG]
[B]Figure 13:[/B] Certificate Authentication
Although the configuration process is pretty much the same as the above mentioned article, let's quickly review the necessary steps:

[LIST=1][*] In this scenario, the agent must be manually installed. From the Edge server, browse to the folder where you installed the OpsMgr binaries on the Management server. In my case this was [B]\\OPSMGR2K7R2\C$\Program Files\System Center Operations Manager 2007\AgentManagement\AMD64\[/B] (Figure 14). Double Click [B]MOMAgent.msi[/B] to trigger the setup process (Figure 15). Click [B]Next[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0241263239838702.jpg[/IMG]
[B]Figure 14[/B][B]:[/B] Agent installation binaries
[IMG]http://www.msexchange.org/img/upl/image0261263239944905.jpg[/IMG]
[B]Figure 15[/B][B]:[/B] Operations Manager Agent Setup

[LIST=1][*]On the [B]Destination Folder[/B] window (Figure 16), accept the default installation path and click [B]Next[/B]. On the next window (Figure 17), click [B]Next[/B] to specify Management Group information.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0281263239944905.jpg[/IMG]
[B]Figure 16[/B][B]:[/B] Destination Folder
[IMG]http://www.msexchange.org/img/upl/image0301263239944920.jpg[/IMG]
[B]Figure 17[/B][B]: [/B]Management Group Configuration

[LIST=1][*]On the [B]Management Group Configuration[/B] window (Figure 18), specify the [B]Management Group Name[/B], the [B]Management Server[/B] and the [B]Management Server Port[/B]. Click [B]Next[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0321263239944920.jpg[/IMG]
[B]Figure 18[/B][B]:[/B] Management Group Configuration (Cont.)

[LIST=1][*]On the [B]Agent Action Account[/B] window (Figure 19), select Local System and click [B]Next[/B]. Review the summary (Figure 20), click [B]Install[/B] and them [B]Finish[/B] (Figure 21).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0341263240046905.jpg[/IMG]
[B]Figure 19[/B][B]:[/B] Agent Action Account
[IMG]http://www.msexchange.org/img/upl/image0361263240046905.jpg[/IMG]
[B]Figure 20[/B][B]:[/B] Ready to Install
[IMG]http://www.msexchange.org/img/upl/image0381263240046920.jpg[/IMG]
[B]Figure 21[/B][B]:[/B] Finish

[LIST=1][*]After these steps the agent will be installed, but it will not be able to communicate with the OpsMgr 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:

[I]MOMCertImport /SubjectName <Certificate Subject Name>[/I]

[B]Note:[/B]
You can also export the previously issued certificate to a .PFX file and run the command [I]MOMCertImport <Certificate File Name>.pfx[/I].

If you ever need to remove certificates imported with the MOMCertImport tool, just run [I]MomCertImport /Remove[/I]. For more information, please read the following article titled; [URL="http://technet.microsoft.com/en-us/library/bb735408.aspx"]Authentication and Data Encryption for Windows Computers in Operations Manager 2007[/URL].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0401263240046920.jpg[/IMG]
[B]Figure 22[/B]: Running MOMCertImport

[LIST=1][*]If you have not previously installed any manual agent, the global setting must be changed from reject to 'Review new manual agent installation in pending management view'. Open the Operations Console and on the [B]Administration[/B] pane select [B]Settings[/B]. On the right pane, expand [B]Server [/B]and click [B]Security [/B](Figure 23). Click [B]Properties[/B] and on the [B]General[/B] tab select [B]Review new manual agent installation in pending management view[/B] (Figure 24). Click [B]OK[/B] to finish.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0421263240272623.jpg[/IMG]
[B]Figure 23[/B]: Allowing manual agent installations
[IMG]http://www.msexchange.org/img/upl/image0441263240272639.jpg[/IMG]
[B]Figure 24[/B]: Global Management Server Settings - Security

[LIST=1][*]Open the Operations Console, on the [B]Administration[/B] pane expand [B]Device Management[/B] and select [B]Pending Management[/B]. On the right pane, right click each server requiring approval and select [B]Approve[/B] (Figure 25). To check if the agent is successfully approved look in the [B]Agent Managed[/B] folder for the approved agent to see if it is there.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0461263240272639.jpg[/IMG]
[B]Figure 25[/B]: Manual Agent Install Approval
[B]Create a New Management Pack for Customizations[/B]

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:

[LIST][*]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 default management pack.[*]It is easier to track and update customizations to individual management packs.[/LIST]

[LIST=1][*]In the Operations Console, click the [B]Administration[/B] button. In the Administration pane, right-click [B]Management Packs[/B] and then click[B] Create Management Pack[/B]. The [B]Create a Management Pack[/B] wizard displays.[*]In the [B]General Properties[/B] page (Figure 26), type a name for the management pack in [B]Name[/B], the correct version number in [B]Version[/B], and a short description in [B]Description[/B]. Click [B]Next[/B] and then [B]Create[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0481263240272655.jpg[/IMG]
[B]Figure 26[/B][B]:[/B] Creating a Custom MP for customizations
[LEFT]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:[/LEFT]

[LIST][*] [LEFT]Plan logical groupings of synthetic transactions. Plan to group synthetic transactions in management packs so that it will be easy later for you to find a particular synthetic transaction.
[/LEFT][*] [LEFT]When you make a change to a synthetic transaction within a management pack, the whole management 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 are redistributed to the servers involved in those transactions.
[/LEFT][*] [LEFT]Do not store each synthetic transaction in a separate management pack, because the number of such management packs can grow into the hundreds, eventually having a negative impact on the Operations Manager 2007 environment.[/LEFT][/LIST]
[LEFT]For the purpose of writing this article I only used one management pack for customizations and synthetic transactions.[/LEFT]
[B]Install the Exchange Server 2007 MP[/B]

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

[LIST][*] [LEFT][URL="http://www.microsoft.com/downloads/details.aspx?FamilyId=AC7F42F5-33E9-453D-A923-171C8E1E8E55&amp;displaylang=en"]Windows Server Cluster Management Pack for Operations Manager 2007 v6.0.6702.0[/URL][/LEFT][*] [LEFT][URL="http://www.microsoft.com/downloads/details.aspx?FamilyId=008F58A6-DC67-4E59-95C6-D7C7C34A1447&amp;displaylang=en"]Active Directory Management Pack for System Center Operations Manager 2007 v6.0.7065.0[/URL][/LEFT][*] [LEFT][URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=61365290-3c38-4004-b717-e90bb0f6c148&amp;displaylang=en"]Operations Manager 2007 R2 Management Pack v6.1.7533.0[/URL][/LEFT][*] [LEFT][URL="http://www.microsoft.com/downloads/details.aspx?FamilyId=3529D233-5E3E-4B51-8F66-5D6F27005EC3&amp;displaylang=en"]Windows Server Operating System Management Pack for Operations Manager 2007 v6.0.6667.0[/URL][/LEFT][*] [LEFT][URL="http://www.microsoft.com/downloads/details.aspx?FamilyId=D351BCA8-182B-4223-8C9E-627E184BA02B&amp;displaylang=en"]Windows Server Internet Information Services for System Center Operations Manager 200 v6.0.6539.0[/URL][/LEFT][/LIST]
With the recommended additional management packs already imported, download and install the latest [URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=e9f3cd3f-9bc0-45cd-b10f-120e937ee4c4&amp;displaylang=en"]Microsoft Exchange Server 2007 Management Pack for System Center Operations Manager 2007 R2[/URL] (by the time of the writing of this article it was version 6.0.6702.0). You can find the latest Management Packs at the [URL="http://go.microsoft.com/fwlink/?LinkId=82105"]System Center Operations Manager 2007 Catalog[/URL].


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:

[LIST][*]Microsoft.Exchange.Server.2007.Discovery - Contains discoveries and common monitoring that applies to all Exchange servers[*]Microsoft.Exchange.Server.2007.Library - Contains class definitions[*]Microsoft.Exchange.Server.2007.Monitoring.Cas - Contains Client Access server (CAS) role monitoring[*]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 Client Access server roles.[*]Microsoft.Exchange.Server.2007.Reports.SLM - Contains Exchange 2007 reports using the Operations Manager R2 Service Level Management Reporting feature. Note that this is an unsealed management pack.[*]Microsoft.Exchange.Server.2007.Template - Contains the Mail Flow and Client Access server synthetic transaction templates.[*]OM2007_MP_EX2007_R2.doc - The management pack guide.[/LIST]
To import the Exchange 2007 MP, open the OpsMgr 2007 Operations Console. Click the [B]Administration[/B] tab, right-click the [B]Management Packs[/B] node and then click [B]Import Management Packs [/B](Figure 27).
Click [B]Add[/B], [B]Add from disk[/B] and then click [B]No[/B] on the [B]Online Catalog Connection[/B] window. Select all the files from the Exchange MP directory (Figure 28), click [B]Open[/B] and then click the [B]Install[/B] 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 [B]Close[/B] button.
[IMG]http://www.msexchange.org/img/upl/image0501263240375780.jpg[/IMG]
[B]Figure 27[/B]: Import Management Packs
[IMG]http://www.msexchange.org/img/upl/image0521263240375811.jpg[/IMG]
[B]Figure 28[/B]: Select Management Packs to import
[IMG]http://www.msexchange.org/img/upl/image0541263240375811.jpg[/IMG]
[B]Figure 29[/B][B]:[/B] Import Management Packs
[B]Summary[/B]

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:

[LIST][*]Enable Exchange 2007 Server Role discoveries to discover Exchange 2007 servers and to start monitoring them.[*]Configure disk monitoring.[*]Configure Internet Information Services (IIS) Monitoring.[*]Assign Edge servers to a particular organization and site[/LIST]

[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part3.html[/CODE]

[SIZE=3][B]PART-3[/B][/SIZE]

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

[B]Enable Exchange 2007 Server Role Discovery[/B]

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.

[LIST=1][*]In the Operations Console, click the [B]Monitoring[/B] button, navigate to [B]Discovered Inventory[/B] and then click [B]Change Target Type[/B] in the [B]Actions[/B] pane. In the [B]Look for[/B] field, type [I]Exchange 2007 Discovery Helper[/I], select it, and then click [B]OK[/B] (Figure 1). A list of Exchange 2007 servers appears with a status of [B]Not Monitored[/B] (Figure 2).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0021264258530840.jpg[/IMG]
[B]Figure 1:[/B] Select Items to Target
[IMG]http://www.msexchange.org/img/upl/image0041264258530840.jpg[/IMG]
[B]Figure [/B][B]2:[/B] Discovered Inventory

[LIST=1][*]Next, we will need to enable Exchange 2007 Server Role Discovery. Go to the [B]Object Discoveries[/B] node located under [B]Management Pack Objects[/B], in the [B]Authoring[/B] section of the Operations Console. In the [B]Look for[/B] field, type [I]Exchange 2007 Server Role[/I] and click [B]Find Now[/B]. A list of Exchange 2007 Server Role Discoveries appears (Figure 3). Notice the [B]Enabled by default[/B] column, most of the role discoveries are disabled.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0061264258553605.jpg[/IMG]
[B]Figure 3[/B]: 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.

[B]Discovery Name[/B]
[B]Description[/B]
Exchange 2007 CCR Clustered Mailbox Server Role Discovery
Discovers 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 mailbox 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
[B]Table 1: [/B]Exchange Server Role Discoveries
[B]Note:
[/B]To discover standalone Exchange Mailbox servers you have to enable Exchange 2007 Standalone CCR Node Discovery.

[LIST=1][*]The process of enabling each role is the same, for example, to enable discovery of all Edge servers, right-click the [B]Exchange 2007 Edge Role Discovery[/B] and select [B]Overrides[/B] | [B]Override the Object Discovery[/B] | [B]For all objects of class: Exchange 2007 Discovery Helper[/B] (Figure 4).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0081264258553605.jpg[/IMG]
[B]Figure [/B][B]4:[/B] Override the Object Discovery

[LIST=1][*]In the [B]Override Properties[/B] dialog box, set the [B]Enabled[/B] parameter to [B]True[/B], choose a destination management pack and click [B]OK[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0101264259006574.jpg[/IMG]
[B]Figure [/B][B]5:[/B] 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.
[B]Configure Disk Monitoring[/B]

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 better results... Why am I talking about double disk monitoring? Because Exchange 2007 disk monitoring discovers the following disks (mount points are also considered as Exchange 2007 disks):

[LIST][*] [LEFT]Disks that store an Exchange 2007 mailbox database file[/LEFT][*] [LEFT]Disks that store an Exchange 2007 mailbox log file[/LEFT][*] [LEFT]Disks that store Exchange 2007 Hub or Edge Queue files[/LEFT][/LIST]
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 the management packs (Exchange 2007 or Windows Operating System). Although the same result can be 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 system disks from the Windows Server Operating System MP (assuming system disks do not contain Exchange data files).

[LIST=1][*]To disable disk monitoring for Exchange servers from the Windows Server Operating System MP, in the [B]Authoring[/B] section of the console, go to the [B]Monitors[/B] node, under [B]Management Pack Objects[/B]. Click [B]Change Scope[/B] and in the [B]Look for[/B] field, type [I]Logical Disk[/I] (Figure 6). Select logical disk classes from all operating system versions where you are running Exchange 2007 servers and click [B]OK[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0121264259006715.jpg[/IMG]
[B]Figure [/B][B]6:[/B] Scope Management Pack Objects: Logical Disk

[LIST=1][*]Expand [B]Windows Server 200x Logical Disk[/B], expand [B]Entity Health[/B], and then expand [B]Availability[/B] to see the Logical Disk Availability and Logical Disk Free Space monitors. Right-click the [B]Logical Disk Free Space[/B] monitor, click [B]Overrides[/B] | [B]Override the Monitor[/B] | [B]For a group[/B] (Figure 7). Select the [B]Exchange 2007 Computer Group[/B], and click [B]OK[/B] (Figure 8).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0141264259006808.jpg[/IMG]
[B]Figure [/B][B]7:[/B] Override the Monitor: Logical Disk Free Space
[IMG]http://www.msexchange.org/img/upl/image0161264259006965.jpg[/IMG]
[B]Figure [/B][B]8:[/B] Select Object

[LIST=1][*]In the [B]Override Properties[/B] dialog box, set the [B]Enabled[/B] parameter to [B]False[/B], and then choose a destination management pack (Figure 9). Perform the same procedure for the [B]Logical Disk Availability Monitor[/B] (Figure 10) as well as for the other disk monitors under [B]Performance[/B]: [B]Average Disk Seconds Per Transfer[/B] (Figure 11), [B]Average Disk Seconds Per Read[/B] and [B]Average Disk Seconds Per Write[/B] (these last 2 might not be enabled by default).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0181264259092261.jpg[/IMG]
[B]Figure [/B][B]9:[/B] Logical Disk Free Space: Override Properties
[IMG]http://www.msexchange.org/img/upl/image0201264259092449.jpg[/IMG]
[B]Figure [/B][B]10:[/B] Logical Disk Availability: Override Properties
[IMG]http://www.msexchange.org/img/upl/image0221264259092496.jpg[/IMG]
[B]Figure [/B][B]11:[/B] Average Disk Seconds Per Transfer: Override Properties

[LIST=1][*]There is a specific monitor from the Windows Operating system MP called [B]Logical Disk Fragmentation Level[/B] (under [B]Performance[/B]). Although this one is not duplicated on the Exchange 2007 MP, my recommendation is to disable it as well (Figure 12).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0241264259190418.jpg[/IMG]
[B]Figure [/B][B]12:[/B] Logical Disk Fragmentation Level: Override Properties

[LIST=1][*]Repeat steps 2, 3 and 4 for logical disk monitors belonging to any other operating system versions.[*]After preventing duplication of disk alerts, we should tune the Exchange 2007 monitors to match our environment thresholds. To configure Exchange 2007 Disk Monitoring, in the Operations Console, click [B]Authoring[/B] and then click [B]Monitors[/B]. Click the [B]Scope[/B] button on the toolbar, ensure that [B]View all targets[/B] is selected and in the [B]Look for[/B] field, type [I]Disk[/I]. Select [B]Exchange 2007 Mailbox Database Disk[/B], [B]Exchange 2007 Mailbox Log Disk[/B] and [B]Exchange 2007 Queue Disk[/B], and then click [B]OK[/B] (Figure 13).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0261264259190527.jpg[/IMG]
[B]Figure [/B][B]13:[/B] Scope Management Pack Objects: Disk

[LIST=1][*]Expand [B]Exchange 2007 Mailbox Database Disk[/B], expand [B]Availability[/B] and right-click [B]Exchange 2007 MDB Disk Free Space Monitor[/B]. Select [B]Overrides[/B] | [B]Override the Monitor[/B] | [B]For all objects of class: Exchange 2007 Mailbox Database Disk[/B] (Figure 14).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0281264259190652.jpg[/IMG]
[B]Figure [/B][B]14:[/B] Override the Monitor: Exchange 2007 MDB Disk Free Space Monitor

[LIST=1][*]In the [B]Overrides Properties[/B] 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 [B]*both*[/B] 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.[*]Repeat steps [B]7[/B] and [B]8[/B] for the disk monitors from the [B]Exchange 2007 Mailbox Log Disk[/B] and [B]Exchange 2007 Queue Disk[/B] classes.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0301264259279433.jpg[/IMG]
[B]Figure [/B][B]15:[/B] Exchange 2007 MDB Disk Free Space Monitor: Override Properties
[B]Configure Internet Information Services (IIS) Monitoring[/B]

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 the Exchange Server 2007 MP.

[LIST=1][*]To disable WWW and IIS Admin Service monitors go to the [B]Monitors[/B] node, under [B]Management Pack Objects[/B] in the [B]Authoring[/B] section of the Operations Console. Set your scope to [B]Exchange 2007 Client Access Role[/B] and then expand [B]Entity Health[/B], expand [B]Availability[/B] and expand [B]Client Access Server Core Services Rollup[/B].
Right click [B]Exchange 2007 IIS Admin Service Monitor on CAS[/B] and then click [B]Overrides[/B] | [B]Disable the Monitor [/B]|[B] For all objects of class: Exchange 2007 Client Access Role[/B] (Figure 16).[*]Repeat last step for [B]Exchange 2007 WWW Publishing Service Monitor[/B] (Figure 17).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0321264259279433.jpg[/IMG]
[B]Figure [/B][B]16:[/B] Disable the Monitor: Exchange 2007 IIS Admin Service Monitor on CAS
[IMG]http://www.msexchange.org/img/upl/image0341264259279449.jpg[/IMG]
[B]Figure [/B][B]17:[/B] Disable the Monitor: Exchange 2007 WWW Publishing Service Monitor
[B]Assign Edge Servers to a Particular Organization and Site[/B]

By default, the Exchange 2007 MP assigns all Edge Transport servers to a separate organization, [I]Default-Edge Organization[/I], and site called [I]Default-Edge Site[/I]. This is what shows up in the topology view (Figure 18).
[IMG]http://www.msexchange.org/img/upl/image0361264259376090.jpg[/IMG]
[B]Figure [/B][B]18:[/B] 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.

[LIST=1][*]Go to the [B]Object Discoveries[/B] node located under [B]Management Pack Objects[/B], in the [B]Authoring[/B] section of the Operations Console. In the [B]Look for[/B] field, type [I]Exchange 2007 Site Edge[/I] and click [B]Find Now[/B]. Right-click the [B]Exchange 2007 Site Edge on Edge Discovery[/B] and select [B]Overrides[/B] | [B]Override the Object Discovery[/B] | [B]For all objects of class: Exchange 2007 Edge Transport Role[/B] (Figure 19).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0381264259376090.jpg[/IMG]
[B]Figure [/B][B]19:[/B] Override the Object Discovery: Exchange 2007 Site Edge on Edge Discovery

[LIST=1][*]In the [B]Override Properties[/B] dialog box, there are 2 parameters that can be configured: [B]AD Site Name[/B] and [B]Forest DNS Name[/B]. Modify them accordingly to match your environment, select a destination management pack and click [B]OK[/B] (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).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0401264259376105.jpg[/IMG]
[B]Figure [/B][B]20:[/B] Exchange 2007 Site Edge on Edge Discovery: Override Properties
[IMG]http://www.msexchange.org/img/upl/image0421264259376136.jpg[/IMG]
[B]Figure [/B][B]21:[/B] Exchange 2007 Topology after assigning Edge
[B]Summary[/B]

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
[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part4.html[/CODE]

[SIZE=3][B]PART-4[/B][/SIZE]

[B]Configure Synthetic Transactions[/B]

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

[LIST][*] [B]Mail flow synthetic transactions[/B] – To monitor the health (availability and latency) of several mail 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 delivery receipt)[*] [B]CAS synthetic transactions[/B] – This type of synthetic transactions run on Client Access servers and 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.[/LIST]
The collected results from both types of synthetic transactions are represented in the Monitoring pane of the Operations Console ([B]Figure 1[/B]).
You can also see synthetic transactions (represented by the perspective icon that looks like a pair of glasses) in the Exchange 2007 Topology View ([B]Figure 2[/B]):
[IMG]http://www.msexchange.org/img/upl/image0021265986826186.jpg[/IMG]
[B]Figure 1[/B]: Monitoring Mail Flow
[IMG]http://www.msexchange.org/img/upl/image0041265986826702.jpg[/IMG]
[B]Figure 2[/B][B]:[/B] Synthetic transactions in Topology View
[B]Configure Intra-Organization Mail Flow[/B]

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.

[LIST=1][*]To configure mail flow synthetic transactions click the [B]Authoring[/B] button in the Operations Console, click [B]Management Pack Templates[/B], and then click [B]Add Monitoring Wizard[/B] on the [B]Actions[/B] pane ([B]Figure 3[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0061265987083217.jpg[/IMG]
[B]Figure 3[/B][B]:[/B] Management Pack Templates

[LIST=1][*]On the [B]Select Monitoring Type[/B] page, select [B]Exchange 2007 Intra-Organization Mail Flow Monitoring[/B], and click [B]Next[/B] ([B]Figure 4[/B]).[*]On the [B]General Properties[/B] page, type the [B]Name[/B] for the object, optionally type a [B]Description[/B] and select a destination management pack from the list. Click [B]Next[/B] ([B]Figure 5[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0081265987083327.jpg[/IMG]
[B]Figure 4[/B][B]: [/B]Select Monitoring Type
[IMG]http://www.msexchange.org/img/upl/image0101265987157889.jpg[/IMG]
[B]Figure 5[/B][B]:[/B] General Properties

[LIST=1][*]On the [B]Source Server[/B] page, select the [B]Exchange organization[/B] and search the [B]Source server[/B] from the list of available servers, and then click [B]Next[/B] ([B]Figure 6[/B]).[*]On the [B]Test Settings[/B] page, specify the [B]Test frequency[/B] value or accept the default. Ensure that the test frequency you specify (between 5 and 60 minutes) is at least two times greater than the [B]Time-out[/B] value (between 1 and 30 minutes) and click [B]Next[/B] ([B]Figure 7[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0121265987158170.jpg[/IMG]
[B]Figure 6[/B]: Source Server
[IMG]http://www.msexchange.org/img/upl/image0141265987158483.jpg[/IMG]
[B]Figure 7[/B]: Test Settings

[LIST=1][*]On the [B]Target Servers[/B] page, click [B]Add[/B]. The source server and the target server must be in the same Exchange organization and site. On the [B]Select Target Servers[/B] page, search for available target servers, select the Mailbox server you want, and then click [B]Add[/B]. Click [B]OK[/B] and then click [B]Next[/B] ([B]Figure 8[/B]).[*]On the [B]Summary[/B] page, review the settings, and click [B]Create[/B] ([B]Figure 9[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0161265987158577.jpg[/IMG]
[B]Figure 8[/B][B]:[/B] Target Servers
[IMG]http://www.msexchange.org/img/upl/image0181265987243936.jpg[/IMG]
[B]Figure 9[/B][B]:[/B] Summary
[B]Configure Inter-Organization Mail Flow (Cont.)[/B]

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:

[LIST=1][*]To configure inter-organization and Internet mail flow transactions, go to [B]Object Discoveries[/B] under [B]Management Pack Objects[/B] in the [B]Authoring[/B] node in the Operations Console. Ensure that your console is not scoped to a subset of management pack objects. In the [B]Look for[/B] box, type [I]Cross[/I] and click [B]Find now[/B].[*]Right-click the [B]Exchange 2007 Mailflow Cross Organization Discovery[/B], click [B]Overrides[/B] | [B]Override the Object Discovery[/B] | [B]For a specific object of class: Exchange 2007 Mailbox Role [/B]([B]Figure 10[/B]).[*]Select the Exchange 2007 Mailbox server you want to use as the source server, and click [B]OK[/B] ([B]Figure 11[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0201265987244186.jpg[/IMG]
[B]Figure 10[/B][B]:[/B] Override the Object Discovery: Exchange 2007 Mail Flow Cross Organization Discovery
[IMG]http://www.msexchange.org/img/upl/image0221265987244311.jpg[/IMG]
[B]Figure 11:[/B] Select Object

[LIST=1][*]On the [B]Override Properties[/B] dialog box, change the [B]Target Addresses[/B] parameter. The destination mail service must be able to generate a delivery receipt. Choose a destination management pack to save the override, and click [B]OK[/B] ([B]Figure 12[/B]). This synthetic transaction runs every 30 minutes by default.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0241265987244373.jpg[/IMG]
[B]Figure 12[/B]: 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.
[B]Configure Client Access Server Synthetic Transactions[/B]

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:

[LIST][*] [I]Test-OwaConnectivity[/I][*] [I]Test-ActiveSyncConnectivity[/I][*] [I]Test-WebServicesConnectivity. [/I][*] [I]Test-PopConnectivity[/I][*] [I]Test-ImapConnectivity[/I][/LIST]
These cmdlets require a special test mailbox on each Exchange Server 2007 Mailbox server managed by Operations Manager.
To create the test mailbox, on each Exchange 2007 Mailbox server, open the [B]Exchange Management Shell[/B], locate the Scripts directory under the installation path for Exchange Server 2007 (usually \Program Files\Microsoft\Exchange Server\Scripts) and execute the script [I]New-TestCasConnectivityUser.ps1[/I] ([B]Figure 13[/B]).
[IMG]http://www.msexchange.org/img/upl/image0261265987333342.jpg[/IMG]
[B]Figure 13[/B][B]:[/B] 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:
[B]Exchange Management Shell (Figure 14):[/B]

[LIST][*][I]Set-OwaVirtualDirectory "<Server name>\owa (Default Web site)" -externalurl:"https://<Fully Qualified Domain Name>/owa"[/I][/LIST]
[B]Exchange Management Console (Figure 15):[/B]

[LIST][*]Open the Exchange Management Console, select [B]Server Configuration[/B], select [B]Client Access[/B], and then click the [B]Outlook Web Access[/B] tab.[*]In the work pane, select the virtual directory that you want to modify, and then click [B]Properties[/B].[*]In the virtual directory properties dialog box, select the tab that contains the properties that you want to modify. Click [B]OK[/B] to save your changes and close the properties window.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0281265987333561.jpg[/IMG]
[B]Figure 14[/B]: Setting the OWA external URL by using the Command Shell
[IMG]http://www.msexchange.org/img/upl/image0291265987333639.gif[/IMG]
[B]Figure 15[/B][B]:[/B] 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.

[LIST=1][*]Click the [B]Authoring[/B] button in the Operations Console, and then click [B]Add Monitoring Wizard[/B] from the [B]Actions[/B] pane. On the [B]Select Monitoring Type[/B] page, select [B]Exchange 2007 Client Access Server Monitoring[/B], and click [B]Next[/B] ([B]Figure 16[/B]).[*]On the [B]General Properties[/B] page, type the [B]Name[/B] for the object, optionally type a [B]Description[/B], select a destination management pack from the list and click [B]Next[/B] ([B]Figure 17[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0311265987333748.jpg[/IMG]
[B]Figure 16[/B]: Select Monitoring Type
[IMG]http://www.msexchange.org/img/upl/image0331265987426248.jpg[/IMG]
[B]Figure 17[/B][B]:[/B] General Properties

[LIST=1][*]On the [B]Source Server[/B] page, select the [B]Exchange organization[/B] where the tests will occur, search a [B]Source server[/B] from the list of available servers and click [B]Next[/B] ([B]Figure 18[/B]). The management pack runs the synthetic transaction on the source server you designate.[/LIST]
[B][IMG]http://www.msexchange.org/img/upl/image0351265987426342.jpg[/IMG]
Figure 18[/B][B]:[/B] Source Server

[LIST=1][*]On the [B]Test Settings[/B] page, specify the [B]Test frequency[/B] value (between 5 and 60 minutes). Ensure that the test frequency you specify is more than two times greater than the [B]Time-out[/B] 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 [B]Test types[/B], and then click [B]Next[/B] ([B]Figure 19[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0371265987426405.jpg[/IMG]
[B]Figure 19[/B][B]:[/B] Test Settings

[LIST=1][*]On the [B]Target Servers[/B] page, click [B]Add[/B] to search for Exchange 2007 mailbox servers that hosts the 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. Click [B]Next[/B] ([B]Figure 20[/B]).[*]On the [B]Summary[/B] page, review the settings, and click [B]Create[/B] ([B]Figure 21[/B]).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0391265987426436.jpg[/IMG]
[B]Figure 20[/B][B]:[/B] Target Servers
[IMG]http://www.msexchange.org/img/upl/image0411265987426748.jpg[/IMG]
[B]Figure 21[/B][B]:[/B] Summary
[B]Summary[/B]

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:

[LIST][*] 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[/LIST]

[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part5.html[/CODE][SIZE=3][B]
PART-5[/B][/SIZE]


[B]Configuring the Exchange 2007 MP to monitor SCR/CCR Log Shipping and Unified Messaging servers, adjusting resource intensive operations to minimize impact on Exchange servers.[/B]


[B]9. Configuring the Log Shipping Relay Queue Length Monitor for SCR and CCR Scenarios[/B]

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 logs and 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.

[LIST=1][*]To override the [B]Log Shipping ReplayQueueLength Monitor[/B], click the [B]Authoring[/B] button in the Operations Console, and then click [B]Monitors[/B], under [B]Management Pack Objects[/B]. Set the scope to [I]Exchange 2007 Log Shipping[/I]. Expand [B]Entity Health[/B], and then expand [B]Performance[/B] to expose the 2 pertinent monitors.[*]Right click [B]Log ShippingReplayQueueLenght Monitor[/B], select [B]Overrides[/B] | [B]Override the Monitor[/B] | [B]For all objects of class: Exchange 2007 Log Shipping[/B] (Figure 1). If you want to specify the override only for some servers (if you have both CCR and SCR), select instead [B]For a specific object of class: Exchange Log Shipping[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0021272028453023.jpg[/IMG]
[B]Figure 1[/B]: Override the Monitor: Log Shipping ReplayQueueLenght Monitor

[LIST=1][*]On the [B]Override Properties[/B] dialog box, configure the [B]Threshold[/B] parameter with a value appropriate 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.[*]Repeat previous steps for [B]Log Shipping CopyQueueLenght Monitor[/B] (Figure 3).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0041272028453070.jpg[/IMG]
[B]Figure 2[/B]: Log Shipping ReplayQueueLenght Monitor: Override Properties
[IMG]http://www.msexchange.org/img/upl/image0061272028453070.jpg[/IMG]
[B]Figure 3[/B][B]:[/B] Log Shipping CopyQueueLenght Monitor: Override Properties
[B]9.1 Enable Remote Unified Messaging Connectivity Monitoring[/B]

You need to modify the parameters of the script that executes [URL="http://technet.microsoft.com/en-us/library/aa997953%28EXCHG.80%29.aspx"]Test-UMConnectivity[/URL] 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:

[LIST][*][B]Extension number[/B]: the cmdlet must know which telephone number to call and it must be a number 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 you’re testing a server dedicated to Auto Attendant only.[*][B]Name of the IP gateway[/B]: the cmdlet must know the identity of an IP gateway that connects it to the telephone network.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0081272028453102.jpg[/IMG]
[B]Figure 4[/B][B]:[/B] Subscriber Access Number
After you have identified the appropriate [B]UM IP Gateway[/B] and [B]Phone[/B] parameters, you must use the following steps to enable the rule and to create an override for the script parameters:

[LIST=1][*]In the Operations Manager Operations Console, click the [B]Authoring[/B] tab, expand [B]Management Pack Objects[/B] and the select [B]Rules[/B]. In the [B]Look For[/B] box, enter [I]Exchange 2007 Test UM Connectivity[/I], and then click [B]Find Now[/B].[*]Right-click the rule [B]Exchange 2007 Test UM Connectivity Remote Voice Collection[/B], select [B]Overrides[/B] | [B]Override the Rule[/B] | [B]For all objects of class: Exchange 2007 Unified Messaging Role [/B](Figure 5).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0101272028570102.jpg[/IMG]
[B]Figure [/B][B]5:[/B] Override the Rule: Exchange 2007 Test UM Connectivity

[LIST=1][*]In the [B]Override Properties[/B] dialog box (Figure 6), select the Override column for the [B]Enabled[/B] Parameter name, and then check that the [B]Override Setting[/B] is set to [B]True[/B]. Select the [B]Override[/B] column for the [B]Phone[/B] parameter name, and then insert the appropriate number as identified previously. Finally override the [B]UM IP Gateway[/B] parameter with the name of your UM IP Gateway. Select a destination management pack and click [B]OK[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0121272028570117.jpg[/IMG]
[B]Figure [/B][B]6:[/B] Override Properties: Exchange 2007 Test UM Connectivity Remote Voice Collection

[LIST=1][*]You must also override the [B]Exchange 2007 Test UM Connectivity Remote Voice Monitor[/B] in the 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).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0141272028570117.jpg[/IMG]
[B]Figure [/B][B]7[/B][B]:[/B] Override the Monitor: Exchange 2007 Test UM Connectivity Remote Voice Monitor
[IMG]http://www.msexchange.org/img/upl/image0161272028570148.jpg[/IMG]
[B]Figure [/B][B]8[/B][B]:[/B] Exchange 2007 Test UM Connectivity Remote Voice Monitor: Override Properties
[B]9.2 Adjust the Best Time to Run Report Data Collection Scripts/Resource- Incentive Rules and Monitors[/B]

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.
[IMG]http://i49.tinypic.com/15xllba.jpg[/IMG]
[B]Table 1: [/B]Schedule of the report collection scripts

[LIST=1][*]To change the time that the Report Data Collection Scripts run, in the Operations Manager Operations Console, click the [B]Authoring[/B] tab, expand [B]Management Pack Objects[/B] and the select [B]Rules[/B]. In the [B]Look For[/B] box, enter the name of the rule you want to reschedule ([I]Exchange 2007 Database File Growth[/I] in this example), and then click [B]Find Now[/B].[*]Right-click the rule [B]Exchange 2007 Database File Growth[/B], select [B]Overrides[/B] | [B]Override the Rule[/B] | [B]For all objects of class: Exchange 2007 Database [/B](Figure 9).[*]In the [B]Override Properties[/B] dialog box, modify the [B]Sync Time[/B] parameter to the new time, choose a destination management pack and click [B]OK [/B](Figure 10).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0181272028703633.jpg[/IMG]
[B]Figure 9[/B][B]:[/B] Override the Rule: Exchange 2007 Database Growth
[IMG]http://www.msexchange.org/img/upl/image0201272028703648.jpg[/IMG]
[B]Figure [/B][B]10[/B][B]:[/B] 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.
[IMG]http://i45.tinypic.com/2crwvmv.jpg[/IMG]
[IMG]http://i46.tinypic.com/2460vo1.jpg[/IMG]

[B]Table 2[/B]
Just like the report data collection rules, to mitigate the impact on the Exchange servers, these objects use a 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:

[LIST=1][*]In the Operations Manager Operations Console, click the [B]Authoring[/B] tab, expand [B]Management Pack Objects[/B] and the select [B]Monitors[/B]. In the [B]Look For[/B] box, enter the name of the monitor you want to reschedule ([I]Exchange 2007 MDB Disk Free Space Monitor [/I]in this example), and then click [B]Find Now[/B].[*]Right-click the rule [B]Exchange 2007 MDB Disk Free Space Monitor[/B], select [B]Overrides[/B] | [B]Override the Monitor[/B] | [B]For all objects of class: Exchange 2007 Mailbox Database Disk [/B](Figure 11 Figure 9).[*]In the [B]Override Properties[/B] dialog box, modify the [B]Sync Time[/B] parameter to the new time, choose a destination management pack and click [B]OK [/B](Figure 12).[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0221272028703648.jpg[/IMG]
[B]Figure [/B][B]11:[/B] Override the Monitor: Exchange 2007 MDB Disk Free Space Monitor
[IMG]http://www.msexchange.org/img/upl/image0241272028703648.jpg[/IMG]
[B]Figure [/B][B]12:[/B] Exchange 2007 MDB Disk Free Space Monitor: Override Properties
[B]Summary[/B]

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 the previous converted Exchange Management Pack. Common Troubleshooting and Reports will be the last topics covered in the article
[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-native-exchange-2007-mpopsmgr-2007-r2-part6.html[/CODE]
[B][SIZE=3]
PART-6[/SIZE][/B]


[B]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.[/B]


[B]Co-Existence with the Previous Version of Exchange Server 2007 MP [/B]

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 Microsoft Exchange Server 2007 Management Pack.
There are some migration options though for you to consider. The following table (from the [URL="http://technet.microsoft.com/en-us/library/dd772509.aspx"]official documentation[/URL]) illustrates the possible options, as well as the pros and cons of each scenario:

[B]Option[/B]
[B]Pros[/B]
[B]Cons[/B]
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 then import the native Exchange Server 2007 Management Pack.
In this scenario, you lose all the historical data of the converted management pack, including reporting data.
Keep the previously released, converted management pack and use a second management group and multi-homing for the new, native management pack.
You keep the history from the converted management pack, including reporting data.
A more complex approach with the overhead of setting up a second management group for the native 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 management groups 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 pack synthetic transactions use fewer resources on the Exchange 2007 servers.
Keep the previously released, converted management pack and plan a gradual introduction of the 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 reporting data. There is less complexity because you only use one management group.
An increasingly complex end-to-end migration solution because, although you avoid using a second 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 the discoveries 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.
[B]Table 1: [/B]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 old MP to avoid duplication of monitoring.
The provided management pack, [I]Microsoft.Exchange.2007.Disable.xml[/I], 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: [URL="http://blogs.technet.com/momteam/archive/2009/07/06/new-exchange-2007-management-pack-and-keeping-old-management-pack-data.aspx"]New Exchange 2007 Management Pack and Keeping Old Management Pack Data[/URL].
[B]Common Troubleshooting Issues[/B]

There are some common problems you may get right after you import and start using the native Exchange 2007 MP. I will mention a few and give you the solution.
[B]1. No Exchange 2007 Servers Discovered[/B]
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 [B]Object Discoveries[/B] located under [B]Management Pack Objects[/B] in the [B]Authoring[/B][B] section of[/B]the 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.
[IMG]http://www.msexchange.org/img/upl/image0021273924237965.jpg[/IMG]
[B]Figure 1[/B][B]:[/B] Override Properties: Exchange 2007 Discovery Helper Discovery
To further troubleshoot the discovery process, go the [B]Discovered Inventory[/B] under [B]Monitoring[/B] section. Click [B]Change Target Type[/B] on the [B]Actions[/B] pane, select [B]Agent[/B] and click OK. Select the server that isn't correctly being discovered, from the list of available agent-managed servers, and then run [B]Show Running Rules and Monitors for this Health Service[/B] from the list of available Tasks.
The task will produce the output depicted on Figure 2. Copy the [B]Task Output[/B] section to Notepad and search for a workflow called [I]Microsoft.Exchange2007.ServerRole.CcrNode.Standalone.Discovery[/I]. This will confirm that the agent is running the discovery workflow.
[IMG]http://www.msexchange.org/img/upl/image0041273924237996.jpg[/IMG]
[B]Figure 2[/B][B]:[/B] Show Running Rules and Monitors for this Health Service
[B]2. No Standalone Exchange 2007 Mailbox servers discovered[/B]
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 on each mailbox server.
[IMG]http://www.msexchange.org/img/upl/image0061273924237996.jpg[/IMG]
[B]Figure [/B][B]3:[/B] Exchange 2007 Standalone CCR Node Discovery: Override Properties
[B]3. "No Exchange 2007 Mailbox Servers were found" message when configuring Intra-Organization Mail Flow Synthetic Transaction[/B]
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).
[IMG]http://www.msexchange.org/img/upl/image0081273924238012.jpg[/IMG]
[B]Figure [/B][B]4:[/B] No Exchange 2007 Mailbox Servers were found
[B]4. Erroneous IIS alerts on physical nodes of clusters[/B]
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 that you monitor only the clustered Mailbox virtual server.
See [B]Configure Internet Information Services (IIS) Monitoring [/B]section[B].[/B]
[B]5. Exchange 2007 MP incorrect discoveries[/B]
When you check the [B]Exchange 2007 Computer Group[/B], you realize it includes servers that aren't Exchange Servers. The group contains servers where the Exchange 2007 Management Tools are installed.
The Exchange 2007 Computer Group membership is based on instances of the Exchange 2007 Discovery Helper. Thus it will include computers (servers only, not client computers) that are not Exchange 2007 servers, including Windows Server installation that have Exchange tools installed.
To resolve this issue, disable the [B]Discovery of the Exchange 2007 Discovery Helper[/B] for the non-Exchange Servers, by means of an override. Next, to clean up the instances of Exchange 2007 Discovery Helper, you will need to run the [I]Remove-DisabledMonitoringObject[/I] Poweshell cmdlet
[B]6. Inter-organization mail flow perspective is not created[/B]
After the configuration of an inter-organization mail flow synthetic transaction, a discovery process runs and generates a new instance of an inter-organization mail flow perspective. (This discovery runs every 24 hours by default.).
If you navigate to the [B]Mail Flow State[/B] view in the Monitoring section, which shows all instances of mail flow perspectives, you can't find the recently created one.
It may take some time for the perspective to be created, so you have to wait a little bit longer.
[B]7. Exchange 2007 Test Active Sync Connectivity Monitor: Could not establish trust relationship for the SSL/TLS secure channel[/B]
[B]Exchange 2007 Test Web Services Connectivity Monitor: Could not establish trust relationship for the SSL/TLS secure channel[/B]
[B]Exchange 2007 Test OWA Internal Connectivity Monitor: The test was unable to log on to Outlook Web Access because the SSL certificate did not validate.[/B]
All of these 3 errors are related. I was getting 3 critical alerts related with SSL for the CAS synthetic transactions (Figure 5). After some troubleshooting, the only thing I noticed is that the certificate in use had a simple name (no FQDN) in its subject (the correct names were all in the Subject Alternate Names), as depicted in Figure 6.
After issuing a new certificate, with an FQDN name as the subject (Figure 7), the problem was solved. I was not able to confirm if this is a bug or just anything related with my own environment.
[IMG]http://www.msexchange.org/img/upl/image0101273924524730.jpg[/IMG]
[B]Figure [/B][B]5:[/B] CAS synthetic transaction errors (SSL related)
[IMG]http://www.msexchange.org/img/upl/image0121273924524730.jpg[/IMG]
[B]Figure [/B][B]6:[/B] Certificate with a simple subject name
[IMG]http://www.msexchange.org/img/upl/image0141273924561449.jpg[/IMG]
[B]Figure [/B][B]7:[/B] Certificate with FQDN name in the Subject
[B]Reports[/B]

Reporting was also one of the areas where the native Exchange 2007 MP introduced major improvements. There are more reports available and it is easier to customize a report using the new search and filtering functionality, which automatically returns objects of the correct type for the report.
Reporting is an optional component of Operations Manager 2007, but its value is unquestionable. Here's a list of all available Exchange 2007 reports:

[LIST][*] Average Mailbox Size[*] Client Access Server Transaction Configuration[*] Client RPC Latency > 2 seconds[*] Database and Log Latency[*] Database File Growth[*] Mail Flow Transaction Configuration[*] Mailbox Messages Delivered Report[*] SMTP Messages Sent[*] Number of Mailboxes.[*] Server Disk Free Space[*] SMTP Messages Received Report[*] SMTP Messages Sent[*] Store RPC Performance[*] Top N Mailboxes by Message Count[*] Top N Mailboxes by Size[*] Top N Public Folders by Message Count[*] Top N Public Folders by Size[*] ActiveSync Site Service Availability SLA[*] Hub Transport Service Availability SLA[*] IMAP4 Site Service Availability SLA[*] Mail Flow Cross Organization Availability SLA[*] Mail Flow Local Availability SLA[*] Mail Flow Local Latency SLA[*] Mail Flow Remote Availability SLA[*] Mail Flow Remote Latency SLA[/LIST]

[LIST=1][*]To run a report, click the [B]Reporting[/B] button in the Operations Console, expand [B]Reporting[/B] and then click Microsoft Exchange Server 2007 Reports (Figure 8).[*]Double-click the report you want to run. In the [B]Objects[/B] area, click [B]Add object[/B].[*]Click [B]Search[/B] to see a list of the available objects for the report. Select the object you want to add and then click [B]Add[/B].[*]Use the settings on the page to further customize the report, and then click [B]Run[/B]. Figure 9 depicts the [B]Exchange 2007 Top N Mailboxes by Size Report[/B].[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0161273924561652.jpg[/IMG]
[B]Figure [/B][B]8:[/B] Exchange Server 2007 Reports
[IMG]http://www.msexchange.org/img/upl/image0181273924561715.jpg[/IMG]
[B]Figure [/B][B]9:[/B] Exchange 2007 Top N Mailboxes by Size Report
[B]Conclusion[/B]

The new native Exchange 2007 MP is a must! There are so many improvements that you will start taking advantage of its value from the moment you import it.
And since Exchange Server 2010 was recently released, it is now time to start playing around with the corresponding Management Pack. I will let you know how it went in a future article.
[B]Related Links:[/B]

[LIST][*][URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=19bd0eb5-7ca0-41be-8c0f-2d95fe7ec636&displaylang=en"]System Center Operations Manager 2007 R2 Documentation[/URL][*][URL="http://www.microsoft.com/downloads/details.aspx?familyid=E9F3CD3F-9BC0-45CD-B10F-120E937EE4C4&displaylang=en"]Microsoft Exchange Server 2007 Management Pack for System Center Operations Manager 2007 R2[/URL][*][URL="http://www.microsoft.com/technet/prodtechnol/scp/mtps/opsmgr07.aspx"]System Center Operations Manager 2007 Catalog[/URL][*][URL="http://blogs.technet.com/momteam/"]Operations Manager Product Team Blog[/URL][*][URL="http://technet.microsoft.com/en-us/library/dd772563.aspx"]Exchange Server 2007 Management Pack for Operations Manager 2007 R2 Guide[/URL][/LIST]

[/LEFT]

Excillent