Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently having an issue with our Domain Controller network environment which is on Hyper V. Basically the machine that was hosting the Hyper V has crashed. The problem is not with hard drive but with the corrupted hyper v file.

We have all the vhds and xml configuration files in separate partition. Plan is to make a fresh install of hyper v and reattach all virtual machine. My question is how to do this so that we can retain same DC network?

Please let me know if you need further clarification.


share|improve this question
Can you be more specific? I don't see any reason your Domain Controller would be affected. What do you mean by "corrupted hyper-v file"? – Chris S Oct 19 '12 at 13:09
Sorry, My concern is that if I build a brand new hyper V server from scratch, could I be able to import/add my existing vhds to the new Hyper V server and rebuild my DC environment? – activebiz Oct 19 '12 at 13:57
You can get the old VMs into Hyper-V, yes. It's not quite as easy as "importing" them because they weren't "exported" cleanly. Still not clear on why you're rebuilding your DC environment; where is the DC, where are your backups? – Chris S Oct 19 '12 at 14:17
You really need to define "corrupted hyper-v file". Was it the guest file that got corrupted or the host/parent install that got corrupted? – Rex Oct 19 '12 at 14:51

Ideally your DC was is separate server and then I don't see the issue right away ...

Or I could be missing what exactly the problem is ?

besides that you "lost" your config of the Hyper-V Server itself I don't see any issue to the Vm's.

if they can access the network on which the domain is "live" then for them nothing will change.

again, I think i'm missing something here regarding what exactly the issue at hand is though.

share|improve this answer

From what I gather, "the corrupted hyper v file" is the Hyper-V host system?

If your Hyper-V host has failed, its not the end of the world. When you have a new host setup, create a new VM, and instead of creating a new .vhd, point to the one you recovered. You won't be able to use any snapshots, though. Assuming the .vhd isn't corrupted, or the guest OS didn't freak out when it was abruptly powered down, it should come up.

share|improve this answer

Your Answer


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.