New-CsClientVersionConfiguration

Syntax

New-CsClientVersionConfiguration
   [-Identity] <XdsIdentity>
   [-DefaultAction <DefaultAction>]
   [-Enabled <Boolean>]
   [-Force]
   [-InMemory]
   [-WhatIf]
   [-Confirm]
   [-DefaultURL <String>]
   [<CommonParameters>]

Description

Skype for Business 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 Skype for Business Server by using Skype for Business; 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 Skype for Business; as a result, users who log on with Office Communicator 2007 R2 will have a different experience than users who log on by using Skype for Business. 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 the client applications that can be used to log on to Skype for Business Server. When you install Skype for Business 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, the New-CsClientVersionConfiguration cmdlet enables you to create client version configuration settings at the site scope. When client version configuration settings are applied at the site scope, those settings take precedence over the global settings. For example, suppose you have enabled client version filtering at the global scope, and then you create a separate collection of settings for the Redmond site, a collection of settings where client version filtering is disabled. In that case, client version filtering will be disabled for all the users who have accounts on the Redmond site.

Note, however, that anonymous users are only affected by global settings. That's because anonymous users are not associated with a site.

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.

Examples

-------------------------- EXAMPLE 1 --------------------------

New-CsClientVersionConfiguration -Identity site:Redmond -Enabled $False

The command shown in Example 1 creates a new collection of client version configuration settings for the Redmond site. In this command, the Enabled parameter is set to False, which means that client filtering is disabled for the Redmond site.

-------------------------- EXAMPLE 2 --------------------------

$x = New-CsClientVersionConfiguration -Identity site:Redmond -InMemory

$x.DefaultAction = "Block"

Set-CsClientVersionConfiguration -Instance $x

Example 2 shows how you can create a new collection of client version configuration settings in memory, modify that collection, and then turn these virtual settings into an actual collection of settings applied to the Redmond site. To do this, the first command uses the New-CsClientVersionConfiguration cmdlet and the InMemory parameter to create an in-memory-only collection of settings with the Identity site:Redmond. This collection is stored in a variable named $x and exists in memory only: if you terminate your Windows PowerShell session or delete the variable $x these client version configuration settings will disappear and will never be applied to the Redmond site.

In command 2 the value of the DefaultAction property for the virtual settings is set to Block. In command 3, the Set-CsClientVersionConfiguration cmdlet is used to transform the virtual settings into an actual collection of client version configuration settings applied to the Redmond site.

Parameters

-Confirm

-DefaultAction

-DefaultURL

-Enabled

-Force

-Identity

-InMemory

-WhatIf

Inputs

None. The New-CsClientVersionConfiguration cmdlet does not accept pipelined input.

Outputs

Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ClientVersion.ClientVersionConfiguration object.

Related Links

• Get-CsClientVersionConfiguration
• Remove-CsClientVersionConfiguration
• Set-CsClientVersionConfiguration