Export (0) Print
Expand All
Expand Minimize

The msExchRoutingGroupMembersBL attribute is indexed

[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 http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-17

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine whether the Routing Group Back-Link attribute has been configured for indexing in Active Directory. Specifically, the Exchange Server Analyzer examines the following Active Directory object to determine the current indexing value for the msExchRoutingGroupMembersBL attribute:

CN=Configuration,DC=domain,DC=com, CN=Services, CN=Microsoft Exchange, CN=OrganizationName, CN=Administrative Groups, CN=AdministrativeGroupName, CN=Routing Groups, CN=RoutingGroupName

By default, this attribute is not indexed. If the Exchange Server Analyzer finds that this attribute is configured for indexing, a non-default configuration message is displayed.

In a distributed or branch office deployment of Exchange that contains a large number of routing groups, leaving this attribute as non-indexed can cause performance degradation. For example, if there are hundreds of routing groups in your Exchange organization, you may notice increased activity on one or more global catalog servers every 15 minutes. This increased activity occurs because the DSAccess component in Exchange re-reads the routing group configuration. In severe cases, the global catalog may become consumed with this activity.

To minimize this burden on the global catalog, the Routing Group Back-Link attribute can be indexed, thereby reducing the time it takes for DSAccess to read the routing group information, as well as reducing the burden placed on the global catalog by this activity.

  • There is no action required, because the message generated by the Exchange Server Analyzer is for informational purposes only.

For more information about tuning Exchange for best performance, see the Exchange Server 2003 Performance and Scalability Guide (http://go.microsoft.com/fwlink/?linkid=47576).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft