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

Get-CsMeetingConfiguration enables you to return information about 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


Get-CsMeetingConfiguration [-Identity <XdsIdentity>] [-LocalStore <SwitchParameter>] [-Tenant <Nullable>]


Get-CsMeetingConfiguration [-Filter <String>] [-LocalStore <SwitchParameter>] [-Tenant <Nullable>]

Parameters

Parameter	Required	Type	Description
Identity	Optional	Xds identity	Indicates the unique identifier for the collection of meeting configuration settings you want to return. 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 retrieved using syntax like this: -Identity service:UserServer:atl-cs-001.litwareinc.com. If this parameter is not specified then Get-CsMeetingConfiguration will return a collection of all the meeting settings in use in the organization. Note that you cannot use wildcards when specifying an Identity. If you need to use wildcards then include the -Filter parameter instead.
Filter	Optional	String	Enables you to use wildcard characters in order to return a collection (or multiple collections) of meeting configuration settings. To return a collection of all the settings configured at the site scope, use this syntax: -Filter site:. To return a collection of all the settings that have the string value "EMEA" somewhere in their Identity (the only property you can filter on) use this syntax: -Filter EMEA*.
Tenant	Optional	Guid
LocalStore	Optional	Switch Parameter

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.

Get-CsMeetingConfiguration enables you to return information about any, or all, of the meeting configuration setting collections currently in use in your organization.

Return Types

Get-CsMeetingConfiguration returns instances of the Microsoft.Rtc.Management.WritableConfig.Settings.UserServices.MeetingConfiguration object.

Examples

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

	Copy Code
Get-CsMeetingConfiguration

The command shown in Example 1 returns a collection of all the meeting configuration settings currently in use in the organization.

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

	Copy Code
Get-CsMeetingConfiguration -Identity site:Redmond

In Example 2, only one collection of meeting configuration settings is returned: the settings that have the Identity site:Redmond. By definition, these are settings that have been applied to the Redmond site.

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

	Copy Code
Get-CsMeetingConfiguration -Filter "service:*"

The preceding command returns all the meeting configuration settings that have been configured at the service scope. This is done by including the -Filter parameter and the filter value "service:*", which limits returned data to settings where the Identity property begins with the characters "service:".

-------------------------- Example 4 ------------------------

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

In Example 4, information is returned for meeting configuration settings where anonymous users are admitted by default. To accomplish this task, the command first uses Get-CsMeetingConfiguration (without any parameters) to return a collection of all the meeting configuration settings currently in use. That collection is then piped to the Where-Object cmdlet, which selects only those settings where the AdmitAnonymousByDefault property is equal to (-eq) True ($True).