Force Parent Disks to stay on specified volume if same file name already exists.
Currently, VMM will place a Parent Disk on the specified "Parent Disk" volume set on the cluster or host.
However, if the Parent Disk VHDX is changed in some way, but does not have its file name updated, the next time a VM is being created, it will fully copy the "new" Parent Disk to the next volume sorted alphabetically instead of appending a "-1" or "Copy 1" onto the file name.
TESTVM has a single hard disk that is set to differencing:
TESTVM-HDD-01.vhdx --> TESTVM-HDD-01-diff.vhdx
When TESTVM is created for the first time, TESTVM-HDD-01.vhdx is copied to the specified PARENT DISK location in the host's Placement Path settings.
Then let's say that changes are made to the original VM and it is re-created and stored in the Library. If the file name of the VHDX did not change, the next time the VM is created, the VHDX files are now different and VMM needs to re-copy the "new" Parent Disk.
VMM (rightfully so) will not overwrite the original file, but instead copies it to a completely different storage volume, typically the next alphabetical one.
I feel it should simply append a suffix to the new Parent Disk's file name and place it on the specified Parent Disk volume.
Users may have storage tiers setup for better IO performance that this could negatively impact.