There are 4 performance collection rules that need to be enabled to collect data for the corresponding reports. These rules all collect data via Exchange message tracking logs.

The performance collection rules for message tracking have the potential to collect significant amounts of data. These rules target Exchange Database Storage, run daily, and collect data from 200 objects.

To enable the Exchange Topology view, do the following:

1. Enable the agent proxy on all managed servers running Exchange Server 2003. For more information about the agent proxy, see the "How to Configure an Operations Manager 2007 Agent-Managed Computer as a Proxy for Agentless Managed Computers" topic in the Operations Manager 2007 Help. Note that only one server per Organization per Operations Manager Management Group needs to have this enabled.
   
2. Use overrides to enable Exchange Topology Discovery on a managed server running Exchange Server 2003. Exchange Topology Discovery will update after the next discovery interval, up to one hour, or you can stop and start the Operations Manager 2007 HealthService on the server running Exchange.
   To enable Exchange Topology Discovery

   1. In the Authoring pane of the Operations Manager 2007 Operations Console, click Object Discoveries.

   2. In the Object Discoveries pane, right-click Exchange 2003 Topology Discovery, point to Overrides, point to Override the Object Discovery, and then click For a specific object of type: Exchange 2003 Role.

   3. In the Select Object dialog box, type the search criteria, and then click OK.

   4. Select the desired server running Exchange Server 2003 from Matching objects, and then click OK.

   5. In the Override Properties dialog box, select Override for the Enabled parameter, and then select True from the Override Setting drop-down list.

   6. Select the Management Pack to save the override in, and then click OK.

Availability monitoring for Outlook Web Access (OWA), Outlook Mobile Access (OMA), and Exchange ActiveSync (EAS) functions only on front-end servers running Exchange Server 2003. When you select the Enable Front-End server monitoring check box in the Configuration Wizard, availability monitoring is enabled.

To monitor availability, a synthetic logon process is used that simulates a user logging on to a mailbox using a mobility client. To enable a synthetic logon, there must be a Test mailbox with a user account. For the Outlook Web Access logon, the Configuration Wizard automatically picks one of the existing back-end test mailboxes that is used by MAPI logon. This mailbox name is automatically stored in the \\HKLM\Software\Exchange MOM\FEMonitoring\<front-end servername>\BEAccount registry value on the front-end server. The Mailbox Access Account mailbox is used for Outlook Mobile Access and Exchange ActiveSync logon.

By default, the Exchange Management Pack automatically determines the URL used to monitor the front-end services by using a combination of the localhost/network card IP and the virtual server and virtual directory information in the Internet Information Services (IIS) metabase. This URL is the local monitoring URL because the logon request is submitted to the local front-end server, where the logon request is generated.

You also can supply a custom URL to monitor the public URL that is used by your Web and mobile devices. This must be a URL that an end-user can use to log on. This logon request that is submitted to the custom URL can be responded to by any one of the organization's front-end servers that normally respond to requests to the specified URL. The public URL monitoring cannot be directed to monitor a specific server.

To use a custom URL, you have to configure registry entries on each server where you want the monitoring enabled.

To configure a custom URL for Outlook Web Access

Open Registry Editor, locate the \\HKLM\Software\Exchange MOM\FEMonitoring\<front-end serverrname>\ key, and create a registry value (type string) named CustomUrls. Enter the custom URL value as a comma-delimited list in this value. For single URLs, follow this example:

• https://www.example.com/exchange
  

For multiple URLs, use the following format:

• https://www.example.com/exchange, https://www.example.com/mail
  

Note
Do not append the mailbox name in the URL, such as https://www.example.com/exchange/johnsmith, or the synthetic logon will fail.

You will also need to set the “CustomURL” override on the Outlook Web Access Logon Monitor to True, which causes the monitor to use the values specified in the CustomURLs registry entry to monitor OWA rather than the default values.

To configure a custom URL for Outlook Mobile Access

To configure a custom URL for Exchange ActiveSync

The Microsoft Windows Server Library Management Pack discovers the virtual node of a cluster, and the virtual node is added to the Management Group. The Exchange Management Pack then discovers and monitors the virtual node of the clustered servers running Exchange Server 2003. This means the virtual node of the cluster is associated with the Exchange 2003 Role, not the physical nodes.

Installing the Operations Manager 2007 Agent

Monitoring the Virtual Cluster

The performance collection rules for message tracking have the potential to collect significant amounts of data. These rules target Exchange Database Storage, run daily, and collect data from 200 objects.

If a server running Exchange connects to its primary or secondary management servers over expensive or low-bandwidth connections, you might want to use overrides to configure these rules to collect data from fewer objects, reduce the value for MaxEntries, run the rules less frequently, increase the value for IntervalSeconds, or disable the rules.