The concept of throttling policy is first introduced in Exchange 2007, by which admin can impose some policies that prevents user application from sending number of Remote Procedure Call per second.
Throttling policies are meant for enhancing the Exchange performance in the organization. It keeps a track of consumption of resources by the end-user and also imposes the bandwidth limits.
Admin can Configure throttling policy in Exchange Server 2016/13/10 to enhance and manage the performance of Exchange.
It keeps on checking the Exchange server’s wellness and monitors it for better performance. The purpose of monitoring exchange server is to ensure that no user is staining the exchange environment and the all resources are shared properly among all the users.
In this article we will discuss the more about throttling policy and method by which we can configure Throttling Policy in Exchange 2016,13 & 10.

Throttling Policies Takes Care Of Following Parameters:

• The total time taken when connecting with Client access server
• Number of open concurrent connections a specific user can have
• The time spent on performing mailbox RPC calls
• Time taken while performing Active Directory lookups and calls

Configure Throttling Policy in Exchange:

Exchange Version – 2010

Admin can apply Throttling policies with the commands for enhancing the performance of Exchange by managing it’s workload. The concept of Throttling policies in Exchange 2010 enables admin to control operations that can be made by user in Exchange 2010. here we will go through the different commands used for creating, applying, modifying the throttling policy:

Commands Used in Throttling Policy Configuration

• For creating new policy -New-ThrottlingPolicy
• For applying a policy -Set-ThrottlingPolicy
• To read the policy -Get-ThrottlingPolicy
• For removing Throttling policy -Remove-ThrottlingPolicy

Reading the existing policy

Creating a new throttling policy

user can set new throttling policy with New-ThrottlingPolicy command, here the Outlook web access concurrency is set to 2 by turning off the OWA time in CAS (OWAPercentTimeInCAS) 

For assigning a new throttling policy to user

In order to assign policy to a user, user can use cmdlet Set-Mailbox 

Removing Throttling Policies

Admin can remove the policies that are not set by default and also not associated with any account, for removing the throttling policy user can execute the following command: 

For Exchange Version -2013 & 2016

Admin can configure throttling policy in Exchange 2013/16, some of them are mentioned below:

• In order to limit the concurrent mailbox searches Exchange server 2013/16 uses throttling policy. By default there are two mailbox searches can run concurrently with maximum 50 mailboxes per search. However, admin can set new policy with New-ThrottlingPolicy command.
  Here number of concurrent searches are set to 10 and number mailboxes are 500
• Setting a policy for the specific users 
• Setting a policy for all users 
• Setting a throttling policy to restrict a user to execute 7 cmdlets in 10 second period of time 

Conclusion

As you have read that the article is describing about how to configure throttling policy in Exchange Server 2016, 2013, & 2010. You probably will be aware about the Importance of resource management in Exchange Server.

In Exchange environment it is very necessary to manage performance, it can be done by deploying throttling policies. With throttling policies exchange will keep the track of the resources that each user consumes in exchange environment. Admin can use number of commands to read, apply, create and remove throttling policies.

Tej Pratap Shukla
about.me/tejpratap