So now that I decided to use iSCSI on the host, i'm stuck with going with a GUI instead of core of
Windows Server 2008 R2 because Drobo does not support core installs.
ISCSI is standardized and ca nbe set up from the command line. Why do you Need a GUI on the Hyper-V Server because of Drobo not supporting core? This doesn't make sense.
Being that its more resource intensive
Häh? A non trivial Hyper-V Server has so many ressources the 100mb or so mroe RAM needed ythe GUI is - nothing. Like NOTHING. Plus you can always use Server 2012, with gui, then remove the GUI - that is possible on 2012. Given all the HGH Advantages of the nwe Hyper-V Version, why anyone would install a old Server 2008 R2 for Hyper-V is osmething that I fail to unerstand. SHort of I do not know what I do".
Keep the server updated with Microsoft updates.
Install anti-virus/security Software
What for, on a Hsper-V role? As noone except admins ever should log in and nothing except bare bones Software (Drivers, backup Agent, System Monitoring) should ever be installed on a Hyper-V Server, why have a antivirus System waste time? It will not protect the virtual machines anyway.
Enable firewall and block unused ports
Yes. Or you make sure the Server itself has no contact outside the operational adminsitrative VLAN for Hyper-V Hosts.
Have the host not join a Domain
Home single Server install? Wrong place here. Otherwise, sorry, run a separate Network for the infrastructure. My own small Company has a separate Domain for infrastructure, Hosting only stuff like WSUS, central file shars (ISO Images) and - Hyper-V Hosts. Access to the Hyper-V Hosts is isolated by Routing policies and a separte VLAN and Management Network.