Today we are kinda locked-in when it comes to service templates and deployment of those. I would like to see more flexibility here, such as:

• dynamically add/remove tiers and instances to an existing service template


• better management capabilities of the entire service and each individual tier, such as live migration, patching, and DSC integration

Also Service Templates and VM Templates should use tags, Familiy name and versioning to use Disk instead of attaching them directly

currently is only about PowerShell possible to add a network adapter with an existing VM and assign the IP Address from a IPOOL. This standard task should be included in the GUI.

Remove VMware integration , Remove V2V and so on , and focus on the features set in Hyper-V.

today polling remote hyper-v hosts takes alot of bandwith , the ability to set poll frequency based on a host/host group would be a great option , or add the ability to set a host to push so it only pushes changes to reduce load

Make Service Templates in SCVMM interoperable with Gallery Items in the WAP

Since MS announced support for Docker, make sure SCVMM will support docker container deployment from day 0

I think it would be great if instead of pretty useless "overall MB\s" and "monthly storage MBPS" we could see an overview of available resources for a host group:
- Storage (Used\Available for Placement)
- Memory (used\available for new VMs)
- Top N hosts running out of resources (3-5 hosts)
- Top N free hosts (2-5 hosts)

If a Hyper-V cluster is created with VMM you can only create a Standard Switch on all Hyper-V hosts. It would be better to select a Logical Switch here.

Another pain point is the assignment of a static IP address to the cluster. In the 2012 R2 release sometimes it works that the option will be visible sometimes not. A drop down menu where I can choose between DHCP or static assignment would be better.

When working with Baselines for patching, it's possible to choose "All hosts" so all new hosts are automatically added to that Baseline.
But there is currently not possible to also pick "All infrastructure Servers" or "All PXE Servers" so when a new server of that type is added, it's automatically included in the baselines just as a host would be.

It would be great if VMM could use the pre-approval groups and rules already setup in WSUS.

When it's technically possible to move a VM with both Live Migration and BITS, then make it possible to choose which method should be used for that transfer.

In this moment a library must be on a Window Server and this is not good because for vhdx, iso, scripts and more could be used share on a remote storage, like QNAP or others, where the agent cannot be installed.

today a host refresh thats read only locks a change on a host/vm , changing so a read only jobs dont prevent any changes from being applied , and que jobs if locked instead of failing them

Can't find anything on this topic in docs. I have a lot requests for this and can't answer with an official statement

Update console is too "poor" because I can't see who many servers need a specific update and if the update is obsolete or not. The console must be improved like WSUS

When creating a new share against a Windows File Server through ther VMM GUI the share is created using the SMB Share - Quick profile. This profile selects the options to allow caching of the share and is not the recommended share type per Microsoft. The recommended profile to use is SMB Share - Applications.