<div>
Thanks for verifying before i go with it!
</div>


Thanks for verifying before i go with it!

<div>
<div class="content wysiwyg-content">
I have 2 physical nics, each with 4 ports. <br />
<br />
I was going to use 2 ports on each adapter for my NIC Team. Since this Server ONLY does Hyper V Hosting, should i leave it as Switch Independent and Dynamic Balancing, or should i actually use the Hyper V Port balancing method? Some Technet articles seem to point out dynamic is still better in general, but i am not sure if that applies for exclusive hosting of virtual machines. <br />
<br />
Server 16 is that matters. Thanks.
</div>
</div>


I have 2 physical nics, each with 4 ports. 

I was going to use 2 ports on each adapter for my NIC Team. Since this Server ONLY does Hyper V Hosting, should i leave it as Switch Independent and Dynamic Balancing, or should i actually use the Hyper V Port balancing method? Some Technet articles seem to point out dynamic is still better in general, but i am not sure if that applies for exclusive hosting of virtual machines. 

Server 16 is that matters. Thanks.

NIC Teaming on Hyper V Host

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.

Windows Server 2016

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.