Virtualize a Running System

[jonander83]

Hi!
So, I have this very old server running windows 2003 on HP hardware.
The thing is that I wanted to virtualize the current state of the machine and discard the physical one.
After a lot of time looking around and trying to find the way to do so, I decided to go like this:

1: Use vmware vCenter Converter to dump a clone of the current machine status
2: Use vmware's ovftool to convert the VM to .ova
3: Import the .ova with virtualbox

But the problem is that when I start the VM, I get prompted with the windows activation dialogue.
Now, I have the license number on a sticker on the real machine, but I don't really know what to do or if there is a way to bypass this and keep the old license.

I have found some tool named "sysprep" but I didn't really understand it's usage and I'm not really sure if this is what I need to look into.

Any help would be much appreciated

[mpack]

Your conversion method was not ideal. You should Google for "P2V site:forums.virtualbox.org", as we've had this exact discussion more times than I care to remember.

And yes, the VM is running on different hardware (albeit simulated), so retail XP and later will indeed ask to be reactivated. No, there is no way to bypass it - and anyway I'm not sure why you'd want to.

Sysprep doesn't do anything you need doing. It allows someone to tag their Windows image as requiring a partial reinstall, including a new key. The PC can then be imaged and the image distributed. It allows admin types to create ready-made custom image of Windows all set up for a particular task, distribute it to end users, but each install instance will still require a unique CD-key and separate activation, thereby satisfying legal requirements.

[jonander83]

Yes! I mean, I successfully boot the system. i don't have the hal problems (I documented myself first)
The problem is with the licensing issues. I don't know how to proceed this step, and it's not documented (or I didn't come across it)
Thanks for your help, though

[mpack]

First, you don't need to activate right away. You usually have 30 days grace period to decide if this is what you want.

You can also change the CD key in the VM before activation. You'll need a new CD key from the same family (e.g. retail XP. An OEM XP key will not work. Or vice versa). Google for how.

With the appropriate CD key installed you can then follow the normal activation procedure. From that point on you'll be obliged to stop using other copies of that installation (i.e. the physical machine).

[jonander83]

It does not give me the option to try for 30 days, it's either activate via internet, via telephone or switch off.
And there must be something going on with the network, since it can't connect to microsoft to authenticate...
Weird.
I'll try.
Thanks!

[scottgus1]

I virtualized our SBS 2003 via a fresh install in the Virtualbox guest and a swing migration. I used the license code on the sticker on the physical server. It reactivated just fine.

if your ova transfer gives you a running guest that is asking for reactivation, then run with it. Maybe not the optimum Disk2VHD method, but hey it's running. Try the codes on the side of the physical machine and see what you get.

[jonander83]

I virtualized our SBS 2003 via a fresh install in the Virtualbox guest and a swing migration. I used the license code on the sticker on the physical server. It reactivated just fine.

if your ova transfer gives you a running guest that is asking for reactivation, then run with it. Maybe not the optimum Disk2VHD method, but hey it's running. Try the codes on the side of the physical machine and see what you get.

How did you do that? When installing your network device is not detected from the beginning, you have to log in to install new hardware and you need to activate to login, and you can't get past the activation screen. I had to give up completely

[mpack]

Scottgus obviously didn't have the same problem, but you could have used telephone activation.

[scottgus1]

When installing your network device is not detected from the beginning

Hmm. Sounds like the network card being simulated is not one that Server 2003 has built-in drivers for. I made a new guest with the Windows 2003 template and found the network card is the "PCnet-Fast III". XP has built-in drivers for that card. I surmise that Server 2003 does too, and could get to the internet with it. If your guest is using a different card, shut down the guest, change the network card type to the PCnet-Fast III and restart the guest. Report back what happens.

[jonander83]

Nope: Changing the net card didn't do it.
I'll try to activate by phone: Wish me luck, since the license is for a dell computer: I don't know if I'll be able to go through with this...

/offtopic: Then, they complain about piracy: I have more things to worry about than a silly license that I already paid and want to transfer to new hardware. I bet I'll end up having to take the fast lane here, since I read somewhere it's not possible to license a 2003 server via phone as of today (mid 2015)
I hope that posts are wrong.
Wish me luck. Thanks for the help

[ikar.us]

I read somewhere it's not possible to license a 2003 server via phone

Why don't you simply try it?
Why haven't you tried right in the beginning?

[mpack]

Wish me luck, since the license is for a dell computer: I don't know if I'll be able to go through with this...

It would have helped if you had mentioned that straight up. Some royalty OEMs, and Dell in the XP era is the most notorious example of this, have a completely different activation mechanism. In fact there is no online or telephone activation at all - your PC must simply have a supported Dell BIOS, which of course a VM does not. This explains why you didn't get 30 days, since if course the BIOS is going to be no different in 30 days time.

These licenses are what is referred to as "node locked" to a specific PC (or at least a specific model).

I suggest that you go on eBay and find yourself a genuine XP Pro OEM license to use in your VMs. Genuine XP licenses are quite cheap now. Avoid name brands (HP, Dell etc), upgrade editions, recovery disks etc. Avoid any mention of SP3 (the disk can't be genuine). Ideally the package is still new (shrink wrapped), with hologram and COA sticker.

[jonander83]

So, I can forget about virtualizing the machine I guess.

The main problem was that this machine has an old software licensed with a usb dongle and i didn't want to activate the vm without checking the dongle was going to work on it.
Now, I guess I'll have to forget about virtualizing it and just try to install it from scratch.

Thanks for the help anyway