To ensure that users do not lose their mail during the migration period, and to make the migration from one Exchange organization to another smooth, Migration Manager establishes mail redirection between the source and the target Exchange servers.
Accordingly, Migration Manager requires the following:
First, open the Migration Manager for Active Directory console. Expand the node of the appropriate domain pair, and open the properties of the Synchronization node under it. Go to the Specify Exchange Options step, and configure the options in the Mailbox redirection settings group.
For mail redirection purposes, the Directory Synchronization Agent adds the secondary SMTP address to the proxy addresses list of the mailbox-enabled object (the proxyAddresses attribute). You can specify the SMTP address templates to create the secondary SMTP addresses that will be applied to the source and target mailbox-enabled objects.
Caution: You should analyze your environment for SMTP namespaces and for redirection implement SMTP address templates that are NOT being used.
To forward mail to a recipient in another Exchange organization, the Directory Synchronization Agent populates the target address property (the targetAddress attribute) of either the source or target mailbox, depending on which mailbox is currently being used, with the additional SMTP address created for redirection.
Target SMTP address template—Specify the SMTP address template for the target accounts so that the target users receive their mail during the synchronization.
Source SMTP address template—Specify the SMTP address template for the source accounts so that the source users receive their mail during the synchronization.
If contacts with the same SMTP or X500 address as the synchronized objects already exist in the opposite directory, Migration Manager can merge SMTP addresses and membership for these objects and delete the corresponding contacts. To use this functionality, select the Merge objects with corresponding contacts check box. This option is applicable if you select the Mail-enabled users, Mail-enabled users for Native Move or the Mailbox-enabled users option above.
For uninterrupted user collaboration during the migration, users in each source and target Exchange organization should see other users in their Global Address Lists. That is why two mailboxes, source and target, exist for each user. However, all mail sent to the user should arrive to the mailbox he or she is currently using, no matter which mailbox it was sent to. To achieve this, mail should be automatically forwarded to the currently-used mailbox from the other mailbox.
Direct forwarding to a recipient in another Exchange organization can be done by using the target address property of the mailbox.
After you register the source or target organization, Migration Manager enumerates the administrative groups, servers, and recipient objects of the organization. Information about all Exchange objects of the registered organizations is stored in the Migration Manager database. This information is not updated automatically; you have to refresh it when changes occur.
To refresh the information for any Exchange server, right-click the server in the management tree and select Refresh from the shortcut menu.
If you do not need to refresh the entire server (which may take some time), you can simply add new recipients to the Migration Manager configuration database. Right-click a server that holds the recipients that should be added and click Add Recipients to Database. In the dialog box that appears, use the search tools to find the recipients you need, and then select them in the Search results list and click OK.
The recommended way to perform data migration successfully is to use standalone agent host servers instead of deploying Migration Manager agents on the Exchange servers.
For detailed information about configuring and using agent hosts for Exchange migration please refer to the Using Agent Hosts for Migration Agents topic.
Hereafter, when the discussion describes Migration Manager for Exchange agents being installed, run, etc. on the Exchange server, "the Exchange server" can denote either the Exchange server or a standalone agent host server associated with it, if any.
The most convenient way to work with Migration Manager for Exchange agents is to use the Agent Management node in the management tree view. Selecting this node opens a console layout in the right pane with tools for finding, adding, removing and configuring agents. The scope of the Agent Management node is project-wide. For details about filtering agent information, see the Filtering Agents by Job and Collection topic.