Hi

Im changing a Lync standard server from one hw to another and while moving the Central Management Server I tried to just run “ Install-CsDatabase –CentralManagementDatabase “

That resulted in

Error: Error connecting to “server.fqdn.local” while installing “CentralMgmtStore”. Verify that the SQL instance is running, connections are not being blocked by a firewall, and that you have SQL administrator permissions. For details, see the following log file: “C:\Users\user\AppData\Local\Temp\Create-CentralMgmtStore-server.fqdn.local-[2010_12_28][13_24_51].log”   2010-12-28 13:25:57   Error

└    Error: An error occurred: “Microsoft.Rtc.Common.Data.SqlConnectionException” “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)”   2010-12-28 13:26:13   Error

Well it was an easy fix.

Make sure to run the full command and –clean

Install-CsDatabase -CentralManagementDatabase -clean -sqlserverfqdn server.fqdn.local sqlinstance rtc

Some other things to keep in mind

from http://ucmadeeasy.wordpress.com/2010/11/09/lync-server-2010-active-directory-references-and-how-to-remove-them/ 

All credits for the below list should go to Randy Wintle

Before you move the Central Management Server, you must do the following:

1. Verify that you have created the new Central Management store. This is d
one by running the Install-CsDatabase cmdlet and using the CentralManagemen
tDatabase parameter.

2. If you are moving the Central Management Server to a Standard Edition se
rver, verify that you have used local setup to run the Prepare Standard Edi
tion server option. This advance preparation is required to add firewall ru
les that will allow Windows PowerShell to remotely access the new Central M
anagement store.

3. Verify that there is enough free disk space on the computer where Move-C
sManagementStore is being run to accommodate the Central Management Server.

4. Verify that the Front End Server service has been installed on the compu
ter where Move-CsManagementStore is being run. If this service is not insta
lled, and running, then the move will fail.

5. Verify that you can successfully run the Enable-CsTopology cmdlet on the
computer where Move-CsManagementStore is going to be run. If Enable-CsTopo
logy cannot be run on that computer then the move will fail and you will no
longer have a functioning Central Management store.

After you have completed these steps, all you need to do to move the Centra
l Management Server from Pool A to Pool B is log on to a computer in Pool B
and then call Move-CsManagementServer without any additional parameters:

Move-CsManagementServer

When you do that, Move-CsManagementServer will consult the topology to dete
rmine the prior location of the Central Management Server  (Pool A), and th
en transfer the Central Management Server and the Central Management store
to the current pool (Pool B).

If the move succeeds, Move-CsManagementServer will display a list of comput
ers on the screen. In order to finish the move, you must run local setup on
each of these computers. Computers in Pool A will still be running an inac
tive version of the Central Management service; running local setup will de
lete that service. The computer in Pool B where the Central Management Serv
er was moved will be running the Central Management service; however, other
computers in the pool will not. Running local setup on these computers wil
l install the Central Management service.