I'm asking this question as someone who has worked with VMWare, and has a tiny amount of time playing with Citrix XenServer.
I'm spinning up Hyper-V Server 2012 R2 for lab testing, and there is something I don't get. Why is Hyper-V Server so focused on having the server as part of a domain?
Normally, I'd want my hypervisor (in my mind at least) *not* to be on a domain (something that of obviously isn't an issue with ESXi or XenServer). I don't know what physical machines I'll have apart from the hypervisor (small organization) and I'd rather have the hypervisor be stand-alone, and then my VMs can be on the domain. However, I've found right away that this seems to create management issues that require workarounds to connect to them using a single Hyper-V Management console.
This doesn't bode well for me, because the network I have inherited has multiple domains (one at each location). If I make them Hyper-V, I can't easily use the management console as easily from my one traveling laptop, because it might not be on their domain.
I'm not the most experienced sysadmin in the world, but it seems a little counter-intuitive to not make it simpler whether your base hypervisor is on a domain or a workgroup. Or is it just me?
Everyone gets everything he wants. Me, I wanted to be a sysadmin. And for my sins --they made me one.