Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Related Help Topics
No resources found.
Related Blog Articles
No resources found.
Expand Minimize


Exchange 2010

Applies to: Exchange Server 2010 SP2, Exchange Server 2010 SP3

Topic Last Modified: 2015-03-09

Use the Remove-ThrottlingPolicy cmdlet to remove a non-default Microsoft Exchange throttling policy.

Remove-ThrottlingPolicy -Identity <ThrottlingPolicyIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

You can't remove the default client throttling policy. Also, you can't remove a policy that’s associated with any users. For more information, see "EXAMPLE 2" later in this topic.

For more information about client throttling, see Understanding Client Throttling Policies. For more information about managing performance by using client throttling policies, see Managing Performance with Client Throttling Policies.

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 "Client throttling settings" entry in the Client Access Permissions topic.


Parameter Required Type Description




The Identity parameter identifies the throttling policy you want to remove. Use the name that matches the name of the policy in Active Directory.




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.




The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.




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.

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.

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.

This example removes the client throttling policy ClientThrottlingPolicy2.

Remove-ThrottlingPolicy -Identity ClientThrottlingPolicy2

You can't remove a policy that's associated with any users. This example reassigns the users subject to ClientThrottlingPolicy2 to the default policy. Then, it removes ClientThrottlingPolicy2.

$policy = Get-ThrottlingPolicy ClientThrottlingPolicy2;
$mailboxes = Get-Mailbox | where-object {$_.ThrottlingPolicy -eq $policy.Identity};
$defaultPolicy = Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true};
foreach ($mailbox in $mailboxes)
  set-mailbox -Identity $mailbox.Identity -ThrottlingPolicy $defaultPolicy;
Remove-ThrottlingPolicy ClientThrottlingPolicy2;
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft