A virtual machine or template having the same name is already registered. Server Error: The specified key, name, or identifier already exists.

[GSS11]

Hi All,

I have an esxi 5.5 server running just the one vm for now. I try to clone this as per below:

http://nchrissos.wordpress.com/2013/04/22/cloning-a-vm-without-vcenter-in-esxi-5-1-free-edition/

However, I get the error:

A virtual machine or template having the same name is already registered. Server Error: The specified key, name, or identifier already exists.

I have no vcenter (yet), and this is just the 1 vm. The vm is off. I get this error regardless of the name I specify when I choose "add to inventory".

Any advice appreciated.

Thanks

[SatyS]

Execute the following commands in the service console in the ESX Server.

• service mgmt-VMware restart

• service VMware-vpxa restart

• service VMware-vmkauthd restart

-Remove all the VM configuration files like vmx,vmdk for the particular VM

-Rename the source VM before cloning and then clone.

-Reboot the Server.

Hope this helps.

-SatyS

[continuum · Accepted solution]

Oh dear ...
first you read poor tips in the internet and then you also get stupid tips here.

Ignore both !!!

If you want to clone a VM by copying it - do it like this:

Create new VM with the wizard.
Skip creating a disk for the new guest.

In Datastorebrowser copy the original vmdk to the new dir that was just created by the wizard.
Reopen the new VM and edit it - assign the vmdk you just copied.

The procedure from the blog is not expected to work.
Satyas tip is not making sense either

[GSS11]

Thanks for that, continuum. However, I now have an issue that the second vm asks for windows activation? The original vm was already activated, however.

[steveb05]

From a Microsoft Licensing perspective, you must license both systems. Activation creates a hash using different hardware identifiers. When you clone a machine, some of the components of the hash change. That is why you are bing asked to activate.

To continue continuum's answer, you should sysprep the system after making a copy and also ensure your MAC addresses are different in the VM config. Using his process, they should be different...but just make sure so you don't get any weird connectivity issues.