VMware Communities: Sysprep.inf

try this
Put this in sysprep.inf before running sysprep on the original

[Sysprep]
BuildMassStorageSection=Yes

[SysprepMassStorage]
;leave blank

then once the new os is booted run

sysprep -clean -quiet to speed up the boot process


You can do the following:

1) Create your new VM
2) Edit the VM and delete the virtual HD that was added
3) run vmkfstools -i /source_path/source.vmdk / dest_path/dest.vmdk
4) Edit the VM and add a new virtual HD - use an existing VMDK file.
5) Power on your VM and run sysprep, etc.

The reason for creating the VM first is to get all the VM‘s files into one folder. If you create a folder first, then copy the VMDK and then create the new VM, you‘ll end up with 2 folders: NEW_VM and NEW_VM_01.

You can also script this process if you want to do that.


Here‘s the process which I normally follow to clone without VirtualCenter. If you have the VMX file copied, you can right click on the datastore and select browser. Then find the VMX and right click and add to inventory.
1) Create a new VM with the specs you want and a small HD.
2) Edit the VM and remove the HD.
3) Copy the VMDK over from the source to new folder with vmkfstools -i /source_path/source.vmdk /dest_path/destination.vmdk
4) Edit the VM, add a HD and use an existing VMDK file.