[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Moves the central management server from one pool to another.

Syntax


Move-CsManagementServer [-Confirm [<SwitchParameter>]] [-CsConfiguration <String>] [-CsLisConfiguration <String>] [-Force <SwitchParameter>] [-Report <String>] [-SourceIsBetaVersion <$true \| $false>] [-WhatIf [<SwitchParameter>]]

Move-CsManagementServer [-Confirm [<SwitchParameter>]] [-CsConfiguration <String>] [-CsLisConfiguration <String>] [-Force <SwitchParameter>] [-Report <String>] [-SourceIsBetaVersion <$true | $false>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter	Required	Type	Description
CsConfiguration	Optional	String	Full path to the Communications Server configuration backup file created by running the Export-CsConfiguration cmdlet. This parameter should only be used in a disaster recovery scenario.
CsLisConfiguration	Optional	String	Full path to the E9-1-1 backup file created by running the Export-CsLisConfiguration cmdlet. This parameter should only be used in a disaster recovery scenario.
SourceIsBetaVersion	Optional	Boolean	When set to True ($True), the database is not marked as read-only before it is moved.
Report	Optional	String	Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\MoveManagementServer.html"
Force	Optional	Switch Parameter	Forces the management server move even if the existing database is offline; this parameter is required in a disaster recovery scenario. Note that there is the potential for some data loss any time you force the movement of the management server.
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

The Move-CsManagementServer cmdlet enables administrators to move the central management server role (and the accompanying database) from one pool to another. Because there is always the potential for data loss (not to mention service interruption) any time you move the central management server, it is recommended that you do not make such a transfer unless:

You need to decommission the existing management pool, and must transfer the central management server before doing so.

You’ve encountered a disaster recovery scenario in which the existing management server is no longer accessible.

To transfer the management server from Pool A to Pool B all you need to do is log on to a computer in Pool B and call Move-CsManagementServer without any additional parameters:

Move-CsManagementServer

When you do that, Move-CsManagementServer will consult the topology to determine the prior location of the management server (Pool A) and then transfer the server and the management database to the current pool (Pool B).

To transfer the management server in a disaster recovery scenario you should have, ideally, used the Export-CsConfiguration and Export-CsLisConfiguration cmdlets to create backup files of your Communications Server configuration and your E9-1-1 configuration, respectively. (Because disasters typically occur without warning, it goes without saying that you should routinely run these cmdlets and make backup files of your configuration settings.) You should then include both the –CsConfiguration and –CsLisConfiguration parameters in order to read in these backup files.

On top of that, you must also include the –Force parameter any time you are trying to move a management server that is offline or otherwise inaccessible. When you call Move-CsManagementServer the cmdlet temporarily sets the management database to read-only before moving that database; that helps guard against data loss. In a disaster recovery scenario, however, the database cannot be marked as read-only. The –Force parameter instructs the cmdlet to move the database even though it has not been configured as read-only.

Note that the Move-CsManagementServer cmdlet must be run locally; it cannot be called from a remote management session.

Return Types

Move-CsManagementServer does not return any objects.

Examples

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

	Copy Code
Move-CsManagementServer

The command shown in Example 1 moves the central management server from its existing pool to a new pool. To perform this live migration (that is, to move a management server that is online and accessible) you must run the command from a computer located in the pool where the server is to be moved.

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

	Copy Code
Move-CsManagementServer -CsConfiguration "C:\CsConfiguration.xml" -CsLisConfiguration "C:\CsLisConfiguration.xml" -Force

Example 2 moves the central management server in a disaster recovery scenario; that is, in a scenario where the existing management server is offline or other inaccessible. To perform this type of migration, you must run the preceding command from a computer located in the pool where the server is to be moved. In addition, you must include the –CsConfiguration parameter to import your previously-saved configuration backup file; the –CsLisConfiguration parameter, to import your previously-saved E9-1-1 backup file (if you are using E9-11); and –Force to force the transfer of the management server even though the existing server cannot be contacted.