My plan is to install Hyper V Server 2012 on my new server then put Windows Server Essentials 2012 into it (which will have AD, DHCP etc). My question is do I need to connect my Hyper-v to a domain or leave it in a workgroup? It's like the chicken and egg!
Hyper V 2012 server advice
- Thread starter GodAtum
- Start date
Soldato
- Joined
- 11 Oct 2008
- Posts
- 3,833
- Location
- London
The hypervisor is irrelevant in this case.
You may need to be on a domain to use the Hyper-V role, but I can't imagine why that would be a prerequisite.
The important part is how you set up the virtual network for the Windows Server Essentials guest OS. This cannot be on the same domain anyway so the point is moot.
You may need to be on a domain to use the Hyper-V role, but I can't imagine why that would be a prerequisite.
The important part is how you set up the virtual network for the Windows Server Essentials guest OS. This cannot be on the same domain anyway so the point is moot.
Personally I wouldn't join the host machine to the domain, because the domain controller is going to be a guest of the host. The host will take a lot longer to boot if it's a member of the domain as it'll be trying to contact a DC, which won't be accessible, because it won't be running yet. Consider the fact that, if you were using any other hypervisor (Xen, VMWare etc), it wouldn't even be an option.
Good point. I've been trying both Hyper-V server and Vmware, I cannot even connect to my hyper-v server using the Windows 8 management tools! Apparently there is a lot of configuration one needs to do to be able to connect! VMware just works for me.