• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1128
  • Last Modified:

VMware - multiple domain controllers

I had a look at this link

I understand that it is not recommended to install vmware on a DC, but can I  have multple DC's that are running as a  virtual machine with VMware?
3 Solutions
Yes, that should be no problem.
Dan560Author Commented:
So it won't  course any conflicts, what about small business servers? Maybe I'm asking this question in the wrong zone, but you cant really have them running on the same network, do you think there won't be any problems with this product as well?
It would probably be a good idea to have them running on seperate servers in case of hardware failure.  But yeah i've ran multiple DCs on VMware with distributed roles and no problems here.  You don't want to install VMWare on a DC, but you can install DCs into VMWare.
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

SBS servers can run on the same LAN, but not on the same domain. Also if they are on the same LAN make sure there is only one DHCP server active. You can also setup VmWare to use separate virtual LANs, check out Host-Only networking with VmWare.
Dan560Author Commented:
thanks final question now...
I have asked this before, but say if I wanted two virtual machines running exchange how does the port mapping work. My Router can handle multiple IP's but would I need multiple network adapters on the machine running vmware to forward port 25?

just to fill in that VMWare's SCSI emulation don't support Forced Unit Access (FUA). Meaning that all that is written to disc is first stored in a cache, then flushed and written to the disc.

If i.e. a replication is running in the domain and you got a power failure on the VMWare host, data in the cache (on the DC) is lost and the NTDS.dit database may become corrupt. Most likely leaving the domain in a USN-rollback state since the USN is not correct when you get the DC up and running again.

If you call Microsoft for help and they hear your domain is on VMWare they will say rebuild your domain on fysicals servers, recreate the problem, then we can help you. That is what we support!

If you have good control on your systemstate backups, and is familiar with the restoring process of a domain/DC then I say go ahead with VMWare. It's a fantastic product :)

If you're going to run a DC on VMware, please have a read at this document if you want to avoid problems:
TAC 9710 - Virtualizing a Windows Active Directory Domain Infrastructure

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.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now