How to use the ADModify.NET tool to add an X.500 proxy address to a user account

This article has been archived. It is offered "as is" and will no longer be updated.
This article describes how to use the ADModify.NET tool to add an X.500 proxy address to a user account.
To use the ADModify.NET tool to add an X.500 proxy address to a user account, follow these steps.

Note The ADModify.NET tool requires the Microsoft .NET Framework.
  1. Start the ADModify.NET tool.
  2. Click Modify Attributes.
  3. In the Domain List list, select the domain with which you want to work.
  4. In the Domain Controller List list, select the domain controller with which you want to work.
  5. In the Show Only section, click to select the Users check box.
  6. Click the arrow to search the domain.
  7. In the search results, click the organizational unit (OU) with which you want to work, and then click Add To List.
  8. In the details pane, select individual users. Alternatively, click Select All.

    Note We recommend that you test these steps on a single recipient before you continue with bulk modifications.
  9. Click Next.
  10. Click the Custom tab.
  11. Under Custom Attribute Set, follow these steps:
    1. Click to select the Make a customized attribute modification check box.
    2. In the Attribute Name box, type proxyAddresses.
    3. In the Attribute Value box, type the X.500 address.

      For example, if you want an X.500 address of /o=OldOrganization/ou=OldSite/cn=Recipients/cn=mailNickname, type the following in the Attribute Value box:

      In this example, we use the %'mailNickname'% variable because we assume that the mailNickname attribute in the new organization matches the mailNickname attribute in the old organization. If these attributes do not match, use another variable.

      Note If the migrated user account is from an Active Directory directory service environment, use the Adsiedit tool to locate the old legacyExchangeDN attribute of the user. Then, use the old legacyExchangeDN attribute for the X.500 address.
    4. Click Multivalued Append, and then click Go.
To verify the X.500 address of the user, follow these steps:
  1. In Active Directory Users and Computers, locate the user whose X.500 address you want to verify.
  2. Right-click the user, and then click Properties.
  3. Click the E-mail Addresses tab, click the X.500 address, and then click Edit.

    You can copy the value to send a test e-mail message to the user.
  4. Start Microsoft Outlook 2002 or Microsoft Office Outlook 2003.
  5. Create a new e-mail message, type the X.500 address of the migrated user in the To box, click Tools, and then click Check Names.

    The following is an example of an X.500 address:
  6. Send the e-mail message.
  7. Verify delivery of the e-mail message by using the new e-mail address.
An X.500 address can be added to a mailbox because old e-mail messages in a migrated mailbox contain these addresses. Therefore, if this address is not present in the new Exchange system, all the replies to these old e-mail messages receive non-delivery reports (NDRs).

You can follow the steps in this procedure if you use one of the following methods to migrate a user account from one server that is running Microsoft Exchange to another server that is running Microsoft Exchange:
  • You copy the mailbox information to a .pst file, delete the existing mailbox, re-create the mailbox on another Exchange server, and then import the .pst file to the newly created mailbox.
  • You use the Microsoft Exchange Server Mailbox Merge Wizard (Exmerge.exe) to migrate the mailbox to another Exchange server.
If e-mail messages are sent from that user account before the migration, the following issues may occur because the X.500 address of the user account has changed:
  • The recipient may not be able to reply to the messages.
  • The sender may receive an NDR that contains the following error message:
    The recipient name is not recognized.
  • Any calendar appointments that contain the migrated user account are no longer linked to that user account.
These issues occur because the site name is part of the X.500 address. Microsoft Exchange Server uses the X.500 address for internal e-mail addressing.
For more information about performing a similar procedure without using the ADModify.NET tool, click the following article number to view the article in the Microsoft Knowledge Base:
313324 How to set X500 proxy addresses for Exchange Server 2003 recipients and for Exchange 2000 Server recipients

For more information about the ADModify.NET tool, visit the following Web site:

Article ID: 909271 - Last Review: 12/09/2015 03:28:57 - Revision: 2.2

Microsoft Exchange 2000 Server Standard Edition, Microsoft Exchange 2000 Enterprise Server, Microsoft Exchange Server 2003 Enterprise Edition, Microsoft Exchange Server 2003 Standard Edition

  • kbnosurvey kbarchive kbexchdirectory kbprb KB909271