EXAMPLE 1

In the first example, the Get-CsClientVersionConfiguration cmdlet is called without specifying any additional parameters. This causes the Get-CsClientVersionConfiguration cmdlet to return a collection of all the client version configuration settings currently in use in your organization.

	Copy Code
Get-CsClientVersionConfiguration

EXAMPLE 2

In this example, the Get-CsClientVersionConfiguration cmdlet returns all the client version configuration settings that have the Identity site:Redmond. Because Identities must be unique, this command will never return more than one item.

	Copy Code
Get-CsClientVersionConfiguration -Identity site:Redmond

EXAMPLE 3

Example 3 returns all the client version configuration settings that have been applied at the site scope. This is done by including the Filter parameter and the filter value "site:*". That filter value instructs the Get-CsClientVersionConfiguration cmdlet to return only the settings that have an Identity that begins with the string value "site:".

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

EXAMPLE 4

Example 4 returns all the client version configuration settings that are currently disabled. To carry out this task, the command first uses the Get-CsClientVersionConfiguration cmdlet to return a collection of all the client version settings configured for use in the organization. This collection is then piped to the Where-Object cmdlet, which applies a filter that limits the collection to those settings where the Enabled property is equal to False.

	Copy Code
Get-CsClientVersionConfiguration | Where-Object {$_.Enabled -eq $False}

Lync Server gives administrators considerable leeway when it comes to specifying the client software (and, equally important, the version number of that software) that users can use to log on to the system. For example, there is no technical reason that requires users to log on to Lync Server by using Lync; there are no technical limitations that would prevent users from logging on by using Microsoft Office Communicator 2007 R2.

However, there might be some non-technical reasons why you would prefer that your users do not log on by using Office Communicator 2007 R2. For example, Office Communicator 2007 R2 does not support all of the features and capabilities found in Lync; as a result, users who log on with Office Communicator 2007 R2 will have a different experience than users who log on by using Lync. This can create difficulties for your users; it can also create difficulties for help desk personnel, who must provide support for a number of different client applications.

If this could be a problem for your organization you can employ client version filtering in order to specify which client applications can be used to log on to Lync Server. When you install Lync Server, a global set of client version configuration settings is installed and enabled. These settings are used to determine whether or not client version filtering is enabled. In addition to the global settings, client version configuration settings can also be applied at the site scope; in those instances, the site settings will have precedence over the global settings.

The Get-CsClientVersionConfiguration cmdlet enables you to retrieve information about the client version configuration settings currently in use in your organization. Note that this cmdlet does not return information about which client applications are allowed or are not allowed. To retrieve that information, use the Get-CsClientVersionPolicy cmdlet.

Note, too that client version configuration is not a security feature. The technology relies on self-reporting from client applications, and does not attempt to verify that an application is really the application and the version number of that application that it claims to be.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Get-CsClientVersionConfiguration cmdlet locally: RTCUniversalUserAdmins, RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself) run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Get-CsClientVersionConfiguration"}

None. The Get-CsClientVersionConfiguration cmmmdlet does not accept pipelined input.

The Get-CsClientVersionConfiguration cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ClientVersion.ClientVersionConfiguration object.