Why "should" one clone a vm via the Workstations "Clone" feature as opposed to just Copying via the OS ?
What's the pro/con ?
for copying via os, you need to know what you are
doing to create a real clone.
with the clone feature, vmware does everything for
hmmm makes sense hahah
Still you would have to updated cloned machine for SID, Computer name, etc. otherwise you would have a "collision" problems when running original and clone/s ath the same time.
If you take a look in your .vmx file you will see the display name of your VM. If you copy, that will be the same in both. If you clone, you get a prompt to change it. Running with the same display name will not create a collission, but it might confuse the user as to what VM they are running.
When you clone your SID is changed automatically. But if you copy, you will be asked when you run it if you want to keep the old SID or crreate a new one.
If you choose to keep the old one, then you will get a collission when you run both the old and the new ones.
The display neame can of course be edited in the .vmx file. And even if you do clone, you will still get a collision when you run both VMs until you run your new change the network name of the new one. If Windows, go to System and change it. If Linux, go to /etc/sysconfig/network and /etc/hosts.
Copying it is perfectly fine as long as you know and account for these things.
Cloning is preferred, as it can also consolidate snapshots and is generally better at guaranteeing a complete standalone VM copy.
ODeckard, I'm guesing you meant to say "UUID" and not "SID"?
Just for clarification, cloning does NOT change the computer SID. Starting up a clone or copy in a new location does prompt the user to change the UUID (and the MAC address), but the UUID has nothing to do with Windows networking SID. The only way to change the SID is to
1) leave the domain, change the computer name, join the domain,
2) use sysprep before cloning,
3) use NewSID after cloning.