Microsoft KB Archive/820554

= An incorrect e-mail address is stamped on a recipient that you create in a mixed mode Exchange organization =

Article ID: 820554

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In a mixed mode Exchange Server organization that contains more than one site, an incorrect e-mail alias may be stamped on a recipient in the Active Directory directory service.



CAUSE
This issue may occur if all the following conditions are true:
 * The Microsoft Exchange Site Replication Service (SRS) is running on two Exchange 2000 computers in two different sites.

-and-
 * An Active Directory Connector (ADC) Connection Agreement is configured to replicate recipient information between the two SRS computers in the different sites.

-and-
 * You create a user account together with a mailbox on a domain controller in the first site, but you have that user's mailbox stored on a computer in the second site.

Under these conditions, the ADC may stamp the user account with an e-mail address from the first site instead of from the second site.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.Before you install this hotfix, change or add the  registry value Disable Proxies Generation under the following registry key:

Set the Disable Proxies Generation value to 1 so the ADC does not generate proxies anymore. If you set the value to 0 and then restart the ADC, the ADC generates proxies again. You must install this hotfix on every server that runs the ADC.

File Information
The English version of this has the file attributes (or later) 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.

Date       Time    Version     Size     File name --- 24-Jul-2003 23:38  6.0.6490.0  757,760  Adc.exe



WORKAROUND
To work around this issue, use one of the following methods:

Method 1: Change the Default Recipient Policy
Change the default recipient policy on the Exchange computer in the second site (the site where you created the user's mailbox) to generate e-mail addresses for that second site.

Note If you later change your organization from mixed mode to native mode (where no Exchange Server computers exist in the organization), you must change the default recipient policy back to the original e-mail alias.

For additional information about how to work with recipient policies, click the following article number to view the article in the Microsoft Knowledge Base:

285136 XADM: How to Customize the SMTP E-mail Address Generators Through Recipient Policies

Method 2: Reconfigure the ADC Recipient Connection Agreement

 * 1) Remove the ADC recipient Connection Agreement between the two Exchange 2000 SRS computers in the two sites (where one Exchange 2000 SRS computer is in each site).
 * 2) Create a new recipient Connection Agreement between the Exchange 2000 SRS computer in the first site and an Exchange Server computer in the second site.

Method 3: Schedule the Conflicting Services
Make sure that the Recipient Update Service runs before the ADC. You can do this by scheduling the services to run at different times.



MORE INFORMATION
The issue that is described in this article occurs because when the ADC recipient Connection Agreement is running, it may stamp the newly created user account with the incorrect e-mail address before the Recipient Update Service can stamp the user account with the correct e-mail address. The ADC design is simpler than the Recipient Update Service and cannot determine the correct e-mail address for the user account. The ADC is designed to select the default recipient policy from the Exchange 2000 computer where the user's mailbox is stored. However, this recipient policy specifies the default e-mail alias. The default e-mail alias may be that of the first site. Therefore, the user account may be stamped with the e-mail alias from the first site, when their mailbox is stored on a computer in the second site.

Additional query words: CA RUS XCON

Keywords: kbhotfixserver kbqfe kbprb KB820554

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.