Installing VMWare on a Domain Controller

I tried to install VMWare on a Windows 2003 server accting as a DC and received the message it is strongly recommended that you DO NOT install VMWare on a DC. Doers anyone know why this is. I do not want to ignore the message and install if it is going to cause problems on my network.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

probably because if you ran two or more instances of a domain controller on the same network, massive network conflict errors would occur. some recommend using GSX version of VMWare or installing VMWare on normal 2003 server first and then promoting it to a DC... only recommended if the DC has enough power to run it all.

It's likely that VMWare are trying to protect you from introducing - as you mention yourself - issues within your network.

Your DC is performing a critical job and you really don't want to deploy anything onto it which could affect the main services it provides - While a very capable suite of products, VMWare Workstation etc. can be very resource hungry when running and will definately affect not only the general responsiveness of your DC but also unneccesarily reduce the other resources (such as RAM) available to the services being provided by your DC.

Install it on a decent spec workstation instead (2Ghz+ and a minimum of 1GB RAM is a good starting point..)

Hope that helps..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I thinkk fostejo is correct -- the problem is loading down your domain controller.  

asian_niceguy's comment is wrong.  It is highly recommended to have two or more domain controllers on a network, so if one falls over you still have the other.  However, there is no reason to suppose that a VMWare virtual machine on a DC would itself also be a DC.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.