Chat now with support
Chat with Support

Migration Manager for Exchange 8.15 - Target Exchange 2010 Environment Preparation (Legacy)

Target Exchange 2010 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 Appendix A: Exchange 2003 to Exchange 2010 Migration Restrictions

Creating Administrator Mailboxes for Mailbox and Calendar Synchronization (Optional)

Mailbox and calendar synchronization agents access the migrated mailboxes via the administrator mailbox. By default, the Microsoft System Mailbox is used as the administrator mailbox on Exchange 2010 servers. However, in some cases it is necessary to create custom administrator mailboxes and use them instead of the Microsoft System Mailbox.

Creating Custom Throttling Policies

To prevent possible issues in an Exchange 2010 Service Pack 1 or later 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 PowerShell commands for each Exchange Account:

New-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name>

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

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> -PowerShellMaxConcurrency <MaxConcurrency>

Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> –EWSMaxConcurrency $null –EWSPercentTimeInAD $null –EWSPercentTimeinCAS $null –EWSPercentTimeInMailboxRPC $null –EWSMaxSubscriptions $null –EWSFastSearchTimeoutInSeconds $null –EWSFindCountLimit $null

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

Restart-Service -Name MSExchangeThrottling

where MaxConcurrency is the number of Migration Agent for Exchange (MAgE) instances simultaneously working with Exchange 2010 server, multiplied by the value of 5.

NOTE: To ensure stable operation of MAgE agents when working with Microsoft Exchange 2010, you should increase the number of permitted user connections. For that, change the value for the MaxSessionsPerUser parameter using the client throttling policies, as follows:

  1. On the computer that hosts the Microsoft Exchange CAS server, in %Program Files%\Microsoft\Exchange Server\V14\Bin, open the microsoft.exchange.addressbook.service.exe.config file in a text editor.
  2. Change the value of the MaxSessionsPerUser parameter to 100000.
  3. Save and close the file.
  4. Restart the Address Book service.

 

Important: Described script creates universal custom throttling policies regardless of whether communication with the source Exchange server is performed through MAPI (legacy agents or MAgE) or EWS protocol (MAgE only, 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.

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 the NSPI Connection Limit

Important: This step must be performed only if you have any Windows Server 2008 or later domain controllers acting as Global Catalog.

By default, the maximum number of simultaneous Name Service Provider Interface (NSPI) connections equals to 50 per user for Windows Server 2008 or later domain controllers. Therefore, to avoid possible issues related to exceeding that value, you may need to increase the NSPI connection limit on all Windows Server 2008 or later domain controllers acting as Global Catalog. The recommended limit value equals the number of agent instances working simultaneously multiplied by 5.

To change the default connection limit for a domain controller, take the following steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS
  3. Click the Parameters key.
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type NSPI max sessions per user, and then press Enter.
  6. Double-click NSPI max sessions per user, type the appropriate maximum number of the NSPI connections, and then click OK.

  7. Restart the computer or restart Active Directory Domain Services.

For additional information, see the following Microsoft Support articles:

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating