W2K3 Licensing issue after P2V conversion

Using Microsoft's Disk2VHd, I did a P2V conversion of this MS W2K3 standard based DELL system. But, after the system booting up, it prompted with the windows licensing activation probem. In order to continue, I click Yes, and the error message occured:

   This copy of windows must be activated with microsoft before you can continue. You cannot log on until you activate windows.

It also stated that the current product key is invalid. So, I double-check the product key, or even change to use other product key, no matter how many I tired, it shows me "invalid activiation key". Called to Microsoft support also ended with wrong key.

This is an valid Product key, a Microsoft Windows Server 2003 OEM. Do I have to change to use a VL copy on hyper-v?
LVL 1
MichaelBalackAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

n4gaaCommented:
FYI OEM licence is lock to the hardware of the computer that it ship with, what is the host os  that you are moving the  virtual machine to
0
MichaelBalackAuthor Commented:
W2k12 standard
0
n4gaaCommented:
Then you need a new key for the VM if you have  VL copy that should work
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

MichaelBalackAuthor Commented:
Hi n4gaa,

I've tried several to change to use valid VL product keys, and still it shows me the invalid activation codes. Do i have to run the "repair" using this VL CD or modify any registry keys?
0
MichaelBalackAuthor Commented:
Hi experts,

any suggestion?
0
Lionel MMSmall Business IT ConsultantCommented:
The issue is that the OS knows that it an OEM install. A repair with a VL CD may work or it may not. I would give it a try. Having gone through a similar process in June I eventually just started from scratch and installed a new install of W2003.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gurutcCommented:
We've done the repair with the VL CD and key many times with success.

Good Luck,

- gurutc
0
gurutcCommented:
But make sure you have both VL CDs if you have 2, you may need the second CD.

Snapshotting the new VM before you start is a good idea in case it takes more than one try and you want to start the fix again.

- gurutc
0
gurutcCommented:
Also, if you had IE8 on the physical before the conversion you may need to uninstall it after the P2V so that IE6 takes over and allows you to run windows update.  The repair install to fix the license rolls back all the patching so you'll need to do a huge windows update session.

- gurutc
0
MichaelBalackAuthor Commented:
ok, I will give it a try and I will be onsite next week...
0
gurutcCommented:
Super, Good Luck.

- gurutc
0
SteveCommented:
a physical OEM license you had on the physical server cannot be transferred to a VM.

If the windows OEM sticker on the server has a 'virtual' key you should use that to get the VM activated.

You should also check the VM licensing model you are using, as the hyper-v host OS version dictates whether you have rights to use 'included' VM licenses or need to license them separately.

You MUST have valid licenses covering all VMs, or included VM rights with the hyper-v host's OS.
0
MichaelBalackAuthor Commented:
It works, just one repair and bingo, not more activation prompting
0
RicDzCommented:
Hey Guys-

Can you tell me what repair command you used for this? I have having the exact same issue. I have my server booted up in the Recovery Console
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.