Migration Manager for Exchange 8.15 - Source Exchange 2013 Environment Preparation

Granting SCP Create, Read and Write Permissions

Grant the Agent Host Account permissions to Create, Read and Write Service Connection Point (SCP) object located in the CN=Exchange Migration Project,CN=QmmEx,CN=Migration Manager,CN=Quest Software,CN=System,DC=eternity,DC=<...>,DC=<...> container:

1. From the Start menu, select Run. In the Run dialog box, type ADSIEdit.msc. Click OK.

   NOTE: If you have a Windows 2003 domain controller, the ADSIEdit utility, which is part of the Windows 2003 Support Tools, may not be installed. In this case install the Support Tools by running the Support\Tools\Suptools.msi file located on the Windows 2003 CD.

2. In the ADSIEdit snap-in, open the CN=Exchange Migration Project,CN=QmmEx,CN=Migration Manager,CN=Quest Software,CN=System,DC=eternity,DC=<...>,DC=<...> container
3. Right-click the SCP object and click Properties.
4. In the Properties dialog box, click the Security tab.
5. On the Security tab, click Advanced.
6. In the Advanced Security Settings dialog box, click Add.
7. In the Select User, Computer, or Group (or similar) dialog box, select the administrative account and click OK.
8. In the Permission Entry for dialog box, select This object and all descendant (child) objects from the Apply onto drop-down list.
9. Allow Create, Readand Write permissions for the Agent Host Account.
10. Close the dialog boxes by clicking OK.

Preparing the Source Exchange Environment for Exchange Migration

Perform the steps described in the related subtopics to ensure that your Exchange environment is ready for migration:

• Backing Up Exchange
• Creating Aelita EMW Recycle Bin Public Folder (Optional)
• Installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
• Configuring Administrator Mailboxes for Public Folder Synchronization
• Preparing Public Folder Mailboxes for Public Folder Synchronization
• Creating Custom Throttling Policies
• Configuring the NSPI Connection Limit
• Setting Exchange Autodiscover URL (Optional)

Backing Up Exchange

Before implementing Migration Manager for Exchange in your production environment, back up your Exchange infrastructure. We recommend that Active Directory data be backed up at least twice a day during migration.

Transaction Log File Cleanup

When Migration Manager for Exchange synchronizes mail, for every megabyte of data migrated from the source to the target, a transaction log file of equal size is generated on the target Exchange server. Exchange-aware backup applications purge the transaction logs after the backup completes. By the time the backup finishes, all logged transactions have already been applied to the store and backed up to tape, making log cleaning safe.

Large transaction logs that are generated during mailbox migration quickly occupy free disk space. To work around this problem, perform one of the following:

• If a full backup strategy is implemented in the organization or there is no backup strategy at all, then circular logging may be enabled for unattended log deletion.
• If an incremental or differential backup strategy is already implemented in the organization, then make sure that logs are cleared automatically when backup process is finished. Do not enable circular logging in this case.

Note also that Microsoft recommends turning OFF circular logging on the Exchange server. For more information, refer to Microsoft Knowledge Base article 147524: XADM: How Circular Logging Affects the Use of Transaction Logs.

Creating Aelita EMW Recycle Bin Public Folder (Optional)

If you plan to perform public folder synchronization using Migration Manager Public Folder agents, you should create a special public folder called Aelita EMW Recycle Bin.

This folder will help prevent data loss in case of accidental public folder deletion. When a public folder is deleted in one of the environments, the public folder synchronization agents move the corresponding folder in the other environment to the Aelita EMW Recycle Bin folder, if it exists, instead of permanently deleting the folder. You can use this folder to check whether important information has been deleted, and restore any data deleted by mistake.