Dear All,
I cloned one virtual machine of Windows 2008 R2 and I want to use this cloned machine with NEW NAME, I will remove the old machine which I used to clone originally. So, with this intention I used 'no customization' during the cloning process. After process completed I turned on the new cloned virtual machine and found the SID of windows is same as original windows VM (which is now in power off state). All my applications are available but noticed that Windows is again asking for activation key, is this OK ? I just want to be safe that my clone is done perfectly so I can safely delete the other VM from disk
Waiting for response.
thanks,
Yes it is a normal behavior. Even you haven't do any customization during cloning process, windows will still ask you to activate again.
You can check this KB as well.
From KB:
Note: Discussion successfully moved from VMware ESXi 5 to Virtual Machine & Guest OS
Hi ,
When you clone a virtual machine, it asks you what to name the new VM and then it makes all of the necessary changes to all of the filenames. When you copy a VM, all of that information (filenames, directories, etc.) stay exactly the same. But something else happens when you clone an VM that doesn't happen when you copy it. Since VMs are completely software-based versions of an Intel-based PC, they also include a virtual networking interface that, like real PCs, has a unique MAC address (the unique address that helps networks tell network attached device apart from another). When you clone a PC, the clone gets a new MAC address.
So when you copy or clone a virtual machine there is something interesting that happens is when you move an existing VMware-based VM from one computer to another. The first time you try to run that VM, it detects that the VM was moved and asks if you want to keep it associated with VMware's unique identifier (known as the UUID) for that virtual machine, or if you want to create one. According to VMware, if you create a new UUID that will trigger a change to the MAC address which in turn could awaken the licensing Gods at Microsoft.
Thanks for your detailed response explaining. Yes, my cloned VM has new UUID and maintains same SID as original machine. All I want to care now that if I just activate my newly created machine, I am all set to continue using it and move to production environment.
thanks,
Dear All,
concerning above discussion, I need to verify the status of below:
- If a virtual machine have two or more virtual disks (vmdk ) this machine can be full cloned ?
- if a virtual machine is having RDM ( virtual mode), how this affect cloning task ?
- if a virtual machine is having RDM (physical mode), how this affect cloning , it works or fails ?
Thanks for sharing knowledge.
Regards,
Hello,
Re: VMDKs + Virtual RDM
Cloning will clone all VMDKs and Virtual RDMs (they are treated just like virtual disks and just work). All the VMDK features are available including change block tracking etc.
Re: Physical RDM
Cloning does nothing with physical RDMs only VMDKs will be cloned.
Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009, 2010, 2011,2012,2013,2014
Author of the books 'VMWare ESX and ESXi in the Enterprise: Planning Deployment Virtualization Servers', Copyright 2011 Pearson Education. 'VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment', Copyright 2009 Pearson Education.
Virtualization and Cloud Security Analyst: The Virtualization Practice, LLC -- vSphere Upgrade Saga -- Virtualization Security Round Table Podcast