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.

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.

When you go apply a classification to a VM's Virtual Disk in the GUI, the drop-down menu sorts things in an incoherent manner.

It appears that Get-SCStorageClassification also returns results in the same order.

It also does not appear to sort based on propreties ID, AddedTime, or ModifiedTime.

Can we at least get the VMM GUI to sort results? (Powershell can obviously be done manually.)

Image attached demonstrating issue.

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?

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 VMM is using unattend.xml for domain joins for VMs and Hyper-V hosts. This contains having unencrypted passwords stored as cleartext at some points of time during the deployment.

We would prefer using offline domain join instead - as it was done for nano server in the past.

It would be great if the Operating System list was something the administrator could define, but in lieu of that, add FreeBSD and OpenBSD as additional OS options for VMs.

Much like Windows Admin Center, a suggestion I would like is in the VMM Help menu, to link directly to User Voice, for user feedback. This would be handy.

When creating somwthing like a VMNetwork, the jobs window always pops up, can we make a preference in systems to not open a jobs window by default.

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

When I'm switching from basic session mode to enhanced session, the VM Console is shown behind the main SCVMM UI

We should be able to resize the VM Window, and the guest OS should change his resolution accordingly

I have different libraries in different locations, on different speed networks. Some locations are deduplicated, some are not.

For me, if I want to move an item from the library to another, I have to "deploy" to a cluster, then "store in library" again to the destination library.

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.

very annoying having to build a whole new profile just for testing a minor change, especially when there is a complex network setup.