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:
|
|
|
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:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS - Click the Parameters key.
- On the Edit menu, point to New, and then click DWORD Value.
- Type NSPI max sessions per user, and then press Enter.
- Double-click NSPI max sessions per user, type the appropriate maximum number of the NSPI connections, and then click OK.
-
Restart the computer or restart Active Directory Domain Services.
For additional information, see the following Microsoft Support articles:
- Error: "Trying to connect to Microsoft Exchange Server" results in MAPI_E_LOGON_FAILED
- NSPI connection to a Windows-based domain controller causes MAPI client applications to fail and returns a "MAPI_E_LOGON_FAILED" error message
Setting Up Connection with the Target Exchange Organization Using SMTP Connectors
This section describes how to set up a connection with the target Exchange organization using SMTP connectors. On this step you may need to coordinate with the administrator of the target Exchange organization to set up the connection properly.
For more details, see the following topics: