Sets the Active Directory service control point for the Central Management Database.
Syntax
Set-CsConfigurationStoreLocation -SqlServerFqdn <Fqdn> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-GlobalSettingsDomainController <Fqdn>] [-Report <String>] [-SkipLookup <SwitchParameter>] [-SqlInstanceName <String>] [-WhatIf [<SwitchParameter>]] |
Parameters
Parameter | Required | Type | Description |
---|---|---|---|
SqlServer |
Required |
String |
Fully qualified domain name of the computer where the SQL Server database has been installed. For example: -SqlServer atl-sql-001.litwareinc.com. |
InstanceName |
Optional |
String |
Name of the SQL Server instance containing the Microsoft Communications Server tables and data. For example: -InstanceName rtc. |
SkipLookup |
Optional |
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. |
GlobalSettingsDomainController |
Optional |
String |
Fully qualified domain name of a domain controller where global settings are stored If global settings are stored in the System container in Active Directory 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. |
Report |
Optional |
String |
Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\ConfigurationStore.xml" |
Force |
Optional |
Switch Parameter |
Suppresses the display of any non-fatal error message that might arise when running the command. |
WhatIf |
Optional |
Switch Parameter |
Describes what would happen if you executed the command without actually executing the command. |
Confirm |
Optional |
Switch Parameter |
Prompts you for confirmation before executing the command. |
Detailed Description
Active Directory uses service control points (SCP) to help computers locate services. For example, when you install Microsoft Communications Server “14” a service control point is created that provides location information for the Central Management Database used to maintain Communications Server data. Computers that need access to the database connect to Active Directory and use the information contained in the service control point to help them locate the correct computer and the correct instance of SQL Server.
As noted, when you install Microsoft Communications Server an SCP that for the Central Management Database 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 using the Set-CsConfigurationStoreLocation cmdlet.
Return Types
Remove-CsConfigurationStoreLocation does not return any objects or values.
Examples
-------------------------- Example 1 ------------------------
Copy Code | |
---|---|
Set-CsConfigurationStoreLocation -SqlServer atl-sql-001.litwareinc.com -Instance Rtc |
The command shown in Example 1 sets the Active Directory service control point (SCP) for the Microsoft Communications Server central management database. In this example, the SCP points to the computer atl-sql-001.litwareinc.com and to the SQL Server instance Rtc.
-------------------------- Example 2 ------------------------
Copy Code | |
---|---|
Set-CsConfigurationStoreLocation -SqlServer atl-sql-001.litwareinc.com -Instance Rtc -Report C:\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 service control point for the Microsoft Communications Server central management database. In addition to that, information regarding the success (or failure) of this operation is logged to the file C:\Store_Location.html. This log is generated by including the -Report parameter followed by the full path to the log file.