Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Expand Minimize



Topic Last Modified: 2015-03-09

Removes an existing bandwidth policy service configuration. This cmdlet was introduced in Lync Server 2010.

Remove-CsBandwidthPolicyServiceConfiguration -Identity <XdsIdentity> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

This example removes the bandwidth policy service configuration defined for the Redmond site (-Identity site:Redmond).

Remove-CsBandwidthPolicyServiceConfiguration -Identity site:Redmond

Example 2 removes all bandwidth policy service configurations where logging is disabled. To accomplish this, the example begins with a call to the Get-CsBandwidthPolicyServiceConfiguration cmdlet. This will return a collection of all bandwidth policy service configurations in the Skype for Business Server 2015 deployment. This collection is then piped to the Where-Object cmdlet, which narrows the collection down to only those configurations where the EnableLogging property is equal to (-eq) False ($False). This leaves a collection of configurations that have logging disabled. This collection is then piped to the Remove-CsBandwidthPolicyServiceConfiguration cmdlet, which removes every item in the collection.

Get-CsBandwidthPolicyServiceConfiguration | Where-Object {$_.EnableLogging -eq $False} | Remove-CsBandwidthPolicyServiceConfiguration

Call admission control (CAC) is a way of determining whether to allow real-time communications sessions, such as voice or video calls, to be established based on bandwidth constraints. Within the Skype for Business Server 2015 implementation of CAC, regions, sites, and subnets are defined within a network along with the relationships and links between those entities in order to place bandwidth constraints between them. Bandwidth Policy service is the component that performs CAC functionality in the Skype for Business Server 2015 deployment, enabling the decision as to whether sufficient bandwidth exists for a call to be established. This cmdlet removes a bandwidth policy service configuration defined at the site level. You can also use the cmdlet to “remove” the global bandwidth policy service; however, the global service will not actually be removed, it will simply be reset to its default values.


Parameter Required Type Description




The unique identifier of the configuration you want to remove. This identifier will consist of the scope (for the global configuration) or the scope and name (for a site-level configuration, such as site:Redmond).




Prompts you for confirmation before executing the command.




Suppresses any confirmation prompts that would otherwise be displayed before making changes.




Describes what would happen if you executed the command without actually executing the command.

Microsoft.Rtc.Management.WritableConfig.Settings.BandwidthPolicyServiceConfiguration.BandwidthPolicyServiceConfiguration object. Accepts pipelined input of bandwidth policy service configuration objects.

This cmdlet does not return a value. It removes an object of type Microsoft.Rtc.Management.WritableConfig.Settings.BandwidthPolicyServiceConfiguration.BandwidthPolicyServiceConfiguration.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft