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

Ok, i seem to have gotten myself into a bit of a catch 22.

I have a hyper-v 2012 server which is running the Domain Controller. However, the Domain Controller isn't loading due to some sort of error.

I cannot remote manage the Domain Controller or use the hyper-v manager remotely, as the hyper-v server has no DC to authenticate against.

I cannot log in to the virtual machine directly from the VM Host, as hyper-v server doesn't have the ability to use hyper-v manager.

Anyone know a possible work around? I know i should have installed a second DC to avoid scenarios exactly like this, however i just never got to it as was busy with other things.

Any advice would be much appreciated.

share|improve this question
Should mention, it is stuck at a screen where it says "Choose an option. Then i think the options are Continue, repair and shut down. However i can only see it in the thumbnail (using corefig utility, which unfortunately doesn't let you remote desktop into the machine) – MSwehli May 25 '13 at 15:19
Was the DC on a CSV? – MDMarra May 25 '13 at 15:22
Nope. Locally stored. This set up was just the basics I was going to work on, however i didn't have time unfortunately. – MSwehli May 25 '13 at 15:28
I have physical access to the hyper-v host, and can login locally to that, either through the remote desktop or physically. It is just the server manager and hyper-v manager tools which i cannot use remotely. – MSwehli May 25 '13 at 15:33
up vote 0 down vote accepted

Ok, so heres what i did to get around it, which i guess was the obvious answer however took quite a lot of time.

First i installed a copy of windows server 2012 standard with GUI on a different server i wasn't using. Next i copied the VM files and VHD file to the new server, in directories with the same name. Then i created a new VM in the new server, i chose to attach the virtual hard disk later, and named it the same name as the first VM. I then went through the files, and replaced any mention of the old GUID with the new GUID. including folder names, file names, and opening the actual .xml configuration file, and using find and replace.

So far it seems to be working well, can use server manager again and hyper-v manager, DNS is working, etc.

share|improve this answer

I can successfully remotely manage my Hyper-V Server 2012 Core in a workgroup environment. I can also remotely manage the disks on the Hyper-V server.

I wrote a quick 12-step tutorial (article and video) showing exactly what I did to get this working.

Hopefully this can help others who found this to be a very frustrating task.


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.