asked on

Domain Controller, DHCP, etc -- HyperV VM vs HOST ?

I will be upgrading my domain controller hardware
and the below articles act like it is find to put
the domain controller, DHCP, etc functions on a
Windows Server 2012 R2 HyperV VM, not a
Windows Server 2012 R2 HyperV HOST

Does anyone have a reason to "NOT"
put these functions on a HyperV VM ?
==========================================================
https://technet.microsoft.com/en-us/library/virtual_active_directory_domain_controller_virtualization_hyperv(v=ws.10).aspx

http://www.altaro.com/hyper-v/reasons-not-to-make-hyper-v-a-domain-controller
http://www.altaro.com/hyper-v/demystifying-virtualized-domain-controllers-part-1-myths
http://www.altaro.com/hyper-v/4-reasons-your-hyper-v-host-should-only-run-the-hyper-v-role

Lee W, MVP

You can have a physical DC if you like...
But you CANNOT make your host a DC and a Host. No professional with experience will advocate that.

SOLUTION

Justin Ellenbecker

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

hecgomrec

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Lee W, MVP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

hecgomrec

Is always nice to here from big corporate IT staff how they don't really understand or see the small owner try to deal with overheads and cost-effective procedures. Well thanks GOD the big OS companies doesn't totally force owner to change their machines every 4 year when their new version is out and they allow us somehow to update the current running software in a 4 years old computer.

Anyways is good to know there are still some people out there they think everything is running in the latest available technology.