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 .

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.

Currently the update management of Storage Hosts is partially limited in VMM. You can add these hosts as "infrastructure hosts" and VMM will handle them as standalone hosts. When using this way to install updates VMM is not cluster-aware and is not aware of S2D and others.

This should be improved to be able to update storage hosts s2d- and cluster-aware as this is the case for hyper-v hosts.

An easy to use web based management option like App Controller should be provided for VMM 2016. Setting up Windows Azure Pack just in order to give internal customers e.g. developers a tool to manage their VMs seems oversized.

All options on the memory tab in any VMs properties are inactive (grayed out), yet virtual computers running Windows 10 and Windows Server 2016 support hot add and hot remove of memory. It works through Hyper-V Manager but in SCVMM it's not functioning.

TL;DR - Is there any chance that VMMAgent will ever use SMB Multichannel for file transfers?

I understand that VMMAgent does stuff over 443 (or 80 if specified) for file copies. If there's an ODX-capable storage provider, then it will leverage that. Otherwise, it will try "Fast File Copy" and then BITS over HTTPS (or HTTP if specified).

In a multi-NIC environment, couldn't VMMAgent be improved to be a little "smarter"? If there's a faster route, use it. The ODX functionality is already built in to pass transfers over various protocols depending on providers, why not extend this to SMB Multichannel?

TL;DR - Is there any chance that VMMAgent will ever use SMB Multichannel for file transfers?

I understand that VMMAgent does stuff over 443 (or 80 if specified) for file copies. If there's an ODX-capable storage provider, then it will leverage that. Otherwise, it will try "Fast File Copy" and then BITS over HTTPS (or HTTP if specified).

With options like Dynamic Disk and Memory allowing you to get the most out of your resources. It would also make sense to allow end users to oversubscribe resources.

Turned off Virtual Machines count towards cloud limits and therefore users cannot easily switch between workloads in a lab environment without an offline Library. When users work with multiple VMs for a test and can switch multiple times in a day it makes little sense to force the Library usage as they cannot export VMs from the Library until the cloud is clear enough. This leads to countless lost hours waiting for VMs to import and export from the Library.

With options like Dynamic Disk and Memory allowing you to get the most out of your resources. It would also make sense to allow end users to oversubscribe resources.

Turned off Virtual Machines count towards cloud limits and therefore users cannot easily switch between workloads in a lab environment without an offline Library. When users work with multiple VMs for a test and can switch multiple times in a day it makes little sense to force the Library usage as they cannot export VMs from the Library until the cloud is clear enough. This leads to countless lost hours waiting…

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.

Please can you either allow the 'Virtual Machine Viewer' text to be removed or reduced to 'Viewer'. When you have multiple Virtual Machine open the task bar doesnt allow you to see which machine is what because this text fills the whole section.

When adding a new Windows 2016 Hyper-V cluster to SCVMM, all VM's deployed to the new Windows 2016 cluster automatically deploy from SCVMM as a configuration version 8.0 machine. In order to allow time to upgrade all other Hyper-V Servers still running Windows 2012, it would be good to have the option to have a choice of configuration version of the VM. This is currently only possible if creating a VM directly on the Windows 2016 Hyper-V server itself. When creating VM's directly on a Windows 2016 Hyper-V server one can use the cmdlet "New-VM" and specify the configuration version using "-Version". The problem is that you cannot migrate any VM's off a Windows 2016 Hyper-V server back to a Windows 2012 R2 Hyper-V Server without the configuration version being 5.0. If any of our new Windows 2016 Hyper-V servers had an issue we will be in deep trouble, being unable to migrate any configuration version 8.0 VM's off to any other of our Windows 2012 R2 Hyper-V servers. Please consider adding this same option to SCVMM (New-SCVirtualMachine) and Windows Azure Pack (New-WAPackVMRole). This would be extremely helpful to maintain VM's across SCVMM, while we make progress in converting to Windows 2016 Hyper-V across all infrastructure.

When adding a new Windows 2016 Hyper-V cluster to SCVMM, all VM's deployed to the new Windows 2016 cluster automatically deploy from SCVMM as a configuration version 8.0 machine. In order to allow time to upgrade all other Hyper-V Servers still running Windows 2012, it would be good to have the option to have a choice of configuration version of the VM. This is currently only possible if creating a VM directly on the Windows 2016 Hyper-V server itself. When creating VM's directly on a Windows 2016 Hyper-V server one can use the cmdlet "New-VM" and specify the configuration version…

Assume you want to change VM configuration. For example, change vCPU count, allow migration to different CPU version, change MAC address type (dynamic/static), attach FC adapters and may be others. All of this actions require to stop VM to perform this changes.

I want to suggest option that allow make this changes in VMM and postpone it to put to VM until it reboots.

When LM a VM to a different cluster using VSM, and if the VM has more than one VHDX attached and I want to place each disk on a different CSV. migration fails with an access denied error. Migrating the same VM to one CSV succeeds.

In some cases customers work on dedicated admin workstations a local VMM Console installed. In these scenarios it's important to keep the console up-to-date, if possible in the same version as the VMM Server. It would be great if the VMM Console notifies the user if he's using and older VMM Console version.

Admittedly, in this case, the title of the article for the hotfix does not imply that it fixes our specific replication issue which was caused by UR12 but when we call in and are told it is a "known Issue", it would be nice to "Know" it is a "known issue".

This has caused business risk for us since we do expect replication is happening in case of recovery so if this replication is not happening, we are at risk with downtime.

I realize communication can be an area of "you send to much" or "you don't send enough". In the case of known issues... I'd rather know of one and ignore than to not know and be troubleshooting.

It would be helpful to have an RSS Feed or email distribution so when "known Issues" internal to microsoft are "known", the community in general will also know.

for example, there was a hotfix for an issue created with UR12 for system center affecting replication. Our engineering team had to open a case with microsoft.

Admittedly, in this case, the title of the article for the hotfix does not imply that it fixes our specific replication issue which was caused by UR12 but when we call in and are told it is a "known Issue", it would be nice…

Presently, a Hyper-V Failover Cluster can have a cluster reserve state of OK or Over-committed. It is boolean.

Instead, I would like to see a measurement or percentage showing how close it is to over-commit, or how much it is over-committed. This measurement would dynamically update based on changing the number of Cluster reserve (nodes).

Currently the Create Logical Unit wizard offers two options:
thin provisioned and thick provisioned.
Please add 'Thin provisioned and deduplicated'
Or give each storage pool a default settings option, in which the new LUN defaults for that pool are saved (thin/thick, deduplication, compression, ...)