Chat now with support
Chat with Support

Migration Manager for Exchange 8.15 - Source Exchange 2007 Environment Preparation

Source Exchange 2007 Environment Preparation
Preparation Overview Checking System Requirements Setting Up Accounts and Required Permissions Preparing the Source Exchange Environment for Exchange Migration Setting Up Connection with the Target Exchange Organization Using SMTP Connectors

Granting Membership in the Local Administrators Group on the License Server

The Source Agent Host Account should be a member of the local Administrators group on the license server (unless alternative credentials are used for the license server).


  • If license server is a domain controller, the account should be added to the domain local Administrators group of the domain.
  • Local Administrator permissions are required on the license server if this license server is located in another trusted forest.

To add the Source Agents Host Account to the local Administrators group on the license server perform the following:

  1. Open the Computer Management snap-in (Click Start | Run, enter compmgmt.msc and then click OK).
  2. In the left pane click System Tools | Local Users and Groups | Groups.
  3. Right-click the Administrators group and click Add to Group.
  4. Click Add and select the Source Agent Host Account (in our example, QMM_Src_AH).
  5. 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

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)

Caution: If you skip this step, you must manually turn off using the Aelita EMW Recycle Bin folder during public folder synchronization (set the UseRecycleBin parameter to 0). See the Use Fine-Tuning the Agents section of the Migration Manager for Exchange User Guide for details.

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. Replicate this folder to all the public folder servers involved in the public folder synchronization process.

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.

Caution: Only deleted public folders will be put into the Aelita EMW Recycle Bin. If you delete a message from a public folder, it will be destroyed permanently in both the Source and Target Exchange organizations.

Related Documents