Cuando se activa la memoria dinamica en las VMs, se afecta el UI de la memoria RAM sobre el "Administrador de tareas" y los contadores de rendimiento.
El tope del porcentaje de la memoria, debería seguir siendo el maximo y no el asignado por el VMHost, Ademas de esto, la tasa de consumo no debería verse afectado por el consumo del controlador, esto debería ser ignorado ya que, cuando se analiza el consumo de una VM dentro de ella, no se sabe realmente cuanto esta consumiendo sin programas adicionales como RAMMAP.

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.

When configuring memory for a VM, make GB be the default instead of MB. These days I think everyone would save some clicks and time if this was implemented.

I wanna know if it's possible to add the support of Ubuntu 18.04 inside SCVMM 2016

Would like to see a plugin In Windows Admin Center for SCVMM so that administrators can perform VM and Host Management tasks from a web based interface rather than depending on the MMC console.
Also it would enable self-servicing by giving the ability for delegated administrators or tenants to administer their own VMs and also create their own VMs under their clouds

Customer is sometimes 'ok' state. And other times, 'overcommit' state, even without changes in environment.

SCVMM 2016 UR4, Standalone VMM environment of 12 Nodes.
He has 192 GB free when he calculates all his HOST's free memory including the reserve node's (R1).

https://support.microsoft.com/en-us/help/3023928/details-of-the-cluster-overcommit-algorithm-in-system-center-2012-r2-v

* What we might really need here is logging of how 'ok' and 'overcommit' was calculated so the toggle between both states is understood.

Currently when you create a VM in VMM it adds a prefix and suffix to the role name when created in Failover Cluster Manager. "SCVMM *ServerName* Resources" for example.

When I name a VM, I want the name to stay the same no matter where I am looking. (Hyper-V Manager, Failover Cluster Manager and VMM.) If I name a server "JoesWebServer" I don't want it to change in FCM to "SCVMM JoesWebServer Resources".

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.

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.

Since Windows Server Container Support. It should be possible to create Containers and Hyper-V Containers with SCVMM. Also suggesting to integrate Kubernetes Management Board Integration into SCVMM since Kubernetes Support Windows Containers.

I find it frustrating when I'm moving a lot of resources around, to have to clear out the "missing" items from the library. Library should be just treated like file explorer essentially. When its gone, its gone. If people like a audit trail, the offer a "keep history for x days" then show as missing......for x days. That would be better.

The requirement for running sysprep when preparing VM Templates (with Windows) looks a bit confusing, because as soon as you start converting finalized VM, the status changes to 'Sysprepping...'.

If VMM could do sysprepping on it's own, I'd like to be able to skip doing this step in my Task Sequence, because one of the last steps I'm doing is applying some hardening GPOs, which in turn, cause sysprep to succeed only after a subsequent reboot (and automating one is quite a challenge as apparently MDT doesn't like something that's being touched by the hardening policies)

Update the VM and Hosts Dashboards management pack that was released for VMM 2012 and SCOM 2012. This Management Pack can no longer be imported into a SCOM 2016/VMM 2016 monitoring scenario.
System Center 2012 R2 Management Pack for Virtual Machine Manager Host and Virtual Machine Dashboards
https://www.microsoft.com/en-us/download/details.aspx?id=43707&WT.mc_id=rss_alldownloads_all

Without this Management Pack the usability of SCOM for monitoring the Hyper-V Hosts and VMs is virtually non-existent

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”

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.