Physical hyper-v server is also a domain member. is this OK?

[edutech4schools]

Seen on another post that it is not a good idea to have the physical hyper-v server as a member of the domain, rather it should be a standalone unit. The reason was given that you might not be able to access your physical hyper-v server if the main DC goes down.

 

In one of my primary schools I do have a hyper-v server and it is on the domain. Should I be worried?

 

My setup

Server 1 = Physical DC with all FSMO roles including Global Catalogue

Server 2 = Hyper-V role + a few other none critical roles and is a member of domain

Server 3 = Virtual DC (for DC backup) which includes Global Catalogue but none of the other FSMO roles and is running on Server 2 and is obviously a member of domain.

 

Can I not simply login locally to the hyper-v server if no DC servers are available?

Edited March 13, 2014 by edutech4schools

[localzuk]

Being a member is fine, so long as you have another server which is providing AD services. In your setup, its fine.

 

We have 2 Hyper-V servers as AD members, as we have a physical AD server (as well as a virtual one).

[sparkeh]

You'll be ok as you have the physical DC.

I tend to leave my hosts as standalone just in case.

[AngryTechnician]

Can I not simply login locally to the hyper-v server if no DC servers are available?

It depends on what storage you are using. If you are using Cluster Shared Volumes then having no DC up will play merry hell with Hyper-V and lead to the situation you've been warned about. If they are simply stored on local disks, without a shared volume, then you can boot and log into the physical host just fine even with no DC available using the local Administrator account (assuming it isn't disabled).

[detjo]

I did this with 2008 R2 and it proved to be a pain, so I ended up joining it to the domain. In 2012 R2 it works a lot better, apparently, if its not domain joined.

[edutech4schools]

Thanks for all the replies.:thumbup: