In Figure 1, when you power on the VM copy, the system asks whether you've moved or copied the original VM. This can cause problems on your network when you run the original and source VM simultaneously. The issue is it's an exact copy, which means the VM's Universal Unique Identifier (UUID) and MAC address would be identical. In theory, if you copy a VM folder you then have a VM clone. VMs are essentially files within a file system. With a VM snapshot, the original state and new state can't run simultaneously, but a VM clone can. Or if you plan to test a certain setup, you can copy the original VM and it remains intact and functional. If you build a base VM with Windows or Linux once and plan to reuse it, you can copy it into a new VM for a future project.

You should first understand their differences, use cases and how to deploy them to avoid any problems.

The VMware Workstation clone VM wizard can eliminate these conflicts with linked or full clone technology. But copying VM files manually comes with its own challenges, such as network conflicts. Because VMs are comprised of files, if you copy those files with virtualization, you create an exact duplicate of that VM. Advances in virtualization have made it simple to create copies of a machine.

Vmware workstation 15 full