About the central Management Server (CMS) workaround that appears when you upgrade Lync or install Lync

Recently made a Lync demo, the experiment is out of the question, I will change the entire environment once.

Finally, I want to install the whole environment and find that there have been problems.

Then the Lync environment was cleared, but found no way to solve it smoothly. All problems end up with an issue where the central Management Server is present and cannot be removed.

Find a lot of information, just know you can use the command to dispose of this central management Server, that is, processing the SCP in the domain.

In Lync Front End server Open Lync Command line tool, enter remove-csconfigurationstorelocation to remove the central Management Server CMS

Here's what you'll see:

after you execute the command, you can delete the CMS SCP is stored in AD ds. In addition to deleting the SCP, this command also logs information about the success (or failure) of the operation to the log file C:\Logs\Store_Location.html. To create the log file, this command uses the report parameter, followed by the path to the log file where the information should be logged. If the file already exists, its contents will be overwritten when the command is run. If the file does not exist, the file is created when you run this command.

Remove-csconfigurationstorelocation-report C:\Logs\Store_Location.html

installation the SCP for the central management store is automatically created when Lync Server is in. If you need to move the database to another computer or if you need to move the database to a different instance of SQL Server, you will need to update the appropriate service control points. You can use the Set-csconfigurationstorelocation command to perform this task. When you run this cmdlet, Set-csconfigurationstorelocation searches the Active Directory for the computer specified by the SQL Server parameter. The cmdlet then sets the storage location to the FQDN of the computer. RTCUniversalServerAdmins permissions are required by default. For specific day command parameters, please refer to the following:

set-csconfigurationstorelocation-sqlserverfqdn <lync Server or SQL Server fqdn>- Sqlinstancename <sqlserver Instance name >

at the completion after the SCP is rebuilt, we can continue to publish the topology to the new CMS location to complete the forced uninstallation of the already offline CMS and rebuild the CMS on the new SQL Server or Standard Edition Servers. After that we can re-publish the topology, save our incomplete lyncserver environment, or deploy a new version of Lync Server to fully rebuild a Lync Server system.

About the central Management Server (CMS) workaround that appears when you upgrade Lync or install Lync