1

I'm researching deploying Hyper-V Server R2 (the stand alone product - not the Server 2008 role) into our environment and was curious how the domain joining process would work if the domain controller resided on a guest OS on the Hyper-V box itself?

Is this supported? Or does the domain controller that the Hyper-V box connects to have to be on another physical server box?

Dennis Williamson
  • 62,149
  • 16
  • 116
  • 151
Sangheili
  • 189
  • 1
  • 7
  • 1
    Already covered: http://serverfault.com/questions/15196/can-windows-domain-controller-be-virtualized and http://serverfault.com/questions/70514/running-an-active-directory-primary-domain-controller-as-a-virtual-machine – ThatGraemeGuy Nov 08 '09 at 07:11
  • I searched but didn't find those. Thank you! – Sangheili Nov 08 '09 at 20:10

1 Answers1

0

I've done this with Windows 2008 Hyper-V with two hosts and DC's running as VM's on both - I haven't tried a completely cold boot of the entire environment though, this just allows me to reliably shut down either host without losing the domain. I wouldn't recommend it though for all of the reasons outlined in the answers to the questions linked to in Graeme Donaldson's comment, keeping at least one physical DC is very strongly recommended.

Helvick
  • 20,019
  • 4
  • 38
  • 55