After you migrate from Lotus Notes to Exchange Server 2003, junk characters are displayed for the e-mail address in Outlook

Consider the following scenario. You migrate from Lotus Notes to Microsoft Exchange Server 2003 by using the Exchange Server 2003 Notes Tools suite. After migration is complete, you start Outlook to send an e-mail message to an internal user.

In this scenario, when you type the first letter of the name in the To box, junk characters are displayed in the To box instead of the e-mail address. However, even when junk characters are displayed, the e-mail message is delivered to the intended user correctly.

This issue is caused because the wrong value is used for the LegacyExchangeDN attribute for the user.

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

To resolve this issue, use one of the following methods, as appropriate for your situation.

Method 1

Run the Admodify.net tool to change the value of the LegacyExchangeDN attribute for all users. To do this, follow these steps:

1. To download the tool, visit the following Microsoft Web site, and save the tool to a suitable location on the Exchange computer:
   http://www.codeplex.com/admodify
2. Uncompress the .zip file that you saved in step 1 to a suitable folder. For example, uncompress the .zip file to a folder that is named Admodify.
3. Move to the folder that contains the uncompressed files.
4. Double-click the ADModify.exe file, and then click Modify Attributes.
5. In the Domain List box, click the domain entry that corresponds to the domain of the Exchange computer that is affected. For example, the entry that you click resembles the following entry:
   DC=Exchange2003,DC=Org_Name,DC=Root_Domain
6. In the Domain Controller List box, type or click the FQDN of the domain controller that contains the users who are affected. For example, you must type a string that resembles the following string:
   Domain_Server_Name.Exchange2003.Org_Name.Root_Domain
7. Click to clear the following check boxes:
   • Groups
   • Contacts
   • Public folders
   • Show Containers only
8. Click the green arrow button that is next to the Domain Controller List box.
9. Expand the domain object that is displayed.
10. Click the container that contains the users who are affected. For example, click Users.
11. Click Add to List, click Select All, and then click Next.
12. Click the Custom tab, and then click to select the Make a customized attribute modification check box.
13. In the Attribute Name box, type LegacyExchangeDN.
14. In the Attribute Value box, type the string that corresponds to the value that is suitable to your context. Notice that you must replace the last part of this string with a variable to suit all users. For example, the value that you type may resemble the following string:
    /o=First Organization/ou=Exchange Administrative Group (Internal_Name)/cn=Recipients/cn=%'DisplayName'
    Note In this example, the following parameters apply to the cn=%'DisplayName' text:
    • The percent sign (%) is included to indicate the division between a literal value and a variable.
    • A single quotation mark (') is used before and after the variable.
    • DisplayName is the variable that is used in this example.
15. Click Go.

Notes

• For Active Directory replication in large environments, allow for several days before replication is complete.
• Make sure that the X.500 address that you enter is correct.

For more information about the Exchange Server 2003 Notes Tools suite, click the following article number to view the article in the Microsoft Knowledge Base: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.