Remove-CsConferencingPolicy

 

Topic Last Modified: 2017-05-17

ImportantImportant:
This only applies to Skype for Business Online and not to Skype for Business Server or Lync on-premises deployments.
NoteNote:
Please note that if your organization utilizes custom policies, then the UI will no longer correctly reflect the policy values. Once they are implemented they must continue to be managed via PowerShell.

Removes the specified conferencing policy. Conferencing policies determine the features and capabilities that can be used in a conference; this includes everything from whether or not the conference can include IP audio and video to the maximum number of people who can attend a meeting.

Remove-CsConferencingPolicy -Identity <XdsIdentity> [-BypassDualWrite <$true | $false>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Tenant <Guid>] [-WhatIf [<SwitchParameter>]]

In Example 1, the Remove-CsConferencingPolicy cmdlet is used to delete the conferencing policy with the Identity SalesConferencingPolicy.

Remove-CsConferencingPolicy -Identity SalesConferencingPolicy

In Example 2, all the policies that allow a maximum meeting size (MaxMeetingSize) of more than 100 people are deleted. To do this, the command first uses the Get-CsConferencingPolicy cmdlet to retrieve a collection of all the conferencing policies configured for use in the organization. That collection is then piped to the Where-Object cmdlet, which applies a filter that limits the returned data to those policies where the MaxMeetingSize value is greater than 100. Finally, that filtered collection is passed to the Remove-CsConferencingPolicy cmdlet, which deletes all the policies in the filtered collection.

Get-CsConferencingPolicy | Where-Object {$_.MaxMeetingSize -gt 100} | Remove-CsConferencingPolicy 

Conferencing is an important part of Skype for Business Online: conferencing enables groups of users to come together online to view slides and video, share applications, exchange files, and otherwise communicate and collaborate.

It’s important for administrators to maintain control over conferences and conference settings. In some cases, there might be security concerns: by default, anyone, including unauthenticated users, can participate in meetings and save any of the slides or handouts distributed during those meetings. In other cases, there might be bandwidth concerns: having a multitude of simultaneous meetings, each involving hundreds of participants and each featuring video feeds and file sharing, has the potential to cause problems with your network. In addition, there might be legal concerns. For example, by default meeting participants are allowed to make annotations on shared content; however, these annotations are not saved when the meeting is archived. If your organization is required to keep a record of all electronic communication, you might want to disable annotations.

Of course, needing to manage conferencing settings is one thing; actually managing these settings is another. In Skype for Business Online, conferences are managed by using conferencing policies. (In previous versions of the software, these were known as meeting policies.) As noted, conferencing policies determine the features and capabilities that can be used in a conference, including everything from whether or not the conference can include IP audio and video to the maximum number of people who can attend a meeting. Conferencing policies can be configured at the per-user scope. This provides administrators with enormous flexibility when it comes to deciding which capabilities will be made available to which users.

You can use the Remove-CsConferencingPolicy cmdlet to delete any of the conferencing policies configured for use in your organization.

 

Parameter Required Type Description

Identity

Required

Microsoft.Rtc.Management.Xds.XdsIdentity

Unique identifier for the conferencing policy to be removed. Conferencing policies can be configured at the per-user scopes. To remove a per-user policy, use syntax similar to this: -Identity SalesConferencingPolicy.

NoteNote:
Wildcards are not allowed when specifying an Identity.

BypassDualWrite

Optional

System.Boolean

PARAMVALUE: $true | $false

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.

Force

Optional

System.Management.Automation.SwitchParameter

If present, causes the Remove-CsConferencingPolicy cmdlet to delete the per-user policy even if the policy in question is currently assigned to at least one user. If not present, you will be asked to confirm the deletion request before the policy will be removed.

Tenant

Optional

System.Guid

PARAMVALUE: Guid

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.

Microsoft.Rtc.Management.WritableConfig.Policy.Meeting.MeetingPolicy object. The Remove-CsConferencingPolicy cmdlet accepts pipelined instances of the meeting policy object.

The Remove-CsConferencingPolicy cmdlet does not return a value or object. Instead, the cmdlet deletes instances of the Microsoft.Rtc.Management.WritableConfig.Policy.Meeting.MeetingPolicy object.

 
Show: