The following steps will create a new "migration throttling policy" for all mailbox-enabled users in Exchange 2010. In Exchange 2010 SP2 RU4 or later, the way Exchange Web Service (EWS) throttling policies were applied changed to also include the end-user mailboxes that are migrating (see Note below). These steps are valid for Exchange 2010 SP2 RU4 or later when it is either a migration Source or Target:
1. Open an Exchange Management Shell and enter the following cmdlets:
Set-ThrottlingPolicy ODME_Policy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null
Get-Mailbox -ResultSize unlimited | Set-Mailbox -ThrottlingPolicy ODME_Policy
2. Open a Command Prompt on the Exchange server and perform an "IISRESET" or Recycle the MSExchangeServicesAppPool application pool within the IIS Management Console on the Exchange server(s) that are hosting the EWS URL that was entered into the ODME connection settings.
Note: Once the migration project is complete, you may want to remove the ODME_Policy from all users by running the following cmdlet in an Exchange Management Shell to restore normal Exchange functionality:
Get-Mailbox -ResultSize unlimited | Remove-ThrottlingPolicy ODME_Policy
For more generic information on Exchange Throttling Policies have a look at the following Microsoft Technet article.
Note: Depending on the exact version of Exchange being used, this throttling policy may need to be applied to either the Exchange migration admin user, and/or to the end-user mailbox that is migrating. See the following Microsoft MSDN article that explains who the throttling policy counts against, depending on the exact version of Exchange in use:
When in doubt, we suggest adding both the Exchange migration admin and the user(s) being migrated to the ODME Exchange throttling policy, as described in the steps above.
© 2019 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad