ASKER
ASKER
ASKER
Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.
TRUSTED BY
1) Create a team with the 2 NIC's.... create a virtual switch in hyper-V. That way you get fault tolerance for all your VM's and the host connection.
2) Allocate one NIC for the host and one NIC for the VM's... no fault tolerance - but very simple to setup
3) if you need higher throughout, create a network team as LACP, configure the switch to support LACP, then you will get fault tolerance and higher throughput.... but realistically, i doubt that is required if your only running 2 VM's
For me - i keep things simple with most clients - and go with option 2. Most of the servers we use have a minimum of 4 ports - so we can choose to dedicate a port to a VM if its needed... in enterprise clients its a different story.... but for 2 VM's... i would keep it simple.