EXAMPLE 1

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.

	Copy Code
Remove-CsMeetingConfiguration -Identity site:Redmond

EXAMPLE 2

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 the Get-CsMeetingConfiguration cmdlet 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.

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

EXAMPLE 3

Example 3 deletes each collection of meeting configuration settings where the AdmitAnonymousUsersbyDefault property is True. To carry out this task, the command first calls the Get-CsMeetingConfiguration cmdlet in order to return a collection of all the meeting configuration settings currently in use. This collection is then piped to the Where-Object cmdddlet, which picks out only those settings where the AdmitAnonymousUsersByDefault property is equal to True. The filtered collection is then piped to the Remove-CsMeetingConfiguration cmdlllet, which proceeds to remove each item in that collection.

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

Online meetings (also called conferences) are an integral part of Lync 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, you can configure meetings so that anyone dialing in over the public switched telephone network (PSTN) is automatically admitted to the meeting. Alternatively, you can configure meetings so that dial-in users are not automatically admitted the meeting, but are instead routed to the meeting lobby. These dial-in users remain on hold in the lobby until a presenter admits them to the meeting.

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. The Remove-CsMeetingConfiguration cmdlet 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.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Remove-CsMeetingConfiguration 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-CsMeetingConfiguration"}

Microsoft.Rtc.Management.WritableConfig.Settings.UserServices.MeetingConfiguration object. The Remove-CsMeetingConfiguration cmdlet accepts pipelined instances of the meeting configuration object.

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