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:
- 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.
- Right-click Logins and click New Login.
- On the General page of the Login - New dialog box, specify the account in the Login name field and select the Windows Authentication method.
- 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.
- Close the dialog boxes by clicking OK.
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:
- 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.
- 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
- Right-click the SCP object and click Properties.
- In the Properties dialog box, click the Security tab.
- On the Security tab, click Advanced.
- In the Advanced Security Settings dialog box, click Add.
- In the Select User, Computer, or Group (or similar) dialog box, select the administrative account and click OK.
- In the Permission Entry for dialog box, select This object and all descendant (child) objects from the Apply onto drop-down list.
- Allow Create, Readand Write permissions for the Agent Host Account.
- Close the dialog boxes by clicking OK.
Preparing the Target 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 2016organization 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 Exchange 2016 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.