Why does Exchange 2003 need Global Catalog Servers?
The specific reason why Microsoft Exchange clients place such a heavy load on the Global Catalog Servers is that they need to make LDAP queries to resolve email addresses. For example, a user opens Microsoft’s Outlook and types the name of a recipient. To find the corresponding SMTP address, the GAL issues an LDAP query to the Global Catalog Server. Before we get deep into Global Catalogs, here are four concepts to help us get started. 1) Only the first Domain Controller in any Domain is a Global Catalog Server by default. Good news, all subsequent Domain Controllers have the Global Catalog capability. 2) Global Catalog Server is a property, a tick in a box, on a Domain Controller. You cannot configure a member server or even an Exchange Member server as a Global Catalog Server. 3) Ordinary non-outlook users need a Global Catalog Server to find network resources such as Universal Group Membership. Therefore, all the configuration you make with Catalog Servers for the sake of Exchange’s
Related Questions
- We do not actually use Microsoft Exchange, but still have PST files generated from POP3 and SMTP servers and email. Will .PST Attender work with these types of PST files?
- Should servers that are running Active Directory domain controllers and the global catalog be upgraded to 64-bit?
- How to import active directory users(from other global catalog ) in exchange 2007?
