Windows Server Standard 2012 R2 -- HyperV licensing ?

Do you recommend DHCP/DNS/AD/etc on the
HOST server OS or the HyperV virtual server OS ?

Is the below #4 doable or do I need to install
DHCP/DNS/AD/etc services on one of the
TWO HyperV virtual servers to be legal ?

 1. purchase ONE Windows
     Server Standard 2012 R2 license
 2. install Windows Server Standard 2012
     HOST on ONE 2-processor physical server
 3. install TWO HyperV virtual servers
 4. install DHCP/DNS/AD/etc services
     on HOST, not on the VMs
finance_teacherAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Cliff GaliherConnect With a Mentor Commented:
#4 is neither recommended nor would it be legal if you are purchasing standard edition. The 1+2 virtualization rights only allow the host to be the hypervisor. No other roles are allowed to take advantage of 1+2.
0
 
Matthew BorrussoConnect With a Mentor Commented:
Best practice for a windows hypervisor is not for the core OS to operate as a domain controller.

here is MS licensing page.
http://www.microsoft.com/licensing/about-licensing/virtualization.aspx#tab=1

but this is what you need: this should make sense. but in short, in your scenario, your licensing falls short of compliance.
http://download.microsoft.com/download/E/6/4/E64F72BF-55E9-4D85-9EFE-39605D7CE272/WindowsServer2012R2_Licensing_Guide.pdf

with regards to number 4. if you do not have a domain controller running on a different box, then you may want to either consider not making the hypervisors domain members, or if you do, make sure you have local admin accounts in case the DC guest is not running or have problems. I highly recommend against putting anything other than the hyperv role on the base hypervisor OS. Let the Hypervisor operate as lightweight as possible, that's its job.

check this out.
http://www.altaro.com/hyper-v/reasons-not-to-make-hyper-v-a-domain-controller/
0
All Courses

From novice to tech pro — start learning today.