Recommendations on Virtual Domain Controllers

Hello Experts,

We are going to be building up two new Windows 2003 domain controllers to replace two existing Windows 2000 domain controllers.  
Can anyone give me some guidance as to why we SHOULD or SHOULD NOT create these virtually?  If we did create them virtually, they would be on to SEPARATE VMWare hosts, so the would be on different hardware.

Is there anything other than server time synchronization that would cause a problem with this?

Thanks in advance for your advice.
Who is Participating?
Mike KlineConnect With a Mentor Commented:
See this question I helped with earlier this year

two other good links from the AD team

those focus on virtualizing with hyper-v but you can do it with other products too.

putting them on separate hosts does give you extra fault tolerance.

We are soon going to virtualize all our DCs too (will be done in Nov).  If you plan right you will be ok.  Just don't have the box/DC time sync with the host


Robby SwartenbroekxConnect With a Mentor MSP engineerCommented:
We have virtualized all of our DC's (and done it with some of our customers too) with both W2k3 and W2k8. We don't have any problems with AD.

Only drawback: ESX boots faster if it has an active DNS server when it is booting. If you have virtualised everything, it is possible booting both machines on the same time (after power failure) takes a longer time. (about 15 minutes)
allan_jardineConnect With a Mentor Commented:
I have some virtual DCs and have found no problems with them and I am gradually moving all of them to virtual. As stated above, spread them on a number of hosts for fault tolerance.
CanHasCheezburgerAuthor Commented:
Excellent.  Thank you all for your advice on this!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.