April
30th,
2009
In Exchange 2010 Beta is client throttling is __introduced. With client throttling policy you are able to limit the bandwidth used per user. Besides this, you are able to keep an eye on the resources consumed per user.
Besides the default policy it’s possible to add additional policies which you can use to change settings for groups of users. Client throttling can only be managed by using Powershell:
- get-throttlingpolicy, gives an overview of all throttling policies
- new-throttlingpolicy, creates a new throttling policy
- set-throttlingpolicy, modifies a current policy
- remove-throttlingpolicy, deletes a throttling policy
The parameters which need to be used in combination with the Powershell commands are:
- MaxConcurrency, how many simultanious connections may a user create
- PercentTimeInCAS, which percentage of a minute may be used when executing a CAS command
- PercentTimeInAD, which percentage of a minute may be used when executing a LDAP request
- PercentTimeInMailboxRPC, which percentage of a minute may be used for a RPC request to the mailbox
- CPUStartPercent, at which CPU usage level throttling must be applied
- PowerShellMaxConcurrency, the maximum of remote Powershell commands which may be simulatious executed
- PowerShellMaxCmdlets, how many Powershell commands may be executed in a specific time-frame before throttling is applied
- PowerShellMaxCmdletsTimePeriod, with this parameter the time frame, in seconds, can be defined
- PowerShellMaxCmdletQueueDepth, the maximum Powershell tasls which may be executed by a user, a Powershell command may execute several tasks when executed. The advice is to set this value 3 times higher then the value being specified as PowershellMaxConcurrency
The settings being specified in the policy will be applied to the following Exchange components:
- Microsoft Exchange ActiveSync
- Exchange Web Services
- IMAP
- Outlook Web Access
- POP
- PowerShell
- Unified Messaging (UM)
For more information have a look at the pages below:
Comments
