Microsoft Exchange Server 2010 and 2013 uses
client throttling policies to manage performance in an Exchange environment.
About this task
When a Microsoft Exchange Server environment is set up,
default throttling policies are automatically created to manage the
load balance across all client users within the environment.
Through
policies, Microsoft Exchange evaluates how a client user uses the
system and ensures that the resulting load falls 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, refer to 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.
Procedure
If you encounter a noticeable drop in performance:
- Check if the event ID 2915 was logged on the Exchange CAS
(Client Access Server) server and which Content Collector service account should
be unthrottled.
- If these events were logged, enter New-ThrottlingPolicy
ICC_NO_RCA_THROTTLING in an Exchange Management Shell
to create a policy that disables throttling.
- Set all values to $null (no throttling limit) by entering Set-ThrottlingPolicy
-Identity ICC_NO_RCA_THROTTLING -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC
$null -RCAMaxConcurrency $null -RCAPercentTimeInAD $null
- Enter Set-Mailbox -Identiy <IBM
Content Collector service account> -ThrottlingPolicy ICC_NO_RCA_THROTTLING to
assign the new policy to the Content Collector service account.
- Check if the event ID 2915 is still logged.
If
these events are still reported, throttling could not be disabled
and the defaults were inadvertently used. Assign large values that
are unlikely to be reached. For example, enter Set-ThrottlingPolicy
-Identity ICC_NO_RCA_THROTTLING -RCAPercentTimeInCAS $5000 -RCAPercentTimeInMailboxRPC
$5000 -RCAMaxConcurrency $100000 -RCAPercentTimeInAD $5000
Note
that due to concurrent process requests percentage based budgets exceeding
100 percent might be required.
- Again, check if the 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.