• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 123
  • Last Modified:

Hyper-V host on the domain when DC is its guest

I only have one license of Windows server 2012 R2, and I am running 1 DC and 1 file server at a remote location.
Do I want to put this host on the domain whose DC is its guest?

It is a very small environment, so I really don't need 2 DCs. I am wondering if I leave the host as is (workgroup), or put it on the domain.
0
Member_2_7970390
Asked:
Member_2_7970390
5 Solutions
 
Cliff GaliherCommented:
With 2012 and newer, both are options. I prefer joining to the domain as management is he really easier. But 2008 era folks still get nervous, so personal preference.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Agree with Cliff.  I literally just got home from setting up a system and I joined it to the domain.  But there's not of a difference either way.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Our preference for standalone Hyper-V settings is to leave the host in a workgroup.

While not foolproof, it offers a bit of a security barrier between the production network and the host which is vital to that network's functioning.

Our primary reason though is it just works.

Management is done via RSAT, RDP inbound rules on the firewall, or Intel RMM/iDRAC Enterprise/iLO Advanced.

EDIT: RSAT method requires some changes via John Howard's HVRemote setup. We don't use RSAT we just log on. :)
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Tarmo Kabonenit managerCommented:
It is a bad choice to add Hyper-V host to domain if there is no second DC out of the host itself. There is no good way to get updates from GPO when guest (DC host)  is down “yet” when system is restarting. Yes, it can be updated manually, but it is not a good solution to do it. If You have one extra DC outside of this host, then it is OK. I would recommend not to join host to domain and leave it as workgroup.
Other issue is time drift in the domain if guest is only DC and host is domain member. You HAVE to leave synchronization of system time inside of Hyper-V guest settings unchecked, it keeps whole domain system time steady.
0
 
Member_2_7970390Author Commented:
Dear all,
Thank you for your comments. First it seemed that it would be easier to manage if I put the hyper-v on the domain, but there may be potential issues like kapsionu pointed out. So I decided to leave it without joining the domain.

Now I just have to go through how to manage the host from another 2012 R2 machine. It sounds a bit complicated, but it is just one-time thing.
0
 
Tarmo Kabonenit managerCommented:
RDP and port forward is enough, RSAT is a little bit overkill if no vpn or dedicated connection between locations involved.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now