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.

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

bikini sites

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.

When deploying a VM from a template, I rename the boot disk the template is made from to "system.<fullvmname>.vhdx" because I do not want the disk created as "<vmtemplatename>.vhdx. If there was a way to setup a rule to do this, it would be nice.

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.

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.

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

When pushing a VMM 2016 UR4 agent to an infrastructure server. If the infrastructure server has an existing certificate bound to HTTPS, example RDSGateway and Network Controller. The agent installation will remove the existing certificate binding when setting up BITS.

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)

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.

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.