Using Hyper-V with a Domain Controller

Building a new server. Are there any issues with using Hyper-V on a Domain Controller? I'm new to Hyper-V but have plenty of experience with VMWare. Thanks!
Who is Participating?
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.

Are you asking if you can add the Hyper-V role to a domain controller or put a domain controller on Hyper-V?

It generally isn't recommended to install the Hyper-V role on a DC. It is possible but if you are looking for ideal security, performance, and other best practices it isn't recommended.

Running a DC virtual works however if you have your Hyper-V on the domain and your DC has issues then you could be in for a headache especially if you use another 2012 server as a shared storage space (like a VMware datastore. Server 2012 can even act as a cheap low-end SAN solution) for VM files and VHDs as authentication is needed for the VMs to access the shares and if the DC is down authentication won't work so the VM won't boot. It's a vicious circle. This is (in my opinion) the one major downside to Hyper-V.

Here's a couple things you may want to read for more info:
WineGeekAuthor Commented:
This is a new server I'll be building. I've been told that there could be problems having a domain controller on a hyper-v box.
WineGeekAuthor Commented:
My boss bought this client a server with Hyper-V on it but now is asking me to do all this research to find out if there are any problems creating hosts VM's as domain controllers on it.
If it is a small client I'd do it and leave Hyper-V out of the domain. From my previous link

Keep the Hyper-V servers out of the domain

In small deployments you can consider just leaving the Hyper-V servers as part of a workgroup and then running all domain controllers inside virtual machines.  This approach has two problems.  First, you lose the security advantages of running in a domain environment and second, it is hard to have multiple administrators in such an environment (as local user accounts need to be created on each Hyper-V server).  Also, you cannot use all the functionality of SCVMM in such an environment.

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
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
Microsoft Legacy OS

From novice to tech pro — start learning today.