Configure a domain controller as a global catalog server
Updated: January 21, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To configure a domain controller as a global catalog server
Open Active Directory Sites and Services.
In the console tree, right-click NTDS Settings.
Active Directory Sites and Services/Sites/YourApplicableSite/Servers/YourApplicableServer/NTDS Settings
- Active Directory Sites and Services/Sites/YourApplicableSite/Servers/YourApplicableServer/NTDS Settings
On the General page, select the global catalog check box.
To open Active Directory Sites and Services, click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
Each Windows Server 2003 family site or Windows 2000 site containing MSMQ 1.0 clients running on Windows NT 4.0, Windows 98, or Windows 95 computers must contain at least one Windows Server 2003 domain controller that is running the Message Queuing directory service (Downlevel Client Support) and is configured as a global catalog server or at least one Windows 2000 domain controller that is running a Message Queuing server and is configured as a global catalog server from the domain of each such client. This is required to enable such clients to send queries programmatically to Message Queuing servers.
When a Windows NT 4.0 primary enterprise controller (PEC) is migrated, it is automatically promoted to a domain controller configured as a global catalog server.
The first domain controller in a Windows Server 2003 family forest is automatically configured as a global catalog server.
Information about functional differences
Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.