Set-CsMeetingConfiguration enables you to modify the meeting configuration settings currently in use in your organization. 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
Set-CsMeetingConfiguration [-Identity <XdsIdentity>] [-AdmitAnonymousUsersByDefault <$true | $false>] [-AssignedConferenceTypeByDefault <$true | $false>] [-Confirm [<SwitchParameter>]] [-DesignateAsPresenter <None | Company | Everyone>] [-EnableAssignedConferenceType <$true | $false>] [-Force <SwitchParameter>] [-PstnCallersBypassLobby <$true | $false>] [-Tenant <Nullable>] [-WhatIf [<SwitchParameter>]] |
Set-CsMeetingConfiguration [-AdmitAnonymousUsersByDefault <$true | $false>] [-AssignedConferenceTypeByDefault <$true | $false>] [-Confirm [<SwitchParameter>]] [-DesignateAsPresenter <None | Company | Everyone>] [-EnableAssignedConferenceType <$true | $false>] [-Force <SwitchParameter>] [-Instance <PSObject>] [-PstnCallersBypassLobby <$true | $false>] [-Tenant <Nullable>] [-WhatIf [<SwitchParameter>]] |
Parameters
Parameter | Required | Type | Description |
---|---|---|---|
Identity |
Optional |
Xds identity |
Indicates the unique identifier for the collection of meeting configuration settings you want to modify. To refer to the global settings use this syntax: -Identity global. To refer to a collection configured at the site scope, use syntax similar to this: -Identity site:Redmond. Settings configured at the service scope can be referenced using syntax like this: -identity service:UserServer:atl-cs-001.litwareinc.com. If this parameter is not specified then Set-CsMeetingConfiguration will modify the global settings. |
Instance |
Optional |
MeetingConfiguration object |
Allows you to pass a reference to an object to the cmdlet rather than set individual parameter values. |
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. |
EnableAssignedConferenceType |
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. The default value is True. |
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. |
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 Set-CsMeetingConfiguration cmdlet enables you to modify any of the meeting configuration collections currently in use in your organization.
Return Types
Set-CsMeetingConfiguration does not return any objects or values. Instead, the cmdlet modifies existing instances of the Microsoft.Rtc.Management.WritableConfig.Settings.UserServices.MeetingConfiguration object.
Examples
-------------------------- Example 1 ------------------------
Copy Code | |
---|---|
Set-CsMeetingConfiguration -Identity site:Redmond -DesignateAsPresenter Everyone |
The command shown in Example 1 modifies the meeting configuration settings assigned to the Redmond site (-Identity site:Redmond). In this case, the value of the DesignateAsPresenter property is set to Everyone.
-------------------------- Example 2 ------------------------
Copy Code | |
---|---|
Get-CsMeetingConfiguration | Set-CsMeetingConfiguration -DesignateAsPresenter Everyone |
The command shown in Example 2 is a variation of the command shown in Example 1. In this case, however, the value of the DesignateAsPresenter property is modified for all the meeting configuration settings in use in the organization. To do this, Get-CsMeetingConfiguration is called without any parameters; that returns a collection of all the meeting configuration settings currently in use. This collection is then piped to Set-CsMeetingConfiguration, which modifies the DesignateAsPresenter property for each item in the collection.
-------------------------- Example 3 ------------------------
Copy Code | |
---|---|
Get-CsMeetingConfiguration | Where-Object {$_.AdmitAnonymousUsersByDefault -eq $False} | Set-CsMeetingConfiguration -PstnCallersBypassLobby $True |
In Example 4, all the meeting configurations that do not allow the default admission of anonymous users are modified. To perform this task, the command first calls Get-CsMeetingConfiguration to return a collection of all the meeting configuration settings currently in use. This collection is then piped to the Where-Object cmdlet, which picks out only those settings where the AdmitAnonymousUsersByDefault property is equal to (-eq) False ($False). In turn, this filtered collection is piped to Set-CsMeetingConfiguration, which takes each item in the collection and sets the PstnCallersBypassLobby property to True ($True).