How to create the Enterprise Vault Service Account's throttling policy manually in Exchange 2013 and higher

Article: 100012182
Last Published: 2025-07-17
Ratings: 3 0
Product(s): Enterprise Vault

Problem

Exchange Server 2013 and higher has 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 higher.

Enterprise Vault includes a PowerShell script, SetEVThrottlingPolicy.ps1 creates a new policy and assigns it to the Vault Service account to remove the restriction. Run SetEVThrottlingPolicy.ps1 against an Exchange 2013 or higher mailbox. 

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.

Solution

These steps are for Exchange 2013 and higher. 

From the Exchange Management Shell, run the following commands. Replace EVThrottlingPolicyNEW and VaultServiceAccount with the relevant values:

  1. Copy the <Install_Path>\Enterprise Vault\PowerShellScripts\SetEVThrottlingPolicy.ps1 file to the Exchange server. 
  2. New-ThrottlingPolicy -name EVThrottlingPolicyNEW
  3. Set-ThrottlingPolicy EVThrottlingPolicyNEW -RcaMaxBurst Unlimited -RcaRechargeRate Unlimited -RcaCutoffBalance Unlimited -RcaMaxConcurrency Unlimited
  4. Set-Mailbox VaultServiceAccount -ThrottlingPolicy EVThrottlingPolicyNEW
  5. 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
  6. Restart the Exchange RPC Client Access Service on the 2013 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.
  7. Enable Dtrace on the ArchiveTask process and start the Exchange archiving task. The Dtrace log will show the throttling policy that has been used on the following line:

    {CAgentTask::CheckThrottlingPolicyDetails:#4705} The throttling policy [CN=EVThrottlingPolicyNEW,CN=Global Settings,CN=EV Lab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=evlab,DC=com] applied to user [CN=EV Service,CN=Managed Service Accounts,DC=evlab,DC=com] has the correct RCAMaxConcurrency value


 

 

Was this content helpful?