Domain Controller -- Windows Server 2012 R2 HyperV ?

I have 100 users with little activity.

Which option do you recommend the
"Domain Controller" be installed
on since I have HyperV VMs for
everything else ?

  Option #1 = install DC on a VM

  Option #2 = install DC on a VM Host

  Option #3 = install DC on a physical, non-VM machine
finance_teacherAsked:
Who is Participating?

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

x
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Option #1 = install DC on a VM
Depends on the Hyper-V host.  2012 And later have the host aware of the potential that the only DC is in a VM.  Generally, if you are using Hyper-V then call me old fashioned, but I'd like to have ONE physical DC and the rest can be Hyper-V VMs... but it's not a strict rule... I've done only Hyper-V VMs as DCs before and it's fine.

Option #2 = install DC on a VM Host
NEVER.  EVER.  Research the number of times on Experts-Exchange a similar question has been answered and you will find no respected expert will EVER recommend this option.  Among other things, it kills a VM license in 2012... possibly BOTH.

Option #3 = install DC on a physical, non-VM machine
If you have the spare hardware, sure.  Have a DC that's hardware only... but it's not strictly necessary.

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
infedonetworkCommented:
I like option 1 for the reason that if something go wrong on the DC and you need to connect remotely you can rdp to the host and work on your DC from there. Safe mode or other.
It happens more than once to me.
If it's on a physical server you have to be on site to deal with.
Cliff GaliherCommented:
Unless the host is the server having issues. The logic there is flawed. For better remote supportability, get a server with iLO (HP) or DRAC (Dell) or similar. Independent from the OS, hardware level, IP KVM is superior in almost every way to relying on RDP when an OS issue arises.
infedonetworkCommented:
Agreed but how many time do you have problems with a host?
Personally I never did with the host but did multiple times with DC or exchange.
I'm not saying that the host never had problems but due to the fact that all it run is hyper v the it has less problems than a server running multiples roles.
I just suggest the less expensive way that has the best chances.
If he has the budget to dedicate a physical server to the DC and has drac built in then that's a better option
Tony GiangrecoCommented:
One Physical DC is our standard and the rest virtual. It has worked out very well for us. Hope this helps!
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
Hyper-V

From novice to tech pro — start learning today.