Microsoft KB Archive/251315

= Enabling replies to old organization after Move Server Wizard =

Article ID: 251315

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q251315



SUMMARY
You may need to move some servers, but not all of the servers, from one organization to a new organization, for example, during a gradual migration to a new organization. The Move Server Wizard can selectively move servers from the original organization to the new organization; however, users in the new organization cannot reply to messages that they received before the Move Server Wizard was run if the senders of the messages remain in the old organization.

If you do not want to wait for users to reply to messages until all of the users are moved to the new organization, you have to create custom recipients on the moved server; you can use the InterOrg Synchronization tool to automate this process. You can use the InterOrg Synchronization tool to automate the creation of Simple Mail Transfer Protocol (SMTP) custom recipients, and then add X.500 addresses to the e-mail addresses of the custom recipients.



Creating Custom Recipients on the Moved Server on a Small Scale
To try this method on a small scale, manually add the required custom recipient, and then add an X.500 address to the custom recipient that matches the distinguished name in the original organization:  Create a custom recipient manually on the moved server. This custom recipient has the address of a mailbox on the unmoved server:  In the Exchange Server Administrator program, select the Recipients container under the site that contains the moved server. On the File menu, click New Custom Recipient. Select the type of address that you want this custom recipient to contain, for example, if you use SMTP to deliver mail to the original organization, click Internet Address. Click OK. Type the address for the recipient. This is an address for the recipient on the unmoved server (for example, someone@microsoft.com).  Add the X.500 address to the list of e-mail addresses of the custom recipient:  Double-click the custom recipient object.</li> Click the E-mail Addresses tab, and then click New.</li> In the New E-mail Address dialog box, click Other Address, and then click OK.</li> In the E-mail address box, type the X.500 address for the mailbox on the unmoved server.

There are many methods that you can use to find a user's X.500 address. One easy method is to open a message from that user that was sent before the Move Server Wizard was run. Double-click the sender's name, and the X.500 address is displayed.</li> In the E-mail type box, type X500. Click OK, and then click OK again to close the Custom Recipient Properties dialog box.</li></ol> </li></ol>

Creating Custom Recipients on the Moved Server on a Large Scale
To create custom recipients on the moved server:  In the new organization, create custom recipients that refer to the mailboxes in the original organization. The InterOrg Synchronization tool automates SMTP custom recipient creation between organizations. For more information about the InterOrg Synchronization tool, click the following article number to view the article in the Microsoft Knowledge Base:

238573 Installing, configuring, and using the InterOrg Replication utility

</li> Add X.500 addresses to the custom recipients that refer to the old organization. One way to accomplish this is to export the new organization's custom recipients to a .csv file, add the X.500 address (the OBJ-DIST-NAME attribute from the mailbox that is referred to in the directory of the old organization) to the E-Mail addresses box, and then import the .csv file back to the directory. For more information about bulk import and export, click the following article number to view the article in the Microsoft Knowledge Base:

155414 Bulk Import/Export FAQ

</li></ol>

Additional query words: Pilgrim MSW InterOrg DirSync XADM

Keywords: kbhowto KB251315

-

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

© Microsoft Corporation. All rights reserved.