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.
-
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 VMM134 votes -
Support Server 2012 R2 Hyper-V in VMM 2019
I know System requirements for System Center Virtual Machine Manager (https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-2019) does not list Server 2012 R2 Hyper-V as being a supported Hyper-V host in a VMM 2019 environment. And there's a difference between "not officially supported" and "officially not supported". VMM 2019 simply does not allow you to install its agent on a Server 2012 R2 Hyper-V server:
Error (20523)
The verslon of the Windows operating system on the computer xxxxx is not supported for a host.Recommended Action
Upgrade the operating system to Windows Server 2016 or a later supported version, and then try the operation…95 votes -
Allow the creation of Service Template Machine Tiers without Sysprep / OOBE
Currently, a Service Template requires Machine Tiers defined by using a VM Template. This VM Template can be preexisting (in the Library) or created in the Service Template Designer.
At deploy-time, VM Templates will always mount an ISO file with an unattend.xml file, containing info like Windows License Key, hostname, IP addresses, etc. The deploy job will sit and wait until the VM is shutdown, which results in the job completing successfully.
Although uncommon, there is sometimes a need to deploy Windows VMs that are not sysprep'd, bypassing the out-of-box-experience (OOBE). An example of this would be in training or…
37 votes -
In SCVMM please add an ICON on the Hyper V host that shows when the Host is in maintenance mode under the "VMs and Services view".
Currently under VMs and Services view, when a host is in maintenance mode there is no icon showing that. You have to click on the host and bring up a menu to see that it's in maintenance mode. It would be helpful if a icon showing the host was in maintenance mode appeared when you put the host in maintenance mode.
10 votes -
Enable nested virtualization for Self Service Users
Nested virtualization requires administrator or delegated administrator role to access.
Please allow this for the Self Service User role.6 votes -
Cluster Overcommitment in VMM should have visual explanation
In SCVMM the overcommit status is not clear althought there is an article from VMM 2012 R2:
https://support.microsoft.com/en-us/help/3023928/details-of-the-cluster-overcommit-algorithm-in-system-center-2012-r2-vIs very important to have a visual / graphical feedback on the overcommitment status.
Example :
In the Cluster properties / General we could have a description like:Not enought Memory to assign more VM's;
Overall CPU consumption over XX%;3 votes -
Can't enable Nested Virtualization from the SPF endpoint
Can't enable Nested Virtualization from the SPF endpoint
Suggesting to add a feature request.We are seeing a behavior where you are unable to enable Nested Virtualization from the SPF endpoint however you can perform this task using PS or the SCVMM console.
1 vote -
Support Cross-Cluster Migrations using S2D/SOFS Storage in Converged Environment
SCVMM (VMM) & S2D should support cross-cluster migration of highly available VMs.
Migrations of highly-available VMs from one cluster to another while using S2D and SOFS as a storage solution (NOT hyper-converged) should be supported by VMM.
VMM has built-in functionality to allow migration of a VM from one cluster to another.
This does NOT work with HA VMs when your storage solution is SOFS on S2D. The VM will be placed in pause-critical, effectively a failed migration.
I believe this is a shortcoming on the part of Failover Clustering not properly handling storage communication, but not sure as this…
44 votes -
1 vote
-
VMM Plugin for Windows Admin Center
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 clouds26 votes -
1 vote
-
Right-click item on VMM jobs to copy the job info.
Provide right-click item on VMM jobs to copy the job ID or other jobs data (Additional Messages). This could be used to paste into emails (for service tickets) or powershell commands (for further debugging).
You can see this information in the jobs list, but you can't copy it (as far as I know).
1 vote -
Allow for IP Pool selection during VM / Service creation (GUI)
You can have multiple IP Pools under a VM Network. When you create a VM (or Service of VMs) thru the GUI, you are not prompted for which IP Pool to use on that VM Network.
I presume it is currently picking the "first" one automatically, meaning whatever one was created first.
3 votes -
Add support for Ubuntu 18.04 in SCVMM 2016
I wanna know if it's possible to add the support of Ubuntu 18.04 inside SCVMM 2016
6 votesWorking to provide this support for SCVMM 2016 and above
-
When configuring memory, make GB be the default instead of MB
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.
4 votes -
Fix the counter in VMs that use "Dinamic Memory" Active.
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.1 vote -
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 -
Make the failover cluster manager VM role names the same as they are named in VMM and Hyper-V
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".
53 votes -
Run compliance check against Logical Switch object and Hosts
Using a Logical Switch object for deployment in a cluster is a time saver and above all mitigates or removes human error by eliminating repetitive tasks. Problem arises AFTER the Logical Switch has been deployed and a modification/change is required, ex; if an additional vNIC is required upon adding it within the Fabric/Logical Switch it is NEVER flagged as non-compliant, hence can never be Remediated. If managing many servers and such a change is required, the only way is to either manually modify each server or create an additional Logical Switch, then remove/add logical switches. This is by no means…
1 voteThanks for reaching out. This suggestion is under review from VMM product group.
Regards,
Nagaraj Venkatesh
Product Manager, System Center
Microsoft -
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.
- Don't see your idea?