Chat now with support
Chat with Support

Migration Manager for Exchange 8.14 - Target Exchange 2016 Environment Preparation

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

Creating Custom Throttling Policies

To prevent possible issues in an Exchange 2016 organization, you should create custom throttling policies, apply them to the Exchange Accounts and then restart the Microsoft Exchange Throttling Service. To do this, run the following cmdlets in Exchange Management Shell for each Exchange Account:

New-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name>

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited –PowerShellMaxConcurrency Unlimited

Set-ThrottlingPolicyAssociation -Identity <QMM_Exchange_Account_Name> -ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name>

Restart-Service -Name MSExchangeThrottling

Preparing Agent Host for Public Folder Synchronization Agents

To perform public folder synchronization you will need one (or more) standalone agent host server associated with each target Exchange 2016 server.

Such agent host must meet the following specific requirements:

  • Outlook 2013 32-bit or Outlook 2016 32-bit version must be installed on the agent host.
  • The agent host must be used only for PFSA and PFTA to work with target Exchange 2016. No other agents can be installed on it.

Note: For complete set of requirements, see Exchange Migration Agents Server in the System Requirements and Access Rights document.

Later when configuring migration in Migration Manager for Exchange console, after you register that agent host(s), open its Properties, go to the General | Connection node and select the Communicate with Exchange Server via Outlook MAPI option. Then select the agent host as Default Agent Host in the Properties of an Exchange 2016 server.

Creating Aelita EMW Recycle Bin Public Folder (Optional)

Note: If you skip this step, the Aelita EMW Recycle Bin folder will be created automatically by PFTA during public folder synchronization.

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.

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.

Configuring Administrator Mailboxes for Public Folder Synchronization

Public folder migration administrator mailboxes should be created on all Exchange 2016 servers involved in public folder synchronization. These mailboxes will be used to access the public folder tree when creating public folder synchronization jobs.

Caution: The administrator mailbox specified for the synchronization job should not be changed during the synchronization process.

The administrator mailboxes should not be included in mailbox or calendar synchronization jobs.

After you created public folder migration administrator mailboxes, take the following steps:

  1. Ensure that the Exchange 2016 organization has primary hierarchy mailbox (which is the first created public folder mailbox in organization). If there are no public folder mailboxes yet, create one. It will automatically become primary hierarchy mailbox.
  2. After that associate public folder migration administrator mailbox specified for the public folder synchronization with the primary hierarchy mailbox. To do this, run the following cmdlet in Exchange Management Shell:

Set-Mailbox –Identity <Public_Folder_Migration_Administrator_Mailboxes> -DefaultPublicFolderMailbox <Primary_Hierarchy_Mailbox>

Caution: The mailbox database and root public folder specified for the synchronization job should not be renamed during the synchronization process.

Related Documents