Article
07/23/2014

Remove-CsConferencingPolicy

Topic Last Modified: 2012-03-26

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.

Syntax

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

Detailed Description

Conferencing is an important part of Microsoft Lync Server 2010: 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 Lync Server 2010, 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 global scope; at the site scope; or 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 to delete any of the conferencing policies configured for use in your organization, with one exception: you cannot delete the global policy. You can still run Remove-CsConferencingPolicy against the global policy. In that case, however the policy will not be removed; instead, all the global policy properties will be reset to their default values.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Remove-CsConferencingPolicy cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Remove-CsConferencingPolicy"}

Parameters

Parameter	Required	Type	Description
Identity	Required	XdsIdentity	Unique identifier for the conferencing policy to be removed. Conferencing policies can be configured at the global, site, or per-user scopes. To remove the global policy, use this syntax: -Identity global. (Note that the global policy cannot actually be removed. Instead, all the policy properties will be reset to their default values.) To remove a site policy, use syntax similar to this: -Identity site:Redmond. To remove a per-user policy, use syntax similar to this: -Identity SalesConferencingPolicy. Wildcards are not allowed when specifying an Identity.
Force	Optional	Switch Parameter	If present, causes Remove-CsConferencingPolicy 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.
WhatIf	Optional	Switch Parameter	Describes what would happen if you executed the command without actually executing the command.
Confirm	Optional	Switch Parameter	Prompts you for confirmation before executing the command.

Input Types

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

Return Types

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

Example

-------------------------- Example 1 --------------------------

Remove-CsConferencingPolicy -Identity SalesConferencingPolicy

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

-------------------------- Example 2 --------------------------

Get-CsConferencingPolicy -Filter "site:*" | Remove-CsConferencingPolicy

In the preceding example, all the conferencing policies that have been configured at the site scope are deleted. To accomplish this task, the command first uses Get-CsConferencingPolicy and the Filter parameter to return a collection of all the site-level policies; the filter value "site:*" ensures that only policies that have an Identity that begins with the string value "site" are returned. That filtered collection is then piped to Remove-CsConferencingPolicy, which deletes each item in the collection.

-------------------------- Example 3 --------------------------

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

In Example 3, all the policies that allow a maximum meeting size (MaxMeetingSize) of more than 100 people are deleted. To do this, the command first uses Get-CsConferencingPolicy 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 Remove-CsConferencingPolicy, which deletes all the policies in the filtered collection.

Share via