Throttling policies enable you to change the amount of resources can be used by mailboxes that are assigned that throttling policy. For example, you may want to increase the maximum concurrent Outlook and OWA connections for a mailbox that needs to have many concurrent open connections.
In this post, I’ll demonstrate how to create a new throttling policy that allows for more concurrent OWA and Outlook connections and then I’ll assign the throttling policy to a mailbox.
The first command we will use is New-ThrottlingPolicy. This creates a new throttling policy (funnily enough?) and is a group of throttling settings which you can apply to a mailbox later on. We’ll be setting up a new throttling policy with the settings below:
- Name: HighUsageMailboxes
- OwaMaxConcurrency: 100 (Default is 5. Increasing this value increases the allowed maximum concurrent connections that an OWA user can have open against an Exchange server at a time)
- RcaMaxConcurrency: 100 (Default is 40. Increasing this value increases the allowed maximum concurrent connections that an RPC user can have against an Exchange server at a time)
New-ThrottlingPolicy -Name HighUsageMailboxes -OwaMaxConcurrency 100 -RcaMaxConcurrency 100
To confirm and check settings on our new throttling policy, we can use the Get-ThrottlingPolicy cmdlet:
Get-ThrottlingPolicy HighUsageMailboxes | fl
This provides all the current settings - a partial output is shown above. For more informations on the settings that can be changed, see here.
Assign throttling policy to a mailbox
To assign a throttling policy to a mailbox, we use the Set-Mailbox cmdlet. We’ll assign the HighUsageMailboxes throttling policy to the Sales mailbox:
Set-Mailbox Sales -ThrottlingPolicy HighUsageMailboxes
We can now confirm that our Sales mailbox has the new throttling policy by running the command below:
Get-Mailbox Sales | ft Name,ThrottlingPolicy
In this quick post, I’ve demonstrated how to set up a new throttling policy and assign it to a mailbox.