Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We're moving our domain controller to a new Hyper-V host. I read it on TechNet about not using export on a VM running as DC (although I saw a lot of answers on TechNet suggesting doing so to move DC). What we plan to do is shutdown the VM, move the VHD to the new Hyper-V host, then create a new VM using that VHD. I don't think USN rollback would occur since it's like shutting down the VM and starting it back up. We have another Hyper-V host with a DC guest that will be running during the migration. All the hosts and VMs are running Windows Server 2008 R2.

Is it a good way to move virtualize DC b/t hosts? If not, how should I proceed?

share|improve this question
    
As a reminder its always a good idea to have a physical DC somewhere on the network to handle virtual downtime that is inevitable. –  Brent Pabst Sep 10 '12 at 12:40
    
We have two DCs running on two Hyper-V hosts to handle downtime. Should we still have one more physical DC? –  Jim Sep 10 '12 at 12:41
1  
Yes. For instance, if you're Hyper-V Hosts happen to be part of a cluster and both DCs are offline, good luck getting the cluster to start properly, let alone access storage devices with no logon servers present on the network. It's OK to virtualize most of them, just have a physical box sitting arround that can help when needed. Saves lots of trouble later on. Plus MSFT recommends it. –  Brent Pabst Sep 10 '12 at 12:43
    
I see. The hosts are domain-joined by not clustered. I'll definitely consider having a small box as a physical DC. Thanks for the advice =) –  Jim Sep 10 '12 at 12:45
    
Yea, there are other services as well that may rely on authentication on Hyper-V host startup, so certainly something to look into. –  Brent Pabst Sep 10 '12 at 12:52

1 Answer 1

up vote 4 down vote accepted

I have moved several DCs in the way you described and it works rather well. Don't forget to remove the old network interface after re-creating the VM on the new host.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.