Workstation to ESXi migration failure solution

So,
Today I found out a nifty tool. I was being lazy and I just copied a Workstation VM (it was a VM nested within VM Workstation on a over-strained physical production server being used in a production aspect, I like like wha..da...F*ck seriously) and I didn't use VM Converter and I ran into this issue:
"Failed to start the virtual machine.
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0
Failed to open disk scsi0:0: Unsupported or invalid disk type 7. Ensure that the disk has been imported."
So I did a little search and found this solution to SSH directly into the ESXi host and do the conversion. Now yes I could just use the convertor and skip all this, but were is the fun in that????
So I did this:
1. logged into the host over SSH in putty and logged in.
2. type: 'cd /vmfs/volumes/<datastore name>/<vm-folder>'
3. then I typed 'vmkfstools -i vm'sdisk.vmdk -d zeroedthick vm'sdisk1.vmdk'
4. then I just waiting about 10 minutes for it to convert.
5. then I just typed 'vmkfstools -E "vm'sdisk1.vmdk" "vm'sdisk.vmdk"' to rename the file back to the original name
6. typed 'ls' to confirm the change in the CLI and then Powered on the VM and whalla!

me lovin' the cli land of VMware
Today I found out a nifty tool. I was being lazy and I just copied a Workstation VM (it was a VM nested within VM Workstation on a over-strained physical production server being used in a production aspect, I like like wha..da...F*ck seriously) and I didn't use VM Converter and I ran into this issue:
"Failed to start the virtual machine.
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0
Failed to open disk scsi0:0: Unsupported or invalid disk type 7. Ensure that the disk has been imported."
So I did a little search and found this solution to SSH directly into the ESXi host and do the conversion. Now yes I could just use the convertor and skip all this, but were is the fun in that????
So I did this:
1. logged into the host over SSH in putty and logged in.
2. type: 'cd /vmfs/volumes/<datastore name>/<vm-folder>'
3. then I typed 'vmkfstools -i vm'sdisk.vmdk -d zeroedthick vm'sdisk1.vmdk'
4. then I just waiting about 10 minutes for it to convert.
5. then I just typed 'vmkfstools -E "vm'sdisk1.vmdk" "vm'sdisk.vmdk"' to rename the file back to the original name
6. typed 'ls' to confirm the change in the CLI and then Powered on the VM and whalla!

me lovin' the cli land of VMware
