The configuration and setup of Logical Networks and Switches are hard for administrators to learn and understand.
There is need to simplify this and also provide a graphical overview for how things are connected on a logical level. (the current build in view is not good enough).

Currently SDN deployed using VMM cannot be managed outside of VMM. WAC has a SDN extension which is useful to monitor, troubleshoot and manage SDN.
It will be super useful to be able to use WAC to monitor / manage SDN deployed through VMM

Today we can only choose which VLAN number to assign.

There are times when you need to give the virtual machine a trunk-port. This has to be done through Powershell: Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList xxx -NativeVlanId yyy
I would like to add the option in the GUI settings of the network adapter of the virtual machine for easy of use.

As Hyper-V nodes hardware is almost the same DC it will be very useful if we can control advanced network adapter configurations from VMM. As Jumbo Frames, Buffers, vRSS for Mnagement OS adapters, RSS and VMQ settings are the same in large DC for every host.

These settings could be controlled by VMM Logical Switch and Uplink Port Profiles.

We use Private VLANs in our Hyper-v Clusters but currently all the management of Private VLANs in all modes (promiscous, isolated, etc) have to be done by using Hyper-v powershell commandlets. We would like to be able to manage this completely through VMM.

Allow Policies of HNV gateways to be refreshed / reset for all or certain networks. Frequently virtualized networks get outdated and there is no way to reset the policies on all hosts / gateways or do any troubleshooting at all.

It would be nice to create a tool that will provide a real time monitor and ability to find past details for blocked and allowed traffic when SCPortAcl Rules are used. Connectivity filtering relies on firewall traffic monitoring for troubleshooting puproses so it is essential to have.

Dear VMM Team,

The protected Network and Port mirroring configuration is missing in VMM Port Profiles virtual network adapter.

Please add those two options so we can manage all vNICs from a single console.

Thank you,

Ease the deployment of the HNV Gateway deployment. Now you can only deploy it through Service Templates. They are subject to many errors during the deployment. Also there is no way to easily migrate networks between gateways. there should be a option for that too

As SET switches don't support LACP

By default an algorithm is in place to affinitize a vNIC to a Physical network adapter when they are in a team (LBFO or SET). This algorithm does not always do the things you want, If I have two storage NICs created on my vSwitch I would like them affinitized both on a different physical adapter.

Set-VMNetworkAdapterTeamMapping -VMNetworkAdapterName SMB_1 –ManagementOS –PhysicalNetAdapterName “SLOT 2”
Set-VMNetworkAdapterTeamMapping -VMNetworkAdapterName SMB_2 –ManagementOS –PhysicalNetAdapterName “SLOT 3”

Customers cry out for the ability to see which VM has what IP in a easy format. Short of writing custom powershell would be good to just have it within the GUI

Configuring the network adapter of the bare-metal is configurable only after deep discovery has been made. like makeing the nic not registering with DNS option.

Physical Computer Profile mostly does alot of time, but only able to preconfigure the network adapter in detail.

Hyper-V 2016 adds a new feature called Virtual Machine Multi-Queue that allows a since VM to have multiple VMQ queues assigned to it to increase throughput. However, this can only be enabled by going into Hyper-V itself and not through VMM. It should be added as a new checkbox to the "Offload Settings" section for Virtual Network Adapter Port Profiles.

I think managing the network configuration should be simpler in the sense if you configured your Hyper-V clustering network prior to using VMM. You should be able to add VMM to the mix afterwards and it import how the network is already configured. Not being forced to have to use VMM to setup the network from the beginning if you want VMM to manage it.

As of today we've the possibility to add "custom properties" to some objects available in VMM (i.e. Hosts, Templates, VMs, ..) but it's not available for other/all objects.

It would be great to make these custom properties available across all objects like VM networks and others for which they're not available today.

The Logical Switch name are limited to 64 characters.
For the implementation with CISCO APIC we need more as 64 characters e.g. 128 characters for the Logical Switch name.
The CISCO APIC delpoyed the Logical Switch with a compex naming convention e.g. TenantName | APIC Name | EPG Name | Logical Switch Name.

HNV Allow the option to forward a port range. Ex: 4000:4111