Allow a Virtual Switch to connect to the Microsoft Hosted Network Virtual Adapter. Other virtualization products allow this; Hyper-V doesn't. This is a severe limitation.

Hi,

Please allow LACP configurations for NIC teaming in virtual environments. This is a possible solution. The only allowed option is "Switch Independent", which is limiting to me. I run LACP configurations in my VMware environment for all my 2012R2 servers now, no issues from this design. Allow me to do this again please.

Thanks,
Nick

It would be nice to allow devices behind the NAT to access ipv6 resources as well externally. Right now this is not possible and as such the default switch for example, sends traffic out only if something is reachable via IPv4.

I found a strange problem with a host WS2012R2 (HP Proliant DL 380 g9 with 1 NIC 4 ports) during Teaming creation. For an astral reason, when I create a team, Windows assign the same MAC Address to Team NIC and also to Hyper-V Virtual Switch; the result is the total fail of everything.

Why Windows Server 2012 R2 hasn’t a pre-check task to understand both NIC have the same MAC Address? Much better is check the MAC Address of the entire host.

It is more clear the vmware strategy to create portgroups on a vswitch that specifies the VLAN. All VMs connected to that portgroup are connected to same VLAN.

What is the point on defining per VM, you are allowing users to create VM and they have to guess what is the VLAN id.

Please review this and allow move VLAN VM definition to the vswitch.

There should be an option to chose the physical NIC or team one would want to send the Replication traffic thru while using kerberos for authentication. It can be achieved while using certificate based replication. but not in an AD environment.

Enable on Hyper-V Manager options configure VLAN on vSwitches.

Add functionality in Hyper-V GUI to create host vNICs and manage them rather than requiring Powershell.

When vSwitch is created from Hyper-V console or Posh, minimumbandwidthmode is absolute.