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 .

We have VMs with a Self-Service owner. When a different user creates a checkpoint on that VM, within the checkpoint properties, it shows that the checkpoint was "created by" the owner, not by the user that actually created it.

Can we have it so the Checkpoint creator's name is in the "created by" field instead of the VM owner?

When creating a VM from template in SCVMM, the disk name (vhd file) is named the same as the VM name. 1. This makes it match the directory the vhd file is in. 2. Saves a step which if it is missed creates a VHD the same as VHD stored in the library server ("bad"). 3. This will save "errors" if people forget to rename the VHD file prior to creating the VM.

Yes, yes automation with PowerShell or some other product can address this but this should be the default behavior in SCVMM. As if you just spin up a bunch of VM's they all have the same name for the VHD file, which can be confusing. I would think this feature would not be that hard to add during VM creation using the SCVMM template. In a way the SCVMM template does it already for the name of the VM. Just use that var in creating the VHD as well.

When creating a VM from template in SCVMM, the disk name (vhd file) is named the same as the VM name. 1. This makes it match the directory the vhd file is in. 2. Saves a step which if it is missed creates a VHD the same as VHD stored in the library server ("bad"). 3. This will save "errors" if people forget to rename the VHD file prior to creating the VM.

Yes, yes automation with PowerShell or some other product can address this but this should be the default behavior in SCVMM. As if you just spin up…

Powershell modules don't accept wildcard values, like Get-VM -Name 'M*', this is available in PowerCLI on ESX, and is frustrating that it is not available. I can do a filter for results, but I would love to see this added.

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

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.

When deploying a bare metal host, have the ability to load a previous powershell saved configuration to predefine the settings. Useful for minor changes, or building out a configuration step by step. When adding pNIC's and vNIC's there is a lot of configuration that has to be re-entered if your testing different settings.