Product Documentation
Abstract
Microsoft Exchange Server 2013 and 2016 uses client throttling policies to manage performance in an Exchange environment. This document describes how to disable the throttling.
Content
About this task
When a Microsoft Exchange Server environment is set up, the default throttling policies are automatically created to manage the load balance across all client users within the environment.
Through these policies, Microsoft Exchange evaluates how a client user uses the system, and ensures that the resulting load is within acceptable boundaries defined for each user. This client throttling system tracks system usage per client user and uses the throttling policy associated with each user to determine if throttling should occur.
For client users, you can define an acceptable load by using the cmdlet parameter values in the Set-Mailbox and New-Mailbox cmdlets to associate throttling policies with a user or a group of users by modifying properties in the user mailboxes.
For detailed information, see the Microsoft Exchange Message Throttling documentation at http://technet.microsoft.com/en-us/library/bb232205.aspx
IMPORTANT
By default, MaxConcurrency is set to 10 connections. Increase this value if you configured an environment that uses more than one IBM® Content Collector server or you configured multiple connectors in a single IBM Content Collector server.
Procedure
If you encounter a noticeable decrease in performance:
1. Check if Event ID is logged on Exchange Client Access Server (CAS ) or on Exchange Server itself (in case of Exchange 2016 where CAS role is merged with Exchange server) on which Content Collector service account should be unthrottled.
2. If these events were logged, run the following command in Exchange Management Shell to create a policy to disable the throttling.
New-ThrottlingPolicy -Name <POLICY_NAME>
NOTE: All the parameter values in this step are Default values.
3. The Parameters RCAPercentTimeInCAS, RCAPercentTimeInMailboxRPC,and RCAPercentTimeInAD are not applicable for Exchange 2013 and Exchange 2016 and hence they not present in Exchange 2013 and Exchange 2016.
- The following parameters are applicable to modify throttling for Content Connector service user in Exchange 2013 and Exchange 2016:
a) RCAMaxConcurrency: Specifies how many concurrent connections an RPC Client Access user can have against an Exchange server at one time.
b) OWAMaxConcurrency: Specifies concurrent connections for OWA services.
c) OutlookMaxConcurrency: Specifies concurrent connections for Outlook Services.
d) EWSMaxConcurrency: Specifies concurrent connections for Exchange Web Services.
Set –ThrottlingPolicy –Identity <POLICY_NAME> - RCAMaxConcurrency $null OWAMaxConcurrency $null OutlookMaxConcurrency $null EWSMaxConcurrency $null
5. Run the following command to assign the new policy to the content collector service account.
Set-Mailbox –Identity <IBM Content Collector Service Account_NAME> -ThrottlingPolicy <POLICY_NAME>
6. Check if event ID 2915 is still logged.
If these events are still reported, throttling was not disabled and the defaults were inadvertently used. Assign large values that are unlikely to be reached.
For example, run the following command:
Set-ThrottlingPolicy –Identity <POLICY_NAME> - RCAMaxConcurrency $1000 OWAMaxConcurrency $1000 OutlookMaxConcurrency $1000 EWSMaxConcurrency $1000
NOTE: When assigning large values, it is possible to assign ‘Unlimited’ value. However, it is observed in Exchange 2016 that even in the case of ‘Unlimited’ value, the defaults are inadvertently used. Hence, it is recommended to use larger values instead of ‘Unlimited’.
7. Again, check if Event ID 2915 is logged.
If this event is still reported, increase the values in the policy.
Throttling is successfully disabled when this event is no longer logged.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27050599