How to create the Enterprise Vault Service Account's throttling policy manually in Exchange 2010

Problem

Exchange Server 2013 and 2010 have a default throttling policy which restricts user accounts to no more than 20 open connections to the server. This restriction on the Vault Service account would cause failures of the Enterprise Vault tasks that run under the account. To prevent these failures, you must remove the restriction from the Vault Service account when you archive from Exchange Server 2013 and 2010.

Enterprise Vault includes a PowerShell script called SetEVThrottlingPolicy.ps1 which creates a new policy and assigns it to the Vault Service account to remove the restriction. You must run SetEVThrottlingPolicy.ps1 against an Exchange 2013 or 2010 mailbox. If your Vault Service account already has a mailbox on Exchange Server
2007 or earlier, you must first move the mailbox to Exchange 2013 or 2010.

However, in certain circumstances it may be problematic to create and assign this policy via the powershell script provided. In those situations the below commands can be manually run to create and assign the policy to the Vault Service Account mailbox.

Error Message

Solution

These steps are for Exchange 2010 only.  For Exchange 2013 see article 100012182

From the Exchange Management Shell, run the following commands. Replace VaultServiceAccount with the relevant value:

1. New-ThrottlingPolicy -name EVThrottlingPolicy
2. Set-ThrottlingPolicy EVThrottlingPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null
3. Set-Mailbox VaultServiceAccount -ThrottlingPolicy EVThrottlingPolicy
4. Run the following command to confirm that the throttling policy has been assigned to the Vault Service Account mailbox by checking the ThrottlingPolicy setting: Get-Mailbox -Identity VaultServiceAccount | fl
5. Restart the Exchange Remote Procedure Call (RPC) service on the Exchange 2010 Server, for the policy to take immediate effect. If the service is not restarted the change can take up to two hours to take effect.
6. DTRACE the ArchiveTask process and start the Exchange 2010 archiving task. The DTRACE log will show the throttling policy has been used on the following line:
   
   {CAgentTask::CheckThrottlingPolicyDetails:#4705} The throttling policy [CN=EVThrottlingPolicy,CN=Global Settings,CN=EV Lab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=evlab,DC=com] applied to user [CN=VSA,CN=Managed Service Accounts,DC=evlab,DC=com] has the correct RCAMaxConcurrency value