Parameters

Lync Server 2010 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 2010 by using Microsoft Lync 2010; there are no technical limitations that would prevent users from logging on by using Microsoft Office Communicator 2007 R2.

On the other hand, 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 2010; 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 2010. 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 2010. When you install Lync Server 2010, 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 Set-CsClientVersionConfiguration cmdlet enables you to modify an existing collection of client version configuration settings.

Note 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 Set-CsClientVersionConfiguration cmdlet locally: 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 "Set-CsClientVersionConfiguration"}

Microsoft.Rtc.Management.WritableConfig.Policy.ClientVersion.ClientVersionConfiguration object. Set-CsClientVersionConfiguration accepts pipelined instances of the client version configuration object.

Set-CsClientVersionConfiguration does not return a value or object. Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ClientVersion.ClientVersionConfiguration object.

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

	Copy Code
Set-CsClientVersionConfiguration -Identity site:Redmond -Enabled $False

In Example 1, Set-CsClientVersionConfiguration is used to modify the settings collection with the Identity "site:Redmond". In this case, the Enabled parameter is set to False in order to disable the client version configuration settings.

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

	Copy Code
Get-CsClientVersionConfiguration | Set-CsClientVersionConfiguration -DefaultURL "https://litwareinc.com/csclients"

In the preceding example, the DefaultUrl property is modified for all the client version configuration settings currently in use in the organization. To do this, the command first calls Get-CsClientVersionConfiguration without any additional parameters in order to return all of the client version configuration settings. That information is then piped to Set-CsClientVersionConfiguration, which sets the value of the DefaultUrl for each configuration collection to https://litwareinc.com/csclients.

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

	Copy Code
Get-CsClientVersionConfiguration | Where-Object {$_.DefaultAction -eq "Block"} | Set-CsClientVersionConfiguration -DefaultAction "BlockWithUrl" -DefaultURL "https://litwareinc.com/csclients"

In Example 3, modifications are made to all the client version configuration settings where the DefaultAction is currently set to Block. To carry out this task, the command first uses Get-CsClientVersionConfiguration to return all of the client version configuration settings currently in use. That information is then piped to the Where-Object cmdlet, which picks out only those items where the DefaultAction property is equal to "Block". In turn, that filtered collection is then piped to Set-CsClientVersionConfiguration, which does two things to each item in the collection: 1) sets the DefaultAction to BlockWithUrl; and, 2) sets the DefaultUrl to https://litwareinc.com/csclients.

Other Resources