Topic Last Modified: 2010-10-01

Sets the Active Directory service control point for the Central Management store.


Set-CsConfigurationStoreLocation -SqlServerFqdn <Fqdn> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-GlobalSettingsDomainController <Fqdn>] [-Report <String>] [-SkipLookup <SwitchParameter>] [-SqlInstanceName <String>] [-WhatIf [<SwitchParameter>]]


Parameter Required Type Description




Fully qualified domain name (FQDN) of the computer where the Central Management store has been installed. For example: -SqlServer




FQDN of a domain controller where global settings are stored. If global settings are stored in the Active Directory System container, then this parameter must point to the root domain controller. If global settings are stored in the Configuration container, then any domain controller can be used and this parameter can be omitted.




Name of the SQL Server instance containing the Lync Server tables and data. For example: -SqlInstanceName "rtc".



Switch Parameter

If this parameter is included then Set-CsConfigurationStoreLocation will not verify that the specified computer and the specified instance of SQL Server are available. Instead, it will simply change the service control point.

If this parameter is not included then both the specified computer and the specified instance of SQL Server must be available before the SCP will be changed.



Switch Parameter

Suppresses the display of any non-fatal error message that might occur when running the command.




Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\ConfigurationStore.html"



Switch Parameter

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



Switch Parameter

Prompts you for confirmation before executing the command.

Detailed Description

Active Directory Domain Services (AD DS) uses service control points (SCP) to help computers locate services. For example, when you install Microsoft Lync Server 2010, a service control point is created that provides location information for the Central Management store used to maintain Lync Server 2010 data. Computers that need access to the database connect to Active Directory and use the information contained in the SCP to help them locate the correct computer and the correct instance of SQL Server.

As noted, when you install Lync Server an SCP that for the Central Management store is automatically created for you. If you need to move that database to another computer or if you need to move that database to a different instance of SQL Server, then you will need to update the corresponding service control point. That’s a task that can be carried out by using the Set-CsConfigurationStoreLocation cmdlet. When you run this cmdlet, Set-CsConfigurationStoreLocation searches Active Directory for the computer specified by the SqlServer parameter. The cmdlet then sets the store location to the FQDN of that computer.

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

Input Types

None. Set-CsConfigurationStoreLocation does not accept pipelined input.

Return Types

Set-CsConfigurationStoreLocation does not return any objects or values.


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

Copy Code
Set-CsConfigurationStoreLocation -SqlServerFqdn -SqlInstanceName Rtc

The command shown in Example 1 sets the Active Directory service control point for the Lync Server Central Management store. In this example, the SCP points to the computer and to the SQL Server instance Rtc.

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

Copy Code
Set-CsConfigurationStoreLocation -SqlServerFqdn -SqlInstanceName Rtc -Report C:\Logs\Store_Location.html

The command shown in Example 2 is a variation of the command shown in Example 1. This command also sets the Active Directory SCP for the Lync Server Central Management store. In addition, information regarding the success (or failure) of this operation is logged to the file C:\Logs\Store_Location.html. This log is generated by including the Report parameter followed by the full path to the log file.

See Also