Hello. I guess I'm missing a major fundamental concept to Hyper-V Server 2012 and I realized it as I was starting to apply it.
I'm dong a bunch of major upgrades and in an effort follow best practices, I'm trying to move the primary DC off the host server and use the (bad ass) host (that I just built ;)) to run Hyper-V Server exclusively .
I got to the server setup and went to configure the network but I knew I would not be able to contact the DC because I was booted to the Hyper-V . In turn, I cannot access the Hyper-V Server when booted into the server GUI. I see tons of content regarding setting up the Remote Admin roles and logging in remotely but I was hoping I was going to be able to use one of my VMs like the DC to login to automatically every time. On the tutorials I see people switchimg from Server Setup to a GUI and it doesn't look like they are using Remote desktop.
I'm building a 2nd server but its not done yet but is a DC on a 2nd physical box and a remote connection required or is there some way to dual boot and have Hyper-V Server fired up in the background? If not then I will probably just go through the expense of using the GUI version of Hyper-V on a copy of 2012 maybe giving Server 2012 R2 Essentials a try.
"GASP! OMG he's running Hyper-v and Active Directory on the same machine?!" LOL no it is not cool but although I do run my business off of these machines I'm a small business operating from my home and much of this is for my own education and interests.