I am a VMware guy who has decided to take the leap over to Hyper-V. I have 1 physical server and the appropriate Server 2016 Datacenter license. It appears that I have 2 choices when installing Hyper-V:
Option 1 - install the (free) 2016 Hyper-V Server, configure it, then (since there's no desktop experience) manage it with Hyper-V Manager running on a remote workstation.
Option 2 - install a full-blown instance of 2016 Server, boot it up and then add the Hyper-V ROLE.
With either method, it is my understanding that any VMs I create from here on out, communicate with this 'parent' Server only. Is that correct? Seems like this is a single point of failure meaning if this parent server goes wonky, I lose all of my VMs and so if it's best practice to ONLY use this server as the hypervisor (that is, do not install any other roles on it such as Domain Services, DNS, DHCP, Web or File Server), it seems like a complete waste of resources (not to mention a license) if the FREE Hyper-V Server gives you the exact same thing.
So I'd like to hear from experts - am I missing something? Or is there a benefit to Option 2? (By the way in the 20740 book I'm studying, I don't even think it mentions the free Hyper-V Server product, and the labs walk you through setting up the first server as described in Option 2).
I've read some articles about how people have tested the performance of option 1 vs 2 and they seem pretty equal. So at the end of the day I suppose I am not looking to get any sort of performance increase. Instead, option 1 seems to have a smaller security footprint and seems to be the closest thing to "just" a hypervisor.
One more Hyper-V question - my server has a RAID 10 with 4.3tb of usable space. When I install the first Hyper-V server instance - do I make one big partition that is 4.3tb and ALL of my future VMs will live inside of this partition? Or ... do I make a partition only big enough to run this Hyper-V server and then create a second partition where all of my other (child) VMs will live?
I come from ESXi where one big VMFS partition is created and then the hypervisor is installed on an internal SD card and you never touch it (unless you're updating the hypervisor itself). Hyper-V, being part of Windows itself, is a completely different animal. I am starting to understand its benefits and I'd like to set this up the best way.
Thank you doctors.