Delete an existing collection of client version configuration settings in Lync Server 2013

Lync Server 2013

Topic Last Modified: 2013-02-23

If you want to remove the client configuration settings that have been previously configured for a site, you can remove the settings from Lync Server 2013 Control Panel or Lync Server 2013 Management Shell.

  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 2013 administrative tools.

  3. In the left navigation bar, click Clients, and then click the Client Version Configuration navigation button.

  4. Select the site, click Edit, click Delete, and then click OK.

You can delete client version configuration settings by using the Remove-CsClientVersionConfiguration cmdlet. This cmdlet 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

  • The following command removes the client version configuration settings applied to the Redmond site:

    Remove-CsClientVersionConfiguration -Identity "site:Redmond"

  • This command removes all the client version configuration settings configured at the site scope:

    Get-CsClientVersionConfiguration -Filter site:* | Remove-CsClientVersionConfiguration

  • And this command removes all the client version configuration settings where the default action has been set to "Block":

    Get-CsClientVersionConfiguration | Where-Object {$_.DefaultAction -eq "Block" | Remove-CsClientVersionConfiguration

For details, see the Help topic for the Remove-CsClientVersionConfiguration cmdlet.