Search <book_title>...

Enterprise Vault™ Installing and Configuring

Last Published: 2018-04-09

Product(s): Enterprise Vault (12.3)

Configuring the Exchange throttling policy on the Vault Service account

Note:

The following procedure describes the configuration of the Vault Service account. If you run Exchange archiving tasks under a service account other than the Vault Service account, run the procedure against this other account.

Exchange 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.

You must remove the restriction from the Vault Service account. 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.

Note the following requirements for this script:

If you archive from both Exchange 2010 and Exchange 2013 or later, you must run the script in the Exchange Management Shell on an Exchange 2013 or later server.
If both Exchange 2010 and Exchange 2013 or later are present in your environment, the script automatically configures Exchange 2010 servers before later servers. The script includes the option to configure Exchange throttling policies separately for each Exchange version. If you choose to use this option, you must configure the Exchange 2010 throttling policy first.

If you would rather configure the throttling policy manually than run the PowerShell script, the following articles on the Veritas Support website describe how to do so:

For Exchange 2010:	https://www.veritas.com/docs/100006018
For Exchange 2013 or later:	https://www.veritas.com/docs/100012182

To configure the Exchange throttling policy by running the PowerShell script

Log in to an Exchange server using an account that is assigned the following management roles:
- Mail Recipients
- Recipient Policies
By default, members of the "Organization Management" role group are assigned these roles.
Copy the SetEVThrottlingPolicy.ps1 script from the Veritas Enterprise Vault\PowerShell Scripts folder on the Enterprise Vault media to the Exchange server.
On the Exchange server, open the Exchange Management Shell.
If you moved an existing Vault Service account mailbox from Exchange 2007 or earlier, update the mailbox using the following command:
Set-Mailbox mailbox_name -ApplyMandatoryProperties
Where:
mailbox_name is the name of the Vault Service account's mailbox. If mailbox_name contains spaces, enclose it in quotation marks.

Run SetEVThrottlingPolicy.ps1. The syntax is as follows:

.\SetEVThrottlingPolicy.ps1 -user domain\user_name [-server exchange_mailbox_server] [-version exchange_version] [-DomainController domain_controller_name]

Where the parameters are as follows:

-user	Specifies the Vault Service account and the domain to which it belongs. If *user_name* contains spaces, enclose the whole **domain\user_name** string in quotation marks. If you run Exchange in a cross-forest environment, run the script against the disabled user account that owns the Vault Service account's linked mailbox. See Creating a mailbox for the Vault Service account.
-server	Specifies the name of the Exchange mailbox server. You must specify an Exchange mailbox server if you run the script on a computer other than the mailbox server.
-version	Specifies the version of Exchange Server for which you want to configure the throttling policy: 2010 or 2013AndLater.
-DomainController	Specifies the name of a domain controller in the domain of which the Vault Service account is a member. This parameter is optional. However, in a cross-forest environment, you must specify the resource domain so that the script runs against the Vault Service account's linked mailbox in the resource forest.

When the script finishes, close the Exchange Management Shell.
To force these changes to take effect immediately, restart the Microsoft Exchange RPC Client Access service on each Exchange server where the service exists.
If you do not restart the service then, by default, the changes can take up to two hours to take effect.