HyperV Server not a member of domain

I have a server 2012 set up as a stand-alone server outside of our domain as a hyperv server. All of the member virtual servers are a part of a domain. This has not appeared to be an issue. I turned off firewall on hyperv server remotely and lost my ability to connect remotely. It appears that I will have to re-enable from console.

My question is... what are the advantages and disadvantages of having your hyperv server setup outside of domain. Is this a good idea/ bad idea?
Who is Participating?
Svet PaperovConnect With a Mentor IT ManagerCommented:
There is no good or bad scenario. It all depends on your requirements.

However, there are some common rules:
- If you have all domain controllers on the Hyper-V, you don’t put the host in the same domain
- For better security, it will be wise to place the host on desiccated IP segment (VLAN) and separated Workgroup or domain

To get Hyper-V Manager access to a Hyper-V host that is not part of the same domain, you need HVRemote http://code.msdn.microsoft.com/windowsdesktop/Hyper-V-Remote-Management-26d127c6
KCTSConnect With a Mentor Commented:
If the server is offering services to domain clients then it makes sense for it to be a member of the domain, that way you can manage it and deploy policies etc to it as you would any other domain member.
PJL2Author Commented:
Since there was no real answer to question as posed... splitting points between the 2 people who bothered to respond. Thanks.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.