The local computer is a domain controller of a child domain
[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-12-29
Microsoft® Exchange Server 2007 setup cannot continue because the local computer is a domain controller for a child domain.
Exchange 2007 setup will not install on to a domain controller for a child domain unless the domain controller is a global catalog server.
To resolve this issue, promote the domain controller to a global catalog server or install Exchange 2007 to a non-domain controller, a member server, in the child domain, and then rerun the Microsoft Exchange setup.
To correct this warning by making the Exchange server a global catalog server
On the domain controller, click Start, point to Programs, click Administrative Tools, and then click Active Directory Sites and Services.
In the console tree, double-click Sites, double-click the name of the site, and then double-click Servers.
Double-click the target domain controller.
In the results pane, right-click NTDS Settings, and then click Properties.
On the General tab, click to select the Global catalog check box.
Restart the domain controller.