Changes in This Update
Applies To: Exchange Server, Operations Manager 2007 R2
The April 2010 release is an update to the guide only – there are no changes to the management pack. The April 2010 update of the Exchange Server Management Pack Guide includes the following changes:
Added two monitors that can be disabled to the Configuring IIS Monitoring topic.
In the Synthetic Transactions and the Windows PowerShell Event Log topic, corrected the default size of Windows Server 2003 server logs.
In the Configuring Inter-Organization and Internet Mail Flow Synthetic Transactions topic, corrected the name of Exchange 2007 Mail Flow Cross Organization Discovery.
Added “Test-OwaConnectivity May Fail When Domain Controllers Are Running Windows 2000 Server” to Known Issues and Troubleshooting topic.
The 6.0.6702.0 version of the Exchange Server Management Pack for Operations Manager 2007 R2 includes the following changes:
Fixed an issue where Exchange 2007 Synthetic transactions would stop running on the source server if the target server was a clustered mailbox server. This update involves not discovering a containment relationship between the synthetic transaction and the target clustered mailbox server in the RMS Target Relationship Discovery. For more information see Synthetic Transactions in the Management Pack. This means that if the entire clustered mailbox server is in maintenance mode, the transaction will still run on the source server, generating alerts.
Retargeted two rules that generate an alert if the agent is unable to discover the Exchange server because of missing permissions, usually because the agent is running with low permissions and the Exchange 2007 Run As profiles have not been assigned. These rules are now targeted to Exchange 2007 Discovery Helper. Because of this, the alerts will not show up under the Exchange views, but in the topmost Active Alerts view under the Monitoring node. The two rules that are retargeted are “Check script running with LDAP permission” and “Check script running as local system”. The rules may alert on Console Only installs as well, if the Run As profile has not been assigned.
Fixed an issue where mailflow synthetic transactions created by using the wizards would not work if the target was a clustered mailbox server.
Fixed an issue in which Exchange Best Practice Analyzer would show the name of the first server that generated that particular event for a given language. All events now show the computer name where the event was generated.