Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
How to configure Outlook to a specific global catalog server or to the closest global catalog server
Article ID: 319206 - View products that this article applies to.
This article was previously published under Q319206
For a Microsoft Outlook 2000 version of this article, see 272290
In some situations, you may notice excessive network traffic when Microsoft Outlook attempts to contact the global catalog server.
This article describes how to configure Outlook to a specific global catalog server or to the closest global catalog server.
Note If the global catalog server and the Exchange Server computer are in the same site as the Outlook client, you do not need to make this registry setting. The normal referral mechanism provides the best performance.
This behavior occurs when the Exchange Server computer (where the Outlook client is homed) and the global catalog server are both located in a site that is remote from the Outlook client location.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
How to set the closest global catalog serverTo have us set the closest global catalog server for you, go to the "Fix it for me" section. To set the closest global catalog server yourself, go to the "Let me fix it myself" section.
Fix it for meTo set the closest global catalog server automatically, click the Fix it button or link. Click Runin the File Downloaddialog box, and then follow the steps in the Fix it wizard.
Fix this problem
Microsoft Fix it 50353
Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Let me fix it myselfIf you are running a version of Exchange Server that is earlier than Exchange Server 2010, use the following steps to force Outlook to identify and use the closest global catalog server yourself.
How to set a specific global catalog serverIn other topologies, you may want to force Outlook to communicate with a specific global catalog server, not necessarily the global catalog server that is closest to the Outlook client.
Note although you can manually change the registry parameter in the MAPI profile, it is overwritten the next time that you start Outlook.
To force Outlook to use a pre-defined global catalog server, use the following steps to set the following special registry parameter to point to the Fully Qualified Domain Name (FQDN). Doing this over-rides any setting in the MAPI profile.
Exchange Server 2010Exchange Server 2010 introduces significant changes in the way Outlook interacts with global catalog servers in the organization.
In earlier editions, Exchange server would direct Outlook to contact a global catalog. In Exchange Server 2010, the Microsoft Exchange Address Book Service on the Client Access Server (CAS) hosts the NSPI endpoint. The Exchange Server 2010 CAS provides address book and related services to Outlook clients instead of referring Outlook to Global Catalog server.
The Closest GC and DS Server registry values that are specified in this article will not work correctly if the mailbox is hosted on Exchange Server 2010. In this case, the Closest GC key should never be used, and the value of the DS Server entry should be set to the Fully Qualified Domain Name of the Exchange Server 2010 CAS.
When you use the Closest GC value with an Exchange 2010 mailbox and reply to an email message from someone external to your Exchange organization, you may receive the following error:
The operation failed. The messaging interfaces have returned an unknown error. If the problem persists, restart Outlook. Cannot resolve recipient.
For more information, see the following Microsoft TechNet article:
Understanding RPC Client Access
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/317209/ )How to identify your global catalog server using Outlook 2000 and Outlook 2002
The information in this article was derived from the "Understanding and Troubleshooting Directory Access" white paper. To view this white paper, visit the following Microsoft Web site: