The DSProxy service does not direct an Outlook client to the global catalog servers that you want to use in Exchange Server 2003

When a Microsoft Outlook client computer connects to Microsoft Exchange Server 2003, the DSProxy service does not direct the client to the global catalog server that you want to use. Instead, the DSProxy service directs the client to a domain controller that is in a different domain. You do not want to use this domain controller as a global catalog server.

This problem may occur if you installed Microsoft Exchange Server 2003 Service Pack 2 (SP2). The algorithm that is used by Exchange Server 2003 to refer Outlook clients to global catalog servers was changed in Exchange Server 2003 SP2.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Exchange Server 2003 SP2 installed to apply this hotfix.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other software updates.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Installation information

After you apply this hotfix, you must configure the RFR Prefer In-Site GCs registry entry. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
3. Right-click Parameters, point to New, and then click DWORD Value.
4. Type RFR Prefer In-Site GCs, and then press ENTER.
5. Right-click RFR Prefer In-Site GCs, and then click Modify.
6. In the Value Data box, type 1, and then click OK.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Typically, Exchange Server 2003 servers refer Microsoft Office Outlook 2003, Microsoft Outlook 2002, and Microsoft Outlook 2000 client computers to global catalog servers for directory access. If you are running a version of Exchange Server 2003 that is earlier than Exchange Server 2003 SP2, Outlook client computers are referred to global catalog servers that are located in the same site as the Exchange server on which the users' mailboxes are located.

When a user account is in a different domain than the Exchange server on which the user account's mailbox is located, the Outlook client is referred to the global catalog server in the Exchange server domain. In this scenario, the Outlook client receives only read access to the global catalog server. Therefore, the Outlook user cannot configure a delegate or any public distribution lists that the Outlook user owns.

After you install Exchange Server 2003 SP2, the Exchange server refers Outlook clients to global catalog servers in the user's local domain. Therefore, the issue in which Outlook users receive only read access to the global catalog server is resolved.

In an environment in which many user mailboxes are located on Exchange servers in other domains, you may experience a significant change in the load on the global catalog servers in the users' local domain. This change in load occurs because referrals that were originally targeted to global catalog servers in the Exchange servers' domains are now all targeted to global catalog servers in the users' local domain. Therefore, the global catalog servers in the users' local domain may not be able to handle the additional load that is caused by the Outlook directory search requests.

For more information about Directory Service Proxy, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: