Look, I know this has been asked a million times before, and the literature is abundantly clear that:
Having a Hyper-V 2008 R2 Host machine as a domain member of a domain which has its only domain controller installed as a guest VM of said machine can create an issue when failure occurs to the DC and prevents logging into the hyper-V host. So called failure loop caused by the fact the login server can't be accessed because its one of the affected VM's.
I was wondering though, wouldn't just having access to a local administrator account for the Hyper-V host prevent all of this cacophony?
The reason I ask is that its quite handy having the 2008 R2 Hyper-V host as a domain member of SBS 2011 hosted domain, as that way you can access update and security status ETC from the SBS Console.
Could somebody also please confirm that in Hyper-V for 2012 and 2012 R2 this 'loop' issue has been resolved entirely now?
Kind Regards, Paul