New build is available.
This release includes bug fixes and a new User Interface to manage advanced Hyper-V Virtual Switch features.
Support for Multiple Parent Virtual NICs
- Virtual Network Manager GUI was enhanced to support multiple virtual switch ports bound to the management operating system virtual NICs. This functionality is available only for hosts running Hyper-V 3.0 and can be accessed via the Virtual Network Manager ‘Ports’ button on each Virtual Network Properties view.
- Parent Virtual NICs can be created for any virtual network (switch) using the ‘Add’ button on its Port dialog box. This operation can effectively change the type of the virtual network, i.e. parent Virtual NIC added to the Private network will change it to Internal etc.
- Virtual switch ports, corresponding to parent Virtual NICs ports, can be deleted using the Port’s dialog box ‘Delete’ button. This operation can also change the type of the underlying virtual network, i.e. Internal virtual network can become Private, or External virtual network can stop sharing its physical adapter with the management operating system.
- When ‘Access host through VLAN’ is checked in Virtual Network Properties all parent Virtual NIC ports will use the same VLAN ID defined in the Virtual Network Properties view.
Support for Hyper-V Virtual Switch New Security Features
- Port Access Control Lists (ACLs) can be defined for Virtual Switch ports bound to virtual machines and the management operating system virtual NICs. This functionality is available only for hosts running Hyper-V 3.0 and can be accessed via the Virtual Network Manager ‘Ports’ dialog for each Virtual Network Properties view (use ACL button to edit port’s Access Control List).
- ACL entries specifying which packets are allowed or denied on the way into or out of the VM or the management operating system can be added, edited or deleted for each applicable port. Multiple ACL rules can be configured per virtual switch port. IPv4, IPv6 addresses or ranges as well as MAC addresses can be used to designate endpoint addresses on local or remote interfaces along with actions ‘Allow’, ‘Deny’ or ‘Meter’. Meter action can be used only with IP addresses.