Servers container is missing
[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: 2006-08-21
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service for the value of the distingushedName attribute for each Routing Group object discovered in the current administrative group.
The Exchange Server Analyzer then queries Active Directory to determine whether a Servers container is present in the current administrative group.
The Exchange Server Analyzer displays an error if the following conditions are true:
The current administrative group contains one or more routing groups.
A Servers container does not exist.
This error indicates that no servers are installed in the administrative group and that routing information may not be dynamically propagated across servers throughout the Exchange organization.
To address this error, make sure that the Exchange organization is in native mode and follow these steps.
Create a new administration group.
Create a new Routing Groups container in the new administration group.
Drag the existing routing groups from the old Routing Groups container into the new one.
Restart all Exchange services.
For more information about this error, see Microsoft Knowledge Base article 318491 "XADM: Routing Information Is Not Propagated Across an Exchange 2000 Organization" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=318491).