Here’s another new System Center Operations Manager 2007 Knowledge Base article we published this morning. This one tells you how to fix and prevent an issue where incorrect Exchange server status can be rolled up to OpsMgr 2007 when multiple domains share the same site name:
Exchange servers using the same organization and AD site name but in separate domains will have their overall status merged when rolled up in Health Explorer.
For example, say you have Exchange servers in Domain_A and in Domain_B and they both belong to an organization named MyOrganization and a site name MySite. If an Exchange server in Domain_A is in a critical state, MyOrganization in Domain_A and in Domain_B will report a critical status even though Exchange servers in Domain_B are healthy.
This can occur if two separate domains contain Exchange servers with identical Organization and Active Directory Site names.
To resolve and prevent this issue, use unique AD site names in each domain.
The information above was published today in the following Microsoft Knowledge Base article written by Simon Xin:
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv