Chat now with support
Chat with Support

Migration Manager for Exchange 8.15 - Source Exchange 2013 Environment Preparation

Source Exchange 2013 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

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.

Configuring Administrator Mailboxes for Public Folder Synchronization

Public folder migration administrator mailboxes should be created on all Exchange 2013 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 2013 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.

Preparing Public Folder Mailboxes for Public Folder Synchronization

In case of two-way public folder synchronization, the source Exchange organization will act as a migration destination during reverse synchronization (from target to source). You need to prepare public folder mailboxes for a successful public folder synchronization as follows:

  1. Ensure that the size of public folder data to be migrated does not exceed the size limit for the primary hierarchy mailbox. If public folder content in the target organization is larger than the limit in the source organization, to migrate it you will need to perform specific steps including creation of additional secondary hierarchy mailboxes in your source Exchange 2013 organization. For detailed instructions, see Appendix B. Migrating Large Public Folders to Exchange 2013 or Higher of Migration Manager for Exchange User Guide keeping in mind that the target of reverse public folder synchronization is your source Exchange organization.
    TIP: For general information on public folders in Exchange 2013, see http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx.
  2. For each public folder mailbox consider adjusting the Recoverable Items quota according to the needs of your Exchange 2013 organization (by default, the limit is 30 GB per mailbox). If the quota limit is exceeded for a public folder mailbox, deletions of content in the target public folders will not be synced back to that source public folder mailbox anymore.
    To change the quota value for a public folder mailbox, invoke the following cmdlet:

Set-Mailbox -Identity PFMailbox -RecoverableItemsQuota 50GB

Creating Custom Throttling Policies

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

New-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name>

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> -RcaMaxConcurrency Unlimited -RcaMaxBurst Unlimited -RcaRechargeRate Unlimited -RcaCutoffBalance Unlimited -PowerShellMaxConcurrency Unlimited

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> –PowerShellMaxConcurrency Unlimited

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

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

Restart-Service -Name MSExchangeThrottling

Important: Described script creates universal custom throttling policies regardless of whether communication with the source Exchange server is performed through MAPI or EWS protocol (used by default). If you migrate to Exchange 2013 (or higher) or Office 365 and the UseEwsProtocolForSourceIfAvailable parameter value is not changed, you can skip creation of throttling policies for MAPI by omitting the following line:

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> -RCAMaxConcurrency 10000 -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null

For details about the UseEwsProtocolForSourceIfAvailable parameter, see Configuring Migration Using PowerShell.

Related Documents