I am designing a solution to move users to Office 365 / RemoteApp With a Dirsync connection back into the on site AD servers to handle local logins / local file server.
The plan is to have two Hyper-v servers (for resilience) for local Linux based apps and to also house the Active Directory servers on them. The problem is that Hyper-v would need to be a member of the domain it is running as a guest.
It could be possible to run an AD server on Azure basically just for these servers to authenticate to while they boot, but that seems complicated.
Ideally we just want to have those two servers on site. Is there a way around this that I'm missing?
So if the only AD servers that are available are Hyper-v guests, and everything is initially turned off. How do I start the (domain member) hyper-v servers, before the Domain Controller guests that they are running have started.
Best Answer
Windows Server 2012 R2 Hyper-V Failover Clusters support DC-less bootstrapping, so the Cluster will bootstrap without needing a DC to be available, so there's really no "chicken or the egg" scenario. There's really no need for an Active Directory-detached cluster. Create your DC VM's, create your AD domain, join the Hyper-V hosts to the domain and create your Failover Cluster.