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

Returns information about Web conference configuration for your organization. Web conference settings determine such things as the maximum-allowed size for meeting content and handouts; the content grace period (that is, the amount of time content will be stored before being deleted); and the URLs for the internal and external downloads of the meeting client.

Syntax

Get-CsConferencingConfiguration [-Identity <XdsIdentity>] [-LocalStore <SwitchParameter>]
Get-CsConferencingConfiguration [-Filter <String>] [-LocalStore <SwitchParameter>]

Parameters

Parameter Required Type Description

Identity

Optional

Xds Identity

Unique identifier for the collection of conferencing configuration settings to be retrieved. To retrieve the global settings, use this syntax: -Identity global. To retrieve settings configured at the site scope, use syntax similar to this: -Identity "site:Redmond". To retrieve settings configured at the service scope, use syntax similar to this: -Identity "service:ConferencingServer:atl-cs-001.litwareinc.com".

If this parameter is not included then Get-CsConferencingConfiguration will return all the conferencing configuration settings currently in use in your organization.

Filter

Optional

String

Enables you to use wildcards when specifying the Identity of the conferencing configuration settings collection (or collections) to be returned. For example, this syntax returns all the settings configured at the site scope: -Filter "site:*". This syntax returns all the settings configured at the service scope: -Filter "service:*".

Note that you cannot use both the –Identity and the –Filter parameters in the same command. Instead you must use either –Identity or –Filter (or leave off both parameters altogether).

LocalStore

Optional

Switch Parameter

Detailed Description

When it comes to Web conferences management and administration is split between two sets of cmdlets. If you want to dictate the things that users can and cannot do (for example, can users invite anonymous participants to join a conference; are users allowed to offer application sharing and/or file transfers within a conference; etc.) then you need to use the CsConferencingPolicy cmdlets. But that’s only one piece of the puzzle. The other piece: the need to manage Web conferencing servers and server settings. For example, administrators need to be able to do such things as specify the maximum amount of content storage allotted to a single meeting and to specify the grace period before that meeting content is automatically deleted. They also need to be able to specify the ports used for activities such as application sharing and file transfer.

The CsConferencingConfiguration cmdlets represent the missing piece to the Web conferencing management puzzle. These cmdlets enable you to manage the actual severs themselves. The CsConferencingConfiguration cmdlets (which can be applied to the global, the site, and the service scopes) aren’t used to specify whether or not a user can share applications during a conference; if application sharing is allowed, however, these cmdlets let you indicate which ports should be used for that activity. Likewise, the cmdlets also let you specify such thing as storage limits and expiration periods, as well as pointers to internal and external URLs where users can obtain conferencing help and resources.

The Get-CsConferencingConfiguration cmdlet provides a way for administrators to return information about all the Web conferencing configuration settings currently in use in their organization.

Return Types

Get-CsConferencingConfiguration returns instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.WebConf.ConfSettings object.

Examples

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

Copy Code
Get-CsConferencingConfiguration

Example 1 returns information about all the conferencing configuration settings currently in use in the organization. This is done by calling Get-CsConferencingConfiguration without any parameters.

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

Copy Code
Get-CsConferencingConfiguration -Identity site:Redmond

In Example 2, conferencing configuration information is returned for the Redmond site (-Identity site:Redmond). Because Identities must be unique, this command will always return, at most, a single collection of conferencing configuration settings.

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

Copy Code
Get-CsConferencingConfiguration -Filter "site:*"

The command shown in Example 3 returns information about all the conferencing configuration settings that have been applied at the site scope. To do this, Get-CsConferencingConfiguration is called along with the -Filter parameter; the filter value "site:*" ensures that only settings that have an Identity that begins with the string value 'site:" are returned.

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

Copy Code
Get-CsConferencingConfiguration | Where-Object {$_.Organization -ne "Litwareinc"}

The preceding command returns information about all the conferencing configuration settings where the organization is not set to Litwareinc. To carry out this task, the command first calls Get-CsConferencingConfiguration without any parameters; this returns a collection of all the conferencing configuration settings used in the organization. The resulting collection is then piped to the Where-Object cmdlet, which selects only those settings where the Organization property is not equal to (-ne) Litwareinc.

-------------------------- Example 5 --------------------------

Copy Code
Get-CsConferencingConfiguration | Where-Object {$_.MaxContentStorageMB -gt 100}

In Example 5 information is returned only for those conferencing configuration settings where the maximum content storage space is greater than 100 megabytes. To do this, the command first calls Get-CsConferencingConfiguration without any parameters in order to return a collection of all your conferencing configuration settings. This collection is then piped to the Where-Object cmdlet, which picks out those settings that where the content storage space is greater than (-gt) 100 megabytes.