Topic Last Modified: 2014-02-21

Modifies the management connection to the Central Management store. This cmdlet was introduced in Lync Server 2010.


Set-CsManagementConnection -Connection <String> -StoreProvider <FileSystem | Sql | Memory | Azure> [-Confirm [<SwitchParameter>]] [-EnableCaching <$true | $false>] [-WhatIf [<SwitchParameter>]]



The command shown in Example 1 changes the management connection to the SQL Server instance rtcbackup found on the computer

Copy Code
Set-CsManagementConnection -StoreProvider Sql -Connection "\rtcbackup"


In Example 2, the management connection is set to file system and, more specifically, to the folder C:\TestTopology on the local computer.

Copy Code
Set-CsManagementConnection -StoreProvider FileSystem -Connection "C:\TestTopology"

Detailed Description

Configuration data for Lync Server is stored in the Central Management store. It is crucial that both Windows PowerShell and the management replica services be able to locate this database. When you install Lync Server, a service control point is created in Active Directory Domain Services that provides location information for this database. Typically, computers rely on this service control point in order to connect to the Central Management store. To see the details behind this connection (that is, if you want to know which computer the Central Management store is running on, as well information about the SQL Server connection to that Central Management store) all you have to do is run the Get-CsManagementConnection cmdlet.

For the most part, after your management connection has been set you will not need to change it. However, in case of hardware or software failure, you might need to temporarily use a connection; for example, you can configure a computer to work from the local replica. The Set-CsManagementConnection cmdlet provides a way for you to provide a new location for the Central Management store.

Note that any changes you make to Lync Server while using a temporary management connection will not persist if and when you switch back to your original connection. (You can switch back by running the Remove-CsManagementConnection cmdlet.) For example, suppose you decide to temporarily use the file system as your store provider. You change the management connection, and then create several new voice policies (each of which will be instantiated as XML files). When you switch back to your original management connection, these new voice policies will disappear because they were never recorded in the Central Management store now being used.

You should also keep in mind that any changes made by running this cmdlet only affect the local computer. You cannot use the Set-CsManagementConnection cmdlet to change the management connection on other computers.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Set-CsManagementConnection cmdlet locally: RTCUniversalUserAdmins, RTCUniversalServerAdmins, RTCUniversalReadOnlyAdmins.


Parameter Required Type Description




Location information for the SQL Server instance or the file system folder being used as the management connection.

For example, if the new management connection is to a SQL Server instance named rtcbackup on the computer then use this syntax: -Connection "\rtcbackup".

If you want to create a management connection to the folder C:\TestTopology then use this syntax: -Connection "C:\TestTopology". If the folder does not exist, the Set-CsManagementConnection cmdlet will create it.




Indicates the type of back-end store used for configuration information. To store configuration data in SQL Server, set the StoreProvider like this: -StoreProvider Sql. To store configuration data to the file system, use this syntax: -StoreProvider FileSystem. To set store configuration data in Windows Azure use this syntax: -StoreProvider Azure. You should not modify the StoreProvider property unless instructed to do so by Microsoft support personnel.




Prompts you for confirmation before executing the command.




When set to True ($True), caching is enabled for the management connection.




Describes what would happen if you executed the command without actually executing the command.

Input Types

None. The Set-CsManagementConnection cmdlet does not accept pipelined input.

Return Types

The Set-CsManagementConnection cmdlet does not return a value or object. Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Store.StoreProvider object.

See Also