VMware VM Clone via HTML5 Client Results in Incorrectly Configured VMDK
This one is just a quick post regarding an issue I came up against just before Christmas.
To get straight to the point, I found an issue where in multiple separate environments, when cloning a virtual machine via the VMware vCenter HTML5 Web client interface, if you select the tick box to “customize this virtual machine’s hardware” and change any of the settings of the VM, the cloned virtual machine’s VMDK file(s) will be pointed to the VMDK file(s) of the source machine you used for the clone.