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).

That’s a major issue that there is no support for DFS-R to keep different VMM library servers in different sites in sync or up to date. If we can use DFS-R for it that would be a good step forward.

Add the ability to control failover and enable replica from VMM without the dependency/cost of Azure Integratio

please add the ability to multiselct and do "anything" aka shutdown move and so on , having to select a vm at a time for some functions is very time consuming

We're discussed this but I want to say it again: it's VERY annoying to click Repair->Ignore every time...

We need a brand new Management Pack that sets the reference for fabric monitoring. No more OpsMgr SDK dependencies to take into account managed service provider scenarios.

SCVMM gets itself in a mess, Cluster Manager knows were the VM's are SCVMM think's it knows and you get in a situation were you can't fix it. Its so frustration...

Add VHD Set support in VMM. Support for shared VHDX and now VHD Set has been requested for years, yet VMM ignores this critical feature.

One of the greatest advancements of VHD Set over shared VHDX is the ability to migrate vhd set, yet VMM has no support for this.

Please add VHD Set management (create, attach, dettach, migrate ....) to VMM.

There must be complete monitoring of Hyper-V Replication from the VMM Console, as it is in the Hyper-V Manager.
Currently VMM does not understand/recognize the replica VMs after the installation of UR5.
The VMM administrators must be able to have real-time monitoring of Hyper-V Replication and all other related tasks (Pause, Resume, Resynchronize, etc.) that are availble in the Hyper-V manager Console.
There must be a column against the Vm on the VMM Console which should be describe that a VM is Primary or Replica.

I like to see what performance counters on Hyper-V hosts and VMs on the following components:
- CPU
- Memory
- Network
- Disk

These performance counters can be viewed in a graph for a day, week and month trend.

It would be nice to see what are the top hosts and VMs on CPU, memory, network and disk I/O in realtime in SCVMM without the use of SCOM

Addin functionality to add a VM to a DPM protection group on creation (Template). Make it fairly simple like the ASR integration. View protection group / DPM server in console without custom fields.
You could have a backup group for DPM servers in fabric computers, and assign them to host groups.
If a cluster or host group is protected by DPM, install the agent onto new hosts as they are added.

Fix the issue with using the DPM and VMM module at the same time maybe.

When ConfigMgr is available, make sure the product can opt-in and leverage that functionality

sometimes i need to use the console view to connect to the VMs desktop. But the console view in VMM is not as good as the viewer in FCM or Hyper-V manager.
Please make the console view the same as in the other management tools (i. e. Insert Integration Services disk, Start, Stop VM, etc.)

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, ...)

We are regularly faced with inconsistency in the database or we need to remove a cluster or a node but can't because VMM simply refuses. Repairing the database is risky and unsupported and once in while things get messed up. I'd love to see a tool which tests for VMM database inconsistency and a way to clean up

Let us use "group managed service accounts" for both a RunAs account, as well as the user under which we would install and run SCVMM.

Today we can only choose which VLAN number to assign.

Today we badly miss a Comprehensive patch managemt nsolution for the datacenter. SCCM is focused on single system patching, VMM just Patches the fabric and has many shortcomings. Today we use custom Scripting Solutions that are hard to mantain.
VMM is the place where to implement the datacenter patching, we need:
- maintenance Windows
- ability to set different environments (test, pilot, poduction at least)
- ability to set relationships between systems
- great compliance reporting
- straightforward tshooting logging and tools
- ability to have pre and post custom actions
...
- service dependencies (

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.

at least this should be displayed within the "about" dialog.