Chat now with support
Chat with Support

Migration Manager for Exchange 8.15 - Source Exchange 2016 Environment Preparation

Source Exchange 2016 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 db_owner Role on SQL Server

To grant the db_owner role on the SQL Server for the Agent Host Account, take the following steps:

  1. In SQL Server Management Studio, browse to the server that will be used by Migration Manager for Exchange, and select Logins from the server Security node.
  2. Right-click Logins and click New Login.
  3. On the General page of the Login - New dialog box, specify the account in the Login name field and select the Windows Authentication method.
  4. On the User Mapping page of the Login - New dialog box, select the migration project database and then select db_owner database role for that database.
  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:

Additional steps for public folder synchronization

Preparation of Exchange 2016 organization for public folder synchronization is different from preparation of any earlier Exchange version. The main distinction is that public folder synchronization agents (PFSA and PFTA) communicate with Exchange2016 Server via Outlook MAPI instead of Microsoft Exchange Server MAPI Client and CDO.

If you perform public folder synchronization with Exchange 2016 organization, take the following additional steps.

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.

Installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

Installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

Migration Manager needs version 6.5.8353.0 or later of Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 to be installed on the computers where Migration Manager agents will run (that is, Exchange 2007 and 2010 Servers and agent hosts only).

Since the MAPI CDO setup package is not available for distribution, you should download it from the Microsoft Web site. At the moment of the last document update, the download link is http://www.microsoft.com/en-us/download/details.aspx?id=42040.

After installing the API, restart the computer.

Related Documents