| Author | Chrissy LeMaire (@cl), netnerds.net |
| Availability | Windows, Linux, macOS |
Want to see the source code for this command? Check out Move-DbaRegServer on GitHub.
Want to see the Bill Of Health for this command? Check out Move-DbaRegServer.
Moves registered servers between groups within SQL Server Central Management Server (CMS)
Moves registered server entries from one group to another within Central Management Server hierarchy. This helps reorganize CMS structure when server roles change or you need to restructure your server groupings for better management. The function updates the CMS database to reflect the new group membership while preserving all server connection details and properties.
Move-DbaRegServer
[[-SqlInstance] <DbaInstanceParameter[]>]
[[-SqlCredential] <PSCredential>]
[[-Name] <String[]>]
[[-ServerName] <String[]>]
[[-Group] <String>]
[[-InputObject] <RegisteredServer[]>]
[-EnableException]
[-WhatIf]
[-Confirm]
[<CommonParameters>]
PS C:\> Move-DbaRegServer -SqlInstance sql2012 -Name 'Web SQL Cluster' -Group HR\Prod
Moves the registered server on sql2012 titled 'Web SQL Cluster' to the Prod group within the HR group
PS C:\> Get-DbaRegServer -SqlInstance sql2017 -Name 'Web SQL Cluster' | Move-DbaRegServer -Group Web
Moves the registered server 'Web SQL Cluster' on sql2017 to the Web group, also on sql2017
The target SQL Server instance or instances.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).
Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory - Integrated are all supported.
For MFA support, please use Connect-DbaInstance.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Specifies one or more registered servers to move by their display name as shown in SSMS CMS interface. This is the friendly name you see in the registered servers tree, which may differ from the
actual server instance name.
Use this when you know the descriptive name assigned to servers in CMS but not necessarily their technical instance names.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Specifies one or more registered servers to move by their actual SQL Server instance name. This is the technical server\instance connection string used to connect to SQL Server.
Use this when you need to target servers by their network instance names rather than their CMS display names.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Specifies the destination group where the registered servers will be moved. Use backslash notation for nested groups like 'Production\WebServers'.
If not specified, servers are moved to the root level of the CMS hierarchy. The target group must already exist in CMS.
| Alias | NewGroup |
| Required | False |
| Pipeline | false |
| Default Value |
Accepts registered server objects from the pipeline, typically from Get-DbaRegServer output. This allows you to filter servers first and then move the results.
Use this approach when you need complex filtering or when working with servers from multiple CMS instances.
| Alias | |
| Required | False |
| Pipeline | true (ByValue) |
| Default Value |
By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value | False |
Shows what would happen if the command were to run. No actions are actually performed.
| Alias | wi |
| Required | False |
| Pipeline | false |
| Default Value |
Prompts you for confirmation before executing any changing operations within the command.
| Alias | cf |
| Required | False |
| Pipeline | false |
| Default Value |