Topic Last Modified: 2013-02-23

You can use client version policies to specify the versions of clients that are supported in your environment. Using client versioning can help reduce the costs associated with supporting multiple client versions. It can also improve the overall user experience, because when earlier and later versions of clients interact, the available features can be limited by the earlier version of the client. You can create or modify client version policies from Lync Server 2013 Control Panel or Lync Server 2013 Management Shell.

To create or modify client version policies by using Lync Server Control Panel

  1. From a user account that is assigned to the CsUserAdministrator role or the CsAdministrator role, log on to any computer in your internal deployment.

  2. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

  3. In the left navigation bar, click Clients.

    Note:
    The Client Version Policy tab is selected by default.

  4. On the Client Version Policy page, do one of the following:

    • To create a client version policy, click New, select Site policy, Pool policy, or User policy, and then click OK.

    • To modify the global policy or another existing client version policy, select the policy, click Edit, and then click Show details.

  5. On the Edit Client Version Policy page, create or modify rules as described in Create or Modify a New Client Version Policy Rule.

Creating or Modifying Client Version Policies by Using Windows PowerShell Cmdlets

You can create client version policies by using the New-CsClientVersionPolicy cmdlet, and modify them by using the Set-CsClientVersionPolicy cmdlet. These cmdlets can be run either from the Lync Server 2013 Management Shell or from a remote session of Windows PowerShell. For details about using remote Windows PowerShell to connect to Lync Server, see the Lync Server Windows PowerShell blog article "Quick Start: Managing Microsoft Lync Server 2010 Using Remote PowerShell" at http://go.microsoft.com/fwlink/p/?linkId=255876.

To create a new site-scoped client version policy

  • The following command creates a new client version policy applied to the Redmond site. Because no additional parameters are specified, the new policy will use the default client version settings.

    Copy Code 
    New-CsClientVersionPolicy -Identity "site:Redmond"

To create a new per-user client version policy

  • To create a per-user policy, use a command similar to this:

    Copy Code 
    New-CsClientVersionPolicy -Identity "RedmondClientVersionPolicy"

For details, see the Help topics for the New-CsClientVersionPolicy cmdlet and the Set-CsClientVersionPolicy cmdlet.