Applies to: Exchange Server 2013, Exchange Online
Topic Last Modified: 2013-01-16
Use the New-ThrottlingPolicy cmdlet to create a non-default user throttling policy.
For information about the parameter sets in the Syntax section below, see Syntax.
Syntax
New-ThrottlingPolicy -Name <String>
[-AnonymousCutoffBalance <Unlimited>] [-AnonymousMaxBurst
<Unlimited>] [-AnonymousMaxConcurrency <Unlimited>]
[-AnonymousRechargeRate <Unlimited>] [-Confirm
[<SwitchParameter>]] [-CpaCutoffBalance <Unlimited>]
[-CpaMaxBurst <Unlimited>] [-CpaMaxConcurrency
<Unlimited>] [-CpaRechargeRate <Unlimited>]
[-DiscoveryMaxConcurrency <Unlimited>] [-DiscoveryMaxKeywords
<Unlimited>] [-DiscoveryMaxKeywordsPerPage <Unlimited>]
[-DiscoveryMaxMailboxes <Unlimited>]
[-DiscoveryMaxPreviewSearchMailboxes <Unlimited>]
[-DiscoveryMaxRefinerResults <Unlimited>]
[-DiscoveryMaxSearchQueueDepth <Unlimited>]
[-DiscoveryMaxStatsSearchMailboxes <Unlimited>]
[-DiscoveryPreviewSearchResultsPageSize <Unlimited>]
[-DiscoverySearchTimeoutPeriod <Unlimited>]
[-DomainController <Fqdn>] [-EasCutoffBalance
<Unlimited>] [-EasMaxBurst <Unlimited>]
[-EasMaxConcurrency <Unlimited>]
[-EasMaxDeviceDeletesPerMonth <Unlimited>] [-EasMaxDevices
<Unlimited>] [-EasMaxInactivityForDeviceCleanup
<Unlimited>] [-EasRechargeRate <Unlimited>]
[-EwsCutoffBalance <Unlimited>] [-EwsMaxBurst
<Unlimited>] [-EwsMaxConcurrency <Unlimited>]
[-EwsMaxSubscriptions <Unlimited>] [-EwsRechargeRate
<Unlimited>] [-ExchangeMaxCmdlets <Unlimited>]
[-ForwardeeLimit <Unlimited>] [-IgnoreDehydratedFlag
<SwitchParameter>] [-ImapCutoffBalance <Unlimited>]
[-ImapMaxBurst <Unlimited>] [-ImapMaxConcurrency
<Unlimited>] [-ImapRechargeRate <Unlimited>]
[-IsServiceAccount <SwitchParameter>] [-MessageRateLimit
<Unlimited>] [-Organization <OrganizationIdParameter>]
[-OwaCutoffBalance <Unlimited>] [-OwaMaxBurst
<Unlimited>] [-OwaMaxConcurrency <Unlimited>]
[-OwaRechargeRate <Unlimited>] [-OwaVoiceCutoffBalance
<Unlimited>] [-OwaVoiceMaxBurst <Unlimited>]
[-OwaVoiceMaxConcurrency <Unlimited>] [-OwaVoiceRechargeRate
<Unlimited>] [-PopCutoffBalance <Unlimited>]
[-PopMaxBurst <Unlimited>] [-PopMaxConcurrency
<Unlimited>] [-PopRechargeRate <Unlimited>]
[-PowerShellCutoffBalance <Unlimited>] [-PowerShellMaxBurst
<Unlimited>] [-PowerShellMaxCmdletQueueDepth
<Unlimited>] [-PowerShellMaxCmdlets <Unlimited>]
[-PowerShellMaxCmdletsTimePeriod <Unlimited>]
[-PowerShellMaxConcurrency <Unlimited>]
[-PowerShellMaxDestructiveCmdlets <Unlimited>]
[-PowerShellMaxDestructiveCmdletsTimePeriod <Unlimited>]
[-PowerShellMaxOperations <Unlimited>]
[-PowerShellMaxRunspaces <Unlimited>]
[-PowerShellMaxRunspacesTimePeriod <Unlimited>]
[-PowerShellMaxTenantConcurrency <Unlimited>]
[-PowerShellMaxTenantRunspaces <Unlimited>]
[-PowerShellRechargeRate <Unlimited>] [-PswsMaxConcurrency
<Unlimited>] [-PswsMaxRequest <Unlimited>]
[-PswsMaxRequestTimePeriod <Unlimited>]
[-PushNotificationCutoffBalance <Unlimited>]
[-PushNotificationMaxBurst <Unlimited>]
[-PushNotificationMaxBurstPerDevice <Unlimited>]
[-PushNotificationMaxConcurrency <Unlimited>]
[-PushNotificationRechargeRate <Unlimited>]
[-PushNotificationRechargeRatePerDevice <Unlimited>]
[-PushNotificationSamplingPeriodPerDevice <Unlimited>]
[-RcaCutoffBalance <Unlimited>] [-RcaMaxBurst
<Unlimited>] [-RcaMaxConcurrency <Unlimited>]
[-RcaRechargeRate <Unlimited>] [-RecipientRateLimit
<Unlimited>] [-ThrottlingPolicyScope <Regular |
Organization | Global>] [-WhatIf
[<SwitchParameter>]]
|
Examples
EXAMPLE 1
This example creates a non-default user throttling policy that can be associated with specific users. Any parameters that you omit inherit the values from the default throttling policy GlobalThrottlingPolicy_<GUID>. After you create this policy, you must associate it with specific users.
Copy Code | |
---|---|
New-ThrottlingPolicy -Name ITUserPolicy -EwsMaxConcurrency 4 -ThrottlingPolicyScope Regular |
EXAMPLE 2
This example creates a policy that applies to all users in your organization. Any parameters that you omit inherit the values from the default throttling policy GlobalThrottlingPolicy_<GUID>.
Copy Code | |
---|---|
New-ThrottlingPolicy -Name AllUsersEWSPolicy -EwsMaxConcurrency 4 -ThrottlingPolicyScope Organization |
EXAMPLE 3
This example creates a throttling policy RemoteSiteUserPolicy that restricts the number of connections for a user to three. The users associated with this policy are only able to create three remote Exchange Management Shell sessions. This policy also restricts to three the number of Exchange Administration Center operations or Exchange Web Services operations that can be executed at the same time.
Copy Code | |
---|---|
New-ThrottlingPolicy -Name RemoteSiteUserPolicy -PowerShellMaxConcurrency 3 -PowerShellMaxCmdletQueueDepth 12 |
EXAMPLE 4
This example creates a throttling policy that restricts a user to be able to only execute 10 cmdlets in a period of five seconds. If the users associated with this policy exceed this number, the cmdlet pipeline execution is stopped with a throttling error message. The user needs to wait for and then resubmit the execution of cmdlets on the open connection.
Copy Code | |
---|---|
New-ThrottlingPolicy -Name ITStaffUserPolicyCmdletMax -PowerShellMaxCmdlets 10 -PowerShellMaxCmdletsTimePeriod 5 |
EXAMPLE 5
This example creates a throttling policy that restricts a user to be able to only execute 10 destructive cmdlets in 60 seconds. If the users associated with this policy exceed this number, the cmdlet pipeline execution is stopped with a throttling error message. The user needs to wait for and then resubmit the execution of cmdlets on the open connection.
Copy Code | |
---|---|
New-ThrottlingPolicy -Name ITStaffUserPolicyDestructiveCmdlets -PowerShellMaxDestructiveCmdlets 10 -PowerShellMaxDestructiveCmdletsTimePeriod 60 |
Detailed Description
By default, there is one default throttling policy
named GlobalThrottlingPolicy_<GUID> with a throttling scope
of Global
. Microsoft Exchange Server 2013 Setup
creates a default client throttling policy when you install the
Exchange 2013 Client Access server role. You should not replace,
re-create, or remove the existing default throttling policy.
However, you can create additional throttling policies with the
scope of Organization or Regular to change your user throttling
settings. You can also edit policies with the scope of Organization
and Regular that you've created using the
Set-ThrottlingPolicy cmdlet.
For more information about how to control how resources are consumed by individual users, see Exchange Workload Management.
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "User throttling" entry in the Server Health and Performance Permissions topic.
Parameters
Parameter | Required | Type | Description | ||
---|---|---|---|---|---|
Name |
Required |
System.String |
The Name parameter specifies the name of the object in Active Directory. The default policy is named DefaultThrottlingPolicy<GUID>. |
||
AnonymousCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The AnonymousCutoffBalance parameter specifies the resource consumption limits for an anonymous user before the user is completely blocked from performing operations on a specific component. |
||
AnonymousMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The AnonymousMaxBurst parameter specifies the amount of time that an anonymous user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
AnonymousMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The AnonymousMaxConcurrency parameter specifies how many
anonymous connections can be made to a user's calendar data at the
same time. A connection is held from the moment a request is
received until a response is sent in its entirety to the requestor.
If anonymous users attempt to make more concurrent requests than
their policy allows, the new connection attempt fails. However, the
existing connections remain valid. The
AnonymousMaxConcurrency parameter has a valid range from 0
through 2147483647 inclusive. The default value is |
||
AnonymousRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The AnonymousRechargeRate parameter specifies the rate at which an anonymous user's budget is charged (budget grows by) during the budget time. |
||
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch. |
||
CpaCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The CpaCutoffBalance parameter specifies the resource consumption limits for a cross-premises user before that user is completely blocked from performing operations on a specific component. |
||
CpaMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The CpaMaxBurst parameter specifies the amount of time that a cross-premises user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
CpaMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The CpaMaxConcurrency parameter specifies how many
concurrent connections a cross-premises user can have against an
Exchange server at one time. A connection is held from the moment a
request is received until a response is sent in its entirety to the
requestor. If users attempt to make more concurrent requests than
their policy allows, the new connection attempt fails. However, the
existing connections remain valid. The CpaMaxConcurrency
parameter has a valid range from 0 through 2147483647 inclusive. To
indicate that the number of concurrent connections should be
unthrottled (no limit), this value should be set to
|
||
CpaRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The CpaRechargeRate parameter specifies the rate at which a cross premises user budget is charged (budget grows by) during the budget time. |
||
DiscoveryMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. |
||
DiscoveryMaxKeywords |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxKeywords parameter specifies the maximum number of keywords that a user can include in a discovery search. For more information, see Search-Mailbox. |
||
DiscoveryMaxKeywordsPerPage |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxKeywordsPerPage parameter specifies the number of keywords for which to show statistics on a single page in the Exchange Administration Center (EAC). |
||
DiscoveryMaxMailboxes |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxMailboxes parameter specifies the maximum number of source mailboxes that a user can include in a discovery search. |
||
DiscoveryMaxPreviewSearchMailboxes |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxPreviewSearchMailboxes parameter specifies the maximum number of mailboxes that a user can include in eDiscovery Search Preview. |
||
DiscoveryMaxRefinerResults |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter isn't used and will be removed. |
||
DiscoveryMaxSearchQueueDepth |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxSearchQueueDepth parameter specifies the maximum number of concurrent discovery search threads that can be active at the same time. |
||
DiscoveryMaxStatsSearchMailboxes |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryMaxStatsSearchMailboxes parameter specifies the maximum number of mailboxes that a user can search in an In-Place eDiscovery search without being able to view the statistics. When the number of mailboxes configured with the DiscoveryMaxStatsSearchMailboxes parameter is exceeded, the user must copy the search results to a discovery mailbox to view the statistics for the discovery search. For more information, see In-Place eDiscovery. |
||
DiscoveryPreviewSearchResultsPageSize |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoveryPreviewSearchResultsPageSize parameter specifies the number of messages displayed on a single page in eDiscovery Search Preview. |
||
DiscoverySearchTimeoutPeriod |
Optional |
Microsoft.Exchange.Data.Unlimited |
The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out. |
||
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory. |
||
EasCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasCutoffBalance parameter specifies the resource consumption limits for a Microsoft Exchange ActiveSync user before that user is completely blocked from performing operations on a specific component. |
||
EasMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasMaxBurst parameter specifies the amount of time that an Exchange ActiveSync user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
EasMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasMaxConcurrency parameter specifies how many
concurrent connections an Exchange ActiveSync user can have against
a server running Exchange 2013 at one time. A connection is held
from the moment a request is received until a response is sent in
its entirety to the requestor. If users attempt to make more
concurrent requests than their policy allows, the new connection
attempt fails. However, the existing connections remain valid. The
EasMaxConcurrency parameter has a valid range from 0 through
2147483647 inclusive. The default value is |
||
EasMaxDeviceDeletesPerMonth |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasMaxDeviceDeletesPerMonth parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can delete per month. By default, each user can delete a maximum of 20 partnerships per calendar month. When the limit is reached, the partnership deletion attempt fails and an error message is displayed to the user. |
||
EasMaxDevices |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasMaxDevices parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can have at one time. By default, each user can create 10 Exchange ActiveSync partnerships with their Exchange account. After users exceed the limit, they must delete one of their existing partnerships before they can create any more new partnerships. An email error message describing the limitation is sent to the user when the limit is exceeded. Additionally, an event is logged in the Application log when a user exceeds the limit. |
||
EasMaxInactivityForDeviceCleanup |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. |
||
EasRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EasRechargeRate parameter specifies the rate at which an Exchange ActiveSync user's budget is charged (budget grows by) during the budget time. |
||
EwsCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EwsCutoffBalance parameter specifies the resource consumption limits for an Exchange Web Services user before that user is completely blocked from performing operations on a specific component. |
||
EwsMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EwsMaxBurst parameter specifies the amount of time that an Exchange Web Services user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
EwsMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EwsMaxConcurrency parameter specifies how many
concurrent connections an Exchange Web Services user can have
against an Exchange server at one time. A connection is held from
the moment a request is received until a response is sent in its
entirety to the requestor. If users attempt to make more concurrent
requests than their policy allows, the new connection attempt
fails. However, the existing connections remain valid. The
EwsMaxConcurrency parameter has a valid range from 0 through
2147483647 inclusive. The default value is |
||
EwsMaxSubscriptions |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EwsMaxSubscriptions parameter specifies the maximum number of active push and pull subscriptions that an Exchange Web Services user can have on a specified Client Access server at the same time. If a user tries to create more subscriptions than the configured maximum, the subscription fails, and an event is logged in Event Viewer. |
||
EwsRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The EwsRechargeRate parameter specifies the rate at which an Exchange Web Services user's budget is charged (budget grows by) during the budget time. |
||
ExchangeMaxCmdlets |
Optional |
Microsoft.Exchange.Data.Unlimited |
The ExchangeMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is slowed down. The value specified by this parameter should be less than the value specified by the PowerShellMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. We recommend that you set values for both parameters at the same time. |
||
ForwardeeLimit |
Optional |
Microsoft.Exchange.Data.Unlimited |
The ForwardeeLimit parameter specifies the limits for the number of recipients that can be configured in Inbox Rules when using the forward or redirect action. This parameter doesn't limit the number of messages that can be forwarded or redirected to the recipients that are configured. |
||
IgnoreDehydratedFlag |
Optional |
System.Management.Automation.SwitchParameter |
This parameter is reserved for internal Microsoft use. |
||
ImapCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The ImapCutoffBalance parameter specifies the resource consumption limits for an IMAP user before that user is completely blocked from performing operations on a specific component. |
||
ImapMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The ImapMaxBurst parameter specifies the amount of time that an IMAP user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
ImapMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The ImapMaxConcurrency parameter specifies how many
concurrent connections an IMAP user can have against an Exchange
server at one time. A connection is held from the moment a request
is received until a response is sent in its entirety to the
requestor. If users attempt to make more concurrent requests than
their policy allows, the new connection attempt fails. However, the
existing connections remain valid. The ImapMaxConcurrency
parameter has a valid range from 0 through 2147483647 inclusive. To
indicate that the number of concurrent connections should be
unthrottled (no limit), this value should be set to
|
||
ImapRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The ImapRechargeRate parameter specifies the rate at which the IMAP user's budget is charged (budget grows by) during the budget time. |
||
IsServiceAccount |
Optional |
System.Management.Automation.SwitchParameter |
The IsServiceAccount switch specifies whether you want the user accounts associated with this policy to be moderated by the per-user thresholds specified by this policy, and also by additional throttling based on the health of system resources, such as overall CPU usage. This value is set to You may want to set this value to By setting the IsServiceAccount switch to
|
||
MessageRateLimit |
Optional |
Microsoft.Exchange.Data.Unlimited |
The MessageRateLimit parameter specifies the number of messages per minute that can be submitted to transport. For messages submitted through the Mailbox server role (using Microsoft Outlook, Microsoft Office Outlook Web App, Exchange ActiveSync, or Exchange Web Services), this results in the deferral of messages until the quota for the user is available. Specifically, messages appear in the Outbox or Drafts folder for longer periods of time when users submit messages at a rate greater than the MessageRateLimit parameter. For POP or IMAP clients submitting messages directly to transport using SMTP, clients receive a transient error if they submit at a rate that exceeds the MessageRateLimit parameter. Exchange attempts to connect and send the messages at a later time. |
||
Organization |
Optional |
Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter |
This parameter is reserved for internal Microsoft use. |
||
OwaCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaCutoffBalance parameter specifies the resource consumption limits for an Outlook Web App user before that user is completely blocked from performing operations on a specific component. |
||
OwaMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaMaxBurst parameter specifies the amount of time that an Outlook Web App user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
OwaMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaMaxConcurrency parameter specifies how many
concurrent connections an Outlook Web App user can have against an
Exchange server at one time. A connection is held from the moment a
request is received until a response is sent in its entirety to the
requestor. If users attempt to make more concurrent requests than
their policy allows, the new connection attempt fails. However, the
existing connections remain valid. The OwaMaxConcurrency
parameter has a valid range from 0 through 2147483647 inclusive.
The default value is |
||
OwaRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaRechargeRate parameter specifies the rate at which an Outlook Web App user's budget is charged (budget grows by) during the budget time. |
||
OwaVoiceCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaVoiceCutoffBalance parameter specifies the resource consumption limits for an Outlook Web App voice user before that user is completely blocked from performing operations on a specific component. |
||
OwaVoiceMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaVoiceMaxBurst parameter specifies the amount of time that an Outlook Web App voice user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
OwaVoiceMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaVoiceMaxConcurrency parameter specifies how many
concurrent connections an Outlook Web App voice user can have
against an Exchange server at one time. A connection is held from
the moment a request is received until a response is sent in its
entirety to the requestor. If users attempt to make more concurrent
requests than their policy allows, the new connection attempt
fails. However, the existing connections remain valid. The
OwaVoiceMaxConcurrency parameter has a valid range from 0
through 2147483647 inclusive. The default value is |
||
OwaVoiceRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The OwaVoiceRechargeRate parameter specifies the rate at which an Outlook Web App voice user's budget is charged (budget grows by) during the budget time. |
||
PopCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PopCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component. |
||
PopMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PopMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
PopMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PopMaxConcurrency parameter specifies how many
concurrent connections a POP user can have against an Exchange
server at one time. A connection is held from the moment a request
is received until a response is sent in its entirety to the
requestor. If users attempt to make more concurrent requests than
their policy allows, the new connection attempt fails. However, the
existing connections remain valid. The PopMaxConcurrency
parameter has a valid range from 0 through 2147483647 inclusive.
The default value is |
||
PopRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PopRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. |
||
PowerShellCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component. |
||
PowerShellMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
PowerShellMaxCmdletQueueDepth |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange Administration Center operations or Exchange Web Services operations. |
||
PowerShellMaxCmdlets |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is stopped. The value specified by this parameter should be more than the value specified by the ExchangeMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. Both values should be set at the same time. |
||
PowerShellMaxCmdletsTimePeriod |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine whether the number of cmdlets being executed exceeds the limits specified by the PowerShellMaxCmdlets and ExchangeMaxCmdlets parameters. |
||
PowerShellMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxConcurrency parameter specifies different information depending on context:
This parameter value doesn't necessarily correlate to the number of browsers opened by the user. |
||
PowerShellMaxDestructiveCmdlets |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive:
The time period used for this limit is specified by the PowerShellMaxDestructiveCmdletsTimePeriod parameter. Both values should be set at the same time. This feature isn't on by default. For more information, see the "Examples" section. |
||
PowerShellMaxDestructiveCmdletsTimePeriod |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxDestructiveCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many destructive cmdlets can be run. You set a value for this parameter when you set the PowerShellMaxDestructiveCmdlets parameter. Both values should be set at the same time. For more information, see the description for the PowerShellMaxDestructiveCmdlets parameter. |
||
PowerShellMaxOperations |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxOperations parameter specifies the
protocol-level operations that are used to send and receive data.
If the execution of a cmdlet results in a significant number of
operations (for example, if there is a lot of input/output
occurring), throttling may occur. The default setting is
|
||
PowerShellMaxRunspaces |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxRunspaces parameter specifies the number
of concurrent Windows PowerShell sessions that a user is allowed to
have. The default setting is |
||
PowerShellMaxRunspacesTimePeriod |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxRunspacesTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many Windows PowerShell sessions can be run. You set this value when you set the PowerShellMaxRunspaces parameter. |
||
PowerShellMaxTenantConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxTenantConcurrency parameter limits the
number of concurrent Windows PowerShell connections per tenant
organization. By default, the limit for concurrent Windows
PowerShell connections per tenant organization is set to
|
||
PowerShellMaxTenantRunspaces |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellMaxTenantRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a tenant is allowed to have. |
||
PowerShellRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PowerShellRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. |
||
PswsMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PswsMaxConcurrency parameter specifies how many concurrent connections a Windows PowerShell Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PswsMaxConcurrency parameter has a default value of
|
||
PswsMaxRequest |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PswsMaxRequest parameter specifies how many requests
a Windows PowerShell Web Services user can have against an Exchange
server at one time. The default setting is
|
||
PswsMaxRequestTimePeriod |
Optional |
Microsoft.Exchange.Data.Unlimited |
The PswsMaxRequestTimePeriod parameter specifies the
period of time, in seconds, that the throttling policy uses to
determine how many requests can be run. The default setting is
|
||
PushNotificationCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
PushNotificationMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
PushNotificationMaxBurstPerDevice |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
PushNotificationMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
PushNotificationRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
PushNotificationRechargeRatePerDevice |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
PushNotificationSamplingPeriodPerDevice |
Optional |
Microsoft.Exchange.Data.Unlimited |
This parameter is reserved for internal Microsoft use. |
||
RcaCutoffBalance |
Optional |
Microsoft.Exchange.Data.Unlimited |
The RcaCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component. |
||
RcaMaxBurst |
Optional |
Microsoft.Exchange.Data.Unlimited |
The RcaMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. |
||
RcaMaxConcurrency |
Optional |
Microsoft.Exchange.Data.Unlimited |
The RcaMaxConcurrency parameter specifies how many
concurrent connections an RPC Client Access user can have against a
server running Exchange 2013 at one time. A connection is held from
the moment a request is received until the connection is closed or
the connection is otherwise disconnected (for example, if the user
goes offline). If users attempt to make more concurrent requests
than their policy allows, the new connection attempt fails.
However, the existing connections remain valid. The
RcaMaxConcurrency parameter has a valid range from 0 through
2147483647 inclusive. The default value is |
||
RcaRechargeRate |
Optional |
Microsoft.Exchange.Data.Unlimited |
The RcaRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. |
||
RecipientRateLimit |
Optional |
Microsoft.Exchange.Data.Unlimited |
The RecipientRateLimit parameter specifies the limits on the number of recipients that a user can address in a 24-hour period. |
||
ThrottlingPolicyScope |
Optional |
Microsoft.Exchange.Data.Directory.SystemConfiguration.ThrottlingPolicyScopeType |
The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values.
For more information about throttling policy scopes, see Exchange Workload Management. |
||
WhatIf |
Optional |
System.Management.Automation.SwitchParameter |
The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch. |
Input Types
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.
Return Types
To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.