Routing group membership error

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at]  

Topic Last Modified: 2006-08-21

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service for each value of the msExchRoutingGroupMembersBL attribute on the Routing Group objects to determine whether the back-linked server belongs to the dedicated Microsoft Exchange Server 2007 administrative group, Exchange Administrative Group (FYDIBOHF23SPDLT).

The Exchange Server Analyzer also queries the value of the CN attribute for the Routing Group object to determine whether the value is equal to the Exchange 2007 routing group default, Exchange Routing Group (DWBGZMFD01QNBJR).

The Exchange Server Analyzer displays an error if the following conditions are true:

  • The back-linked server belongs to the dedicated Exchange 2007 administrative group, Exchange Administrative Group (FYDIBOHF23SPDLT).

  • The routing group is not the Exchange 2007 routing group default, Exchange Routing Group (DWBGZMFD01QNBJR).

This error indicates that the server may have been manually moved from the Exchange 2007 default routing group. This may cause routing issues.

Microsoft Exchange Server 2003 and Microsoft Exchange 2000 Server use routing groups to define an Exchange-specific routing topology. Exchange 2007 uses Active Directory sites to define its routing topology. Exchange 2003 and Exchange 2000 use a routing topology that is based on routing groups and connectors. An Exchange-specific routing configuration is no longer required in a pure Exchange 2007 organization. A pure Exchange 2007 organization uses the Active Directory site topology to determine its routing topology.

To support coexistence between these two routing topologies, all Exchange 2007 servers are automatically added to a single routing group when Exchange 2007 is installed. The Exchange 2007 routing group is recognized in the Exchange System Manager in Exchange 2003 or Exchange 2000 as Exchange Routing Group (DWBGZMFD01QNBJR) within Exchange Administrative Group (FYDIBOHF23SPDLT).

To resolve this issue, move Exchange 2007 servers to the Exchange 2007 dedicated routing group, or remove and reinstall the server.