I just started using Oracle’s VirtualBox for the first time this past weekend. Tumor De Ampolla De Vater Pdf. Shortly after creating my first Virtual Machine with a Windows 7 guest, I created a clone just to test out this functionality.
I was surprised to find out that within the clone, Windows 7 had to be re-activated. Crime Life Repack. After doing some digging, I found a pretty simple way to create VMs so that the clones do not require a second activation.
See the instructions after the break. Warning: Following these steps may violate your license agreement with Microsoft.
In many cases, you are only permitted to install a single copy of Windows on at most one machine. I believe this includes virtual machines. Please consult your sales representative to ensure you that are in compliance with your license agreement. How to create a VirtualBox VM so that a clone does not require re-activation of Windows.
Create a new Virtual Machine for Windows 7. Do no install the operating system just yet! Locate the vbox file of the VM you just created. Open the file in a text editor and locate the “Machine uuid”. In the example below, see that the machine uuid is “ 02f110e7-369a-4bbc-bbe6-6f0b6864ccb6“.
Some of you have been asking if it can be done in Virtual Box as. Run XP Mode in VirtualBox on Windows 7. A way to activate XP Mode through VirtualBox using. Follow these steps to clone a VirtualBox VM in a manner so that the Windows 7 Activation in the guest doesn't have to be re-activated in the clone.
Typically when you clone a VM, a new machine uuid is generated.. In the next few steps, you will generate a new uuid that will not change when a VM is cloned. Thus, Windows will remain activated in each of the clones. Use one of the following sites to generate a new uuid: • • • For this tutorial, I generated the uuid of “ dbc5316a-2600-4d6e-8964-a07f3de5ded8“.
Open a command prompt and execute the following statement: C:Program FilesOracleVirtualBoxvboxmanage modifyvm –hardwareuuid In my example, the statement looks like this: C:Program FilesOracleVirtualBoxvboxmanage modifyvm 02f110e7-369a-4bbc-bbe6-6f0b6864ccb6 –hardwareuuid dbc5316a-2600-4d6e-8964-a07f3de5ded8 6. Open the vbox file and verify that a new hardware “version 2” uuid was created. Sorry – I used &tl; and >in my post, which got filtered out here replaced by brackets Tried several versions now and found one, that did the trick nicely: When cloning a vbox do NOT create new MAC Adresses for the virtual network-adapters. After creating a clone of a registred Win7 vbox BUT NOT starting it!!! Do the following: # vboxmanage showvminfo “[name of my master installation]” find the lines containing the string ‘UUID’ you could simply grep for it like this: # vboxmanage showvminfo “[name of your master]” grep UUID UUID: df1XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXe6 Hardware UUID: df1XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXe6 notice, that both are identical! Now set the “Hardware UUID” of the newly created clone: # vboxmanage modifyvm “[name of your clone]” –hardwareuuid “[the uuid you just found out]” and add the Hardware UUID to the BIOS Image of your clone: # vboxmanage setextradata “[name of your clone]” “VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid” “string:[the uuid you just found out]” now check: # vboxmanage showvminfo “[name of your clone]” grep UUID UUID: 8a4YYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYb9 Hardware UUID: df1XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXe6 notice, that those are no longer identical!
The UUID is only needed and seen by VirtualBox programs so this dosen’t matter. Now you should be able to start your clone and have it still registred.
Tried several versions now and found one, that did the trick nicely: When cloning a vbox do NOT create new MAC Adresses for the virtual network-adapters. After creating a clone of a registred Win7 vbox BUT NOT starting it!!! Do the following: # vboxmanage showvminfo “” find the lines containing the string ‘UUID’ you could simply grep for it like this: # vboxmanage showvminfo “” grep UUID gives you two lines: UUID: df1XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXe6 Hardware UUID: df1XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXe6 notice, that both are identical! Now set the “Hardware UUID” of the newly created clone: # vboxmanage modifyvm “” –hardwareuuid “” and add the Hardware UUID to the BIOS Image of your clone: # vboxmanage setextradata “” “VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid” “string:” now check: # vboxmanage showvminfo “” grep UUID UUID: 8a4YYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYb9 Hardware UUID: df1XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXe6 notice, that those are no longer identical! The ‘UUID’ is only needed and seen by VirtualBox programs so this dosen’t matter.
Now you should be able to start your clone and have it still registred. I’ve followed the entire thread and did some unsuccessful experiments (windows 7 and apps appear unactivated in cloned vm).
I am dubious about some of the claims that are being made. Perhaps someone could elaborate and straighten me out. To begin with the MS algorithm that checks whether activation is required looks at the hard drive UUID amongst other things, correct?