[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

New-CsMeetingConfiguration enables you to create a new collection of meeting configuration settings at the site or service scope. Meeting configuration settings help dictate the type of meetings that users can create as well as control how (or even if) anonymous users and dial-in conferencing users can join these meetings.

Syntax


New-CsMeetingConfiguration -Identity <XdsIdentity> [-AdmitAnonymousUsersByDefault <$true \| $false>] [-AssignedConferenceTypeByDefault <$true \| $false>] [-Confirm [<SwitchParameter>]] [-DesignateAsPresenter <None \| Company \| Everyone>] [-EnableAssignedConferenceType <$true \| $false>] [-Force <SwitchParameter>] [-InMemory <SwitchParameter>] [-PstnCallersBypassLobby <$true \| $false>] [-Tenant <Nullable>] [-WhatIf [<SwitchParameter>]]

New-CsMeetingConfiguration -Identity <XdsIdentity> [-AdmitAnonymousUsersByDefault <$true | $false>] [-AssignedConferenceTypeByDefault <$true | $false>] [-Confirm [<SwitchParameter>]] [-DesignateAsPresenter <None | Company | Everyone>] [-EnableAssignedConferenceType <$true | $false>] [-Force <SwitchParameter>] [-InMemory <SwitchParameter>] [-PstnCallersBypassLobby <$true | $false>] [-Tenant <Nullable>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter	Required	Type	Description
Identity	Required	Xds Identity	Unique identifier for the new collection of meeting configuration settings. Meeting configuration settings can only be created at the site or service scope. To create new settings at the site scope, use syntax similar to this: -Identity site:Redmond (where "Redmond" is the name of the site). To create new settings at the service scope, use syntax like this: -Identity service:UserServer:atl-cs-001.litwareinc.com. Note that the call to New-CsMeetingConfiguration will fail if the specified site or service already has a collection of meeting configuration settings.
PstnCallersBypassLobby	Optional	Boolean	Indicates whether users dialing in over a PSTN (Public Switched Telephone Network) phone line should automatically be admitted to a meeting. If set to True ($True) PSTN callers will automatically be admitted to the meeting. If set to False ($False) then PSTN callers will initially be routed to the conference lobby. At that point, they will have to wait, on hold, until a conference presenter grants them access to the meeting. The default value is True.
EnablAssignedConferenceType	Optional	Boolean	Indicates whether users are allowed to schedule public meetings. Public meetings are in-house, ad-hoc get-togethers that users can schedule without having to identify participants, set access permissions, or configure PSTN dial-in settings.
DesignateAsPresenter	Optional	PS List Modifier	Indicates which users (outside the meeting organizer) can be designated as presenters. Valid choices are: None; Company; and Everyone. By default, DesignateAsPresenter is set to Company, meaning anyone within your organization can be promoted to presenter.
AssignedConferenceTypeByDefault	Optional	Boolean	Determines whether new meetings will be configured, by default, as public meetings. Set this value to True ($True) to use public meetings by default; set this value to False ($False) to use private meetings by default. The default value is True.
AdmitAnonymousUsersByDefault	Optional	Boolean	Determines whether meetings will, by default, allow attendance by anonymous users (that is, unauthenticated users). Set this value to True ($True) if you would like new meetings to, by default, allow for attendance by anonymous users. Set this value to False ($False) if you would prefer that, by default, new meetings do not allow for attendance by anonymous users. The default value is True.
InMemory	Optional	Switch Parameter	Creates an object reference without actually committing the object as a permanent change. If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet’s matching Set- cmdlet.
Tenant	Optional	Guid
Force	Optional	Switch Parameter	Suppresses the display of any non-fatal error message that might arise when running the command.
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.

Detailed Description

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.

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 Server service). Meeting settings cannot be created at the global scope; that’s 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.

Return Types

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

Examples

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

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

The preceding command creates a new collection of meeting configuration settings for 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 ($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, at most, only one collection of meeting configuration settings can be applied to a given site.

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

	Copy Code
$x = New-CsMeetingConfiguration -Identity site:Redmond -InMemory $x.EnableAssignedConferenceType = $False $x.AssignedConferenceTypeByDefault = $False $x.AdmitAnonymousUsersByDefault = $False Set-CsMeetingConfiguration -Instance $x

Copy Code

$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 New-CsMeetingConfiguration to create new meeting settings for the Redmond site; the -InMemory parameter is tacked on 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, that’s a variable named $x.)

After the virtual meeting settings have been created, commands 2, 3, and 4 are used to modify various properties of those settings (EnableAssignedConferenceType; AssignedConferenceTypeByDefault; and AndmitAnonymousUsersByDefault). In the final command, Set-CsMeetingConfiguration 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 Set-CsMeetingConfiguration the new meeting configuration settings will never be applied to the Redmond site. Instead, your virtual settings will disappear as soon as you terminate your Windows PowerShell session or delete the variable $x.