Moving a Hyper-V cluster to a new AD Domain

Company A and Company B are Merging. Company A has better ICT infrastructure and so will use this environment to help setup a new domain for both company A and company B

Company A - environment
2 x 2012 Hyper-V Manager hosts (5 x VM's on each) attached to HP SAN storage and running failover cluster management.

Idea (very much simplified):
1. Create a new VM DC (and domain) within the current Cluster
2. Import all users into AD from Company A/B
3. move all VM's into new Domain

There are a ton of other things to take note of but I am thinking this solution may not be viable as the both the 2012 hosts are on the Company A  domain currently.

Did some investigating and did find this and looks like could be a better way to proceed but we only have 1 cluster and need to have a new DC (domain) to be running somewhere. 

Just after suggestions from any experts that may have done this in the past.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Truthfully, that process seems overly complex. Unless you have no free storage, I'd live migrate the VMs from the old cluster into a new one. Draining anode, evicting it, and standing up a new cluster on that node should allow for this with minimal effort.
You cannot migrate failover cluster from one domain to another

The better approach could be:
Backup all VM configuration and VHDX for safety

Move all VMs to one node (node A to node B)
Then remove node A from cluster and domain
Build new domain (DC) may be outside this TWO nodes
Join above node A to new domain and built one node hyper-v failover cluster

Now on node B shutdown all VMs, remove CSV volume from cluster
delete failover cluster
Disjoin node B from source domain and add to target domain
Add this server to new failover cluster created above
Add same storage above as CSV volume again

Start VMs again

This will be accomplished with some downtime

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
oiaadminAuthor Commented:
Hi Cliff,

thanks for that, we only have 300GB left in storage on the current cluster  so would love to proceed that way as its simple but storage is an issue. Thanks for your input.
oiaadminAuthor Commented:
Hi Mahesh,

Thanks for the feedback, your suggestion sounds like the way to go but time constraints are forcing us to change our plan completely initially for phase 1 and during phase 2 will look to implement what you have suggested and for that reason have awarded your most of the points
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.