New-CsMeetingConfiguration

Syntax

New-CsMeetingConfiguration
   [-Identity] <XdsIdentity>
   [-AdmitAnonymousUsersByDefault <Boolean>]
   [-AssignedConferenceTypeByDefault <Boolean>]
   [-DesignateAsPresenter <DesignateAsPresenter>]
   [-EnableAssignedConferenceType <Boolean>]
   [-PstnCallersBypassLobby <Boolean>]
   [-Force]
   [-InMemory]
   [-Tenant <Guid>]
   [-WhatIf]
   [-Confirm]
   [-CustomFooterText <String>]
   [-HelpURL <String>]
   [-LegalURL <String>]
   [-LogoURL <String>]
   [-RequireRoomSystemsAuthorization <Boolean>]
   [<CommonParameters>]

Description

Meetings (also called "conferences") are an integral part of Skype for Business Server. The CsMeetingConfiguration cmdlets enable administrators to control the type of meetings that users can create and to 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.

As noted previously, these settings only affect scheduled meetings; they do not affect ad-hoc meetings created by clicking Meet Now in Microsoft Lync. When you create a meeting by clicking Meet Now, participant access is automatically open to all everyone, and anonymous users can join the meeting without having to wait in the lobby. This will occur regardless of how you have configured your meeting settings using the CsMeetingConfiguration cmdlets.

The New-CsMeetingConfiguration cmdlet enables you to create new meeting configuration collections at either the site or the service scope (albeit only for the User Services). Meeting settings cannot be created at the global scope because there is already a global collection of meeting settings.

Note that each site or service can only have, at most, one collection of meeting configuration settings. If you try to create new settings for the Redmond site, and the Redmond site already has a collection of meeting configuration settings, then your command will fail.

Examples

-------------------------- EXAMPLE 1 --------------------------

New-CsMeetingConfiguration -Identity site:Redmond -EnableAssignedConferenceType $False -AssignedConferenceTypeByDefault $False -AdmitAnonymousUsersByDefault $False

Example 1 creates a new collection of meeting configuration settings for the Redmond site (-Identity site:Redmond). In addition to specifying the Identity, three optional parameters are included in this command: EnableAssignedConferenceType, AssignedConferenceTypeByDefault, and AdmitAnonymousUsersByDefault. In all three cases, these parameters are set to False. That means that public meeting types will be disabled; the default meeting type will not be set to public meeting; and anonymous users will not be admitted to meetings by default.

Note that this command will fail if a collection of meeting configuration settings with the Identity site:Redmond already exists. That's because only one collection of meeting configuration settings can be applied to a given site.

-------------------------- EXAMPLE 2 --------------------------

$x = New-CsMeetingConfiguration -Identity site:Redmond -InMemory

$x.EnableAssignedConferenceType = $False

$x.AssignedConferenceTypeByDefault = $False

$x.AdmitAnonymousUsersByDefault = $False

Set-CsMeetingConfiguration -Instance $x

Example 2 shows an alternate way to create a new collection of meeting configuration settings for the Redmond site; in this case, the settings are initially created in memory only, and are only later applied to the site. To do this, the first command in the example uses the New-CsMeetingConfiguration cmdlet to create new meeting settings for the Redmond site. The InMemory parameter is added to the end of the command to ensure that these new settings are created in memory only, and are not immediately applied to the Redmond site. (Because these settings exist only in memory, they must be stored in a variable. In this example, they are stored in a variable named $x.)

After these virtual meeting settings have been created, commands 2, 3, and 4 are used to modify properties of those settings (EnableAssignedConferenceType, AssignedConferenceTypeByDefault, and AdmitAnonymousUsersByDefault). In the final command, the Set-CsMeetingConfiguration cmdlet and the Instance parameter are used to actually apply the virtual settings to the Redmond site. Note that this final step is crucial: if you do not call the Set-CsMeetingConfiguration cmdlet, the new meeting configuration settings will never be applied to the Redmond site. Instead, your virtual settings will disappear as soon as you end your Windows PowerShell session or delete the variable $x.

Parameters

-AdmitAnonymousUsersByDefault

-AssignedConferenceTypeByDefault

-Confirm

-CustomFooterText

-DesignateAsPresenter

-EnableAssignedConferenceType

-Force

-HelpURL

-Identity

-InMemory

-LegalURL

-LogoURL

-PstnCallersBypassLobby

-RequireRoomSystemsAuthorization

-Tenant

-WhatIf

Inputs

None. The New-CsMeetingConfiguration cmdlet does not accept pipelined data.

Outputs

The New-CsMeetingConfiguration cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Settings.UserServices.MeetingConfiguration object.

Related Links

• Get-CsMeetingConfiguration
• Remove-CsMeetingConfiguration
• Set-CsMeetingConfiguration