General VMM Feedback
Do you have an idea or suggestion based on your experience with VMM? We would love to hear it! Please take a few minutes to submit your idea in the one of the forums available on the right or vote up an idea submitted by another VMM customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building VMM.
This forum (General Feedback) is used for any broad feedback related to VMM.
Be specific on your feedback. The more specific, the easier and quicker for us to review. Please be concise!! For more information, please see User Voice How to FAQ .
VMM Product Team Response is on the bottom right, VMM Product Team Response.
Announcement section is created! This gets updated periodically so stay tuned! We are recruiting VMM customers for TAP. Check new items in VMM Team Announcement.
If you have technical questions or need help with VMM, please try visit our MSDN forums.
-
Easier setup and management of Logical and Virtual Switches/Networks
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).201 votes -
SDN deployed by VMM can be managed through WAC SDN extension
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 VMM159 votes -
"Set-VMNetworkAdapterVlan -Trunk" in the GUI settings of the network adapter
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.52 votesPlanned for VMM 2019 UR3.
-
Please create the possibility to label the VLANs
Today we can only choose which VLAN number to assign.
38 votes -
Manage vRSS, RSS and VMQ from VMM
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.
29 votesRequest is under review for implementation
-
Manage Private VLAN through VMM
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.
14 votes -
HNV Network Virtualization Policy Refresher
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.
13 votes -
monitor traffic bound to SCPortAcl rules
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.
13 votes -
Network configuration delivery
Deliver all network configuration commands as a whole so that the host can process them even if the commands will momentarily disconnect the host from the network. This is most useful when provisioning new hosts that only have two adapters that will be part of a team. Currently the team and switch commands are delivered and THEN the commands for the virtual interfaces, these later commands fail as the host has dropped off the network. This leaves the host without network connectivity and the job fails. Many hosts are using converged network fabrics and being able to provision them without…
10 votes -
Add Port Mirroring
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,
10 votes -
HNV GW Cluster deployment / migration
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
9 votes -
Preconfigure Network Adapter in Physical Computer Profile
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.
7 votesWe are reviewing the feasibility of this feature.
-
Mapping virtual NICs to SET switch Physical adapters
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 SMB1 –ManagementOS –PhysicalNetAdapterName “SLOT 2”
Set-VMNetworkAdapterTeamMapping -VMNetworkAdapterName SMB2 –ManagementOS –PhysicalNetAdapterName “SLOT 3”7 votes -
IP Management
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
8 votes -
Virtual Machine Multi-Queue in Port Profiles
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.
5 votes -
Logical network workflow concept
The creation and management of logical networks, sites, IP Pools, Port Uplinks and VM networks are all related in a VMM configuration but the management of these is very segmented.
As an example it would be better if I wanted to delete a Logical Network then VMM would show me the impact of deleting that logical network. VM's, Port uplinks, Sites etc that are affected and then provide the option to go ahead and clean up the associated resources for that logical network. If this affects the VM or the VM config is broken as a result this would be…4 votes -
Import network configuration to VMM for hosts already configured
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.
3 votes -
Custom Properties for VM Networks (and other objects)
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.
3 votes -
VMM should consider available VMQs when moving VMs in a cluster.
SCENARIO
Please describe the user scenario(s) in elaborate detail
a. When a live migration is triggered by VMM (for example if the dynamic optimizier is enabled) it does not take the number of available VMQs on the target host into account.
VMM may move more VMs onto that host than it has available hardware VMQs.For the above user scenario(s), what is the expected result?
a. VMM should stop moving VMs to a Hyper-V host when the number of available VMQs will be <1 when another VM is moved to that host.For the above user scenario(s), what is the…
3 votes -
Logical Switch - Extend characters from 64 to 128
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.2 votes
- Don't see your idea?