First published on MSDN on Jan 09, 2018
For the last two decades, changing the domain membership of a Failover Cluster has always required that the cluster be destroyed and re-created. This is a time-consuming process, and we have worked to improve this.
This is going to enable scenarios such as building a Failover Cluster in one location and then ship it to its final location or in the event that companies have merged and need to move them to their domain structure.
Moving a Cluster from one domain is a straight-forward process. To accomplish this, we introduced two new PowerShell commandlets.
In the following example, this is my setup and goal:
The process to accomplish to accomplish this is to change the cluster from one domain to a workgroup and back to the new domain. For example:
1. Create a local Administrator account with the same name and password on all nodes.
2. Log on to the first node with a domain user or administrator account that has Active Directory permissions to the Cluster Name Object (CNO), Virtual Computer Objects (VCO), has access to the Cluster, and open PowerShell.
3. Ensure all cluster Network Name resources are in an Offline state and run the below command to change the type of the Cluster to a workgroup.
Remove-ClusterNameAccount -Cluster CLUSCLUS -DeleteComputerObjects
4. Use Active Directory Users and Computers to ensure the CNO and VCO computer objects associated with all cluster names have been removed.
5. If so, it is a good idea to go ahead and stop the Cluster Service on both nodes and set the service to MANUAL so that it does not start during this process.
Stop-Service -Name ClusSvc
Set-Service -Name ClusSvc -StartupType Manual
6. Change the nodes domain membership to a workgroup, reboot, then join to the new domain, and reboot again.
7. Once the nodes are in the new domain, log on to a node with a domain user or administrator account that has Active Directory permissions to create objects, has access to the Cluster, and open PowerShell. start the Cluster Service, and set it back to Automatic.
Start-Service -Name ClusSvc
Set-Service -Name ClusSvc -StartupType Automatic
8. Bring the Cluster Name and all other cluster Network Name resources to an Online state.
Start-ClusterResource -Name "Cluster Name"
Start-ClusterResource -Name FS-CLUSCLUS
9. We now need to change Cluster to be a part of the new domain with associated active directory objects. To do this, the command is below. The network name resources must be in an online state.
New-ClusterNameAccount -Name CLUSTERNAME -Domain NEWDOMAINNAME.com -UpgradeVCOs
10. If you do not have any additional groups with network names (i.e. a Hyper-V Cluster with only virtual machines), the -UpgradeVCOs parameter switch is not needed.
NOTE: If you are using the new USB Witness feature, you will be unable to add the cluster to the new domain. The reasoning is that the file share witness type must utilize Kerberos for authentication. Simply change the witness to none before adding the cluster to the domain. Once it is completed, recreate the USB witness. The error you will see is:
New-ClusternameAccount : Cluster name account cannot be created. This cluster contains a file share witness with invalid permissions for a cluster of type AdministrativeAccesssPoint ActiveDirectoryAndDns. To proceed, delete the file share witness. After this you can create the cluster name account and recreate the file share witness. The new file share witness will be automatically created with valid permissions.
11. Use Active Directory Users and Computers to check the new domain and ensure the associated computer objects were created. If they have, then bring the remaining resources in the groups online.
Start-ClusterGroup -Name "Cluster Group"
Start-ClusterGroup -Name FS-CLUSCLUS
Senior Program Manager
High Availability and Storage
Follow me on Twitter @JohnMarlin_MSFT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.