Converter and Windows activation

[StefanoChiappin]

Hi,

I'm running my ESX 3.5 during the 60 days trial mode, and during this period I need to test our main servers in VM mode. For this reason I donloaded VMWare Converter 3.0.2u1 and converted two Win2003 server. But at the en of the job I was unable to login onto the new VMs because windows "must be activated". Is there a way to perform the conversion by exactly cloning the two systems, without asking for activation ? This conversion is for test only, so I cannot dismiss the real server by now. What I would like to do is convert the real server comlletely, keeping the same names, IP, etc, then switch off the real servers, power on the VMs and see if all goes ok. So, I will not run the real and virtual machine at the same time, but I need to keep the real servers ready and activated.

Is there a solution for this issue ? Thanks and bye, Stefano

[sfont3n]

i bet your physical OS is an OEM license. If so, boot the vm with the OS disc, then run a repair on the os and enter a volume license key

[admin]

Use the customization option to invoke Sysprep. This will allow you to enter in a different license.

If your original license was an OEM license, then you're stuck. You can't swap in a volume license key when the original installation used OEM media.

[sfont3n]

yes you can swap an oem license for a volume license. i have done it at least 10 times. once you get the oem server converted, boot the vm with the volume license cd, run a repair on the OS and change the key there. it has worked everytime for me

[admin]

That's good to clarify that you mean going through a repair process. What I meant was when Windows requires a reactivation, you can't put in just any license key-- if it was originally an OEM license the dialog won't take a volume license. Doing a repair, or in an extreme case, a reinstall, can lead to some items potentially changing on the system, unlike a standard conversion using Converter.

[StefanoChiappin]

Hi,

please can you explain me wich command to give once I enter the recovery console ? I didn't find any in the help list.

Thanks, Stefano

[sfont3n]

dont go to the recovery console.

just do it like a fresh install it will find the previous OS install and run a repair

[StefanoChiappin]

Hi,

but if I perform a fresh install and choose the same partition/folder of the present win installation, the installer warns me that the present installation will be deleted, together with "My Document" folder. I tried to go on pressing the "L" key (accepting the deletion) and in fact I got a completely new VM, with the old OS destroyed, wich was not what I was looking for. Fortunately I had a shapshot. :smileyhappy:

Maybe I'm missing something... please can you explain me step by step your procedure ? Thanks.

[sfont3n]

oh yeah u missing something

boot to the OS cd

welcolme to setup press enter

press f8 at license agreement

then at the next screen hit r and just let it do its thing to windows starts to load.

so thats all it is

[StefanoChiappin]

Umhhh... that's the issue: after F8 (license agreement) I have no "hit R" choice, instead I have a screen where to choose which partition to install in. Then I select C: (where is the old Win2003) and in the nwxt screen I'm warned about another system installed being overwritten. I can only select Continue (C) or Cancel (ESC). If I go on, I'm propted how to format the C: partition ! I do NOT format it, then the last screen asks whether delete the content of C:\WINDOWS directory, or choose another dir. If I select Delete (L) I get the old installation destroyed. :smileysad:

I'm using a Windows Server 2003 Enterprise Edition disk.

[sfont3n]

i do too use w23k ent

[OsceolaVCP]

Hi all-

I've done quite a bit of these too, make sure you use VLK media of the same edition of Windows to get the Repair option (Web,Std,Ent)

Also, be sure to select "Install Windows" (don't hit the 'R' option, this will open the Repair Console). After accepting the EULA the installer should search for and detect an earlier installation, and then give you the option to repair that installation.

Hopefully this helps!

[ajdelo]

Hello all.

I received the same activation error, but when I boot the VM from the Windows XP CD and select to Setup Windows, I get the error, "Setup did not find any hard disk drives installed in your computer."

I'm running ESX 3.5 with Virtual Center and booting the VM from an XP CD on my local laptop. The datastore is located on local disks.

[OsceolaVCP]

I just did another P2V and had the same issue. Download and mount the SCSI driver floppy and press F6 on boot to load the SCSI driver from floppy. This should resolve your issue. On another point, I found that doing the repair installs all non-updated system files to the Windows installation, you'll need to reapply updates via Windows Update or a WSUS server.

http://download3.vmware.com/software/vmscsi-1.2.0.4.flp

[ajdelo]

Worked like a charm. Thanks. I just wish Micro$oft would come out with XP SP3 already so that there aren't 125 updates to install after installing SP2. Go figure.

[OsceolaVCP]

Sounds good, glad to help.

[milo365]

I converted the OEM server but there is no way to boot this VM with the OS disk. I never get to the point where I hit can hit Enter, then F8, I hit enter and the Windows install tells me it can't find any hard disks, even though I can boot the VM normally to the point where it wants me to reactivate Windows.

[milo365]

The issue with not being able to boot the VM from the VOL LIC OS disk was related to the default SCSI driver the VM thought it needed. It was trying to use the BusLogic driver. Windows 2003 Server needs the LSI Logic driver. I turned off the VM and edited the properties of the VM and chose the LSI driver. The VM booted with the Volume license disk and allowed me to run a repair install and did take the new Vol license activation code. All is well now. Thanks to all for your input.