Remove-CsMeetingConfiguration -Identity <XdsIdentity> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Tenant <Nullable>] [-WhatIf [<SwitchParameter>]]

Parameters

Online meetings are an integral part of Microsoft Communications Server. The CsMeetingConfiguration cmdlets enable administrators to control the type of meetings that users can create as well as determine how meetings deal with anonymous users and dial-in conferencing users. For example, both New-CsMeetingConfiguration and Set-CsMeetingConfiguration allow administrators to give users the option of creating public meetings. Public meetings are designed for in-house and impromptu get-togethers: public meetings include no designated start or end times, and organizers do not have to specify attendee lists or set up access permissions. By definition, any user within the organization can participate in a public meeting; however, anonymous users (that is, unauthenticated users) are not allowed to attend public meetings.

Alternatively, administrators can disable the ability of their users to create public meetings. In that case, all meetings will be private meetings: meetings with specified start and end times; meetings that require an attendee list; and meetings that require organizers to assign access permissions. Private meetings give users full control over their get-togethers and who can attend them; conversely, private meetings also require more effort to schedule and to manage.

Meeting configuration settings can be assigned to the global, site, or service scopes. If you create new settings at the site or service scope those settings can later be removed by using the Remove-CsMeetingConfiguration cmdlet. Remove-CsMeetingConfiguration can also be run against the global meeting settings. In that case, however, the settings will not be removed; that’s because the global settings cannot be removed. Instead, all the properties in the global collection will be reset to their default values.

Remove-CsMeetingConfiguration deletes existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.UserServices.MeetingConfiguration object.

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

	Copy Code
Remove-CsMeetingConfiguration -Identity site:Redmond

In Example 1, the meeting configuration settings that have the Identity site:Redmond are removed. When these settings are removed from the Redmond site, users in that site will automatically inherit the global meeting configuration settings.

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

	Copy Code
Get-CsMeetingConfiguration -Filter "site:*" | Remove-CsMeetingConfiguration

The command shown in Example 2 removes all the meeting settings that have been configured at the site scope. To do this, the command first calls Get-CsMeetingConfiguration along with the -Filter parameter; the filter value "site:*" ensures that only settings that have an Identity that begins with the characters "site:" are selected. This filtered collection is then piped to the Remove-CsMeetingConfiguration cmdlet, which deletes each item in the collection.

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

	Copy Code
Get-CsMeetingConfiguration | Where-Object {$_.AdmitAnonymousUsersByDefault -eq $True} | Remove-CsMeetingConfiguration

The preceding command deletes each collection of meeting configuration settings where the AdmitAnonymousUsersbyDefault property is True. To carry out this task, the command first calls Get-CsMeetingConfiguration, which returns a collection of all the meeting configuration settings currently in use. This collection is then piped to Where-Object, which picks out only those settings where the AdmitAnonymousUsersByDefault property is equal to (-eq) True ($True). The filtered collection is then piped to Remove-CsMeetingConfiguration, which proceeds to remove each item in that filtered collection.