Licensing problem on Server 2003 after Virtualization

I'm having a somewhat disturbing problem on my citrix servers.  At random (at least I can't see a pattern) I am seeing licensing and windows activation errors and staff cannot launch Citrix applications hosted there.  This morning I am getting this on one of the servers:

A problem is preventing windows from accurately checking the license for this computer. Error code: 0x80040057.

I can't even login to the console.  After investigating this I've found the cause.  These servers used to be physical Dell machines and were converted to VMs running on VMWare ESX.  The license for the original operating systems were OEM and now that they are on virtual hardware I'm getting the activation problems.  Its odd that this only started happening about two months ago and they were converted to VMs more than a year ago but I believe that is the source of the problem.  The only solution I've found so far is a reinstall of the entire OS which I'd like to avoid.  Is there an easy way out of this one?  One would think that with the popularity of virtualization that there would be a painless way to convert the OEM licenses over to something that will run in VMWare but if there is I haven't found it.  I would greatly apprecaite any advice, thanks!
LVL 1
First LastAsked:
Who is Participating?
 
Ayman BakrSenior ConsultantCommented:
If you have a MAK key for your Microsoft servers then you can run the folowing two commands by opening an elevated CMD:

slmgr.vbs /ipk <MAK Key>
slmgr.vbs /ato


You need to be aware that using slmgr.vbs doesn't try to activate automatically over the internet. So you have to follow it with slmgr.vbs /ato.
0
 
Lee OsborneCommented:
You can also check this KB article for a couple of other options:

http://support.microsoft.com/kb/918342

If you don't have many servers to do, the Product Activation method may be the easiest (modifying the OOBETimer registry entry).

Lee
0
 
First LastAuthor Commented:
What I found worked best was to modify the hosts file on each server to prevent it from reaching out to MS and doing a license check.  I wish MS made another way available to me but they kind of forced my hand with their crazy licensing schemes.  Thanks for the tips guys.
0
 
First LastAuthor Commented:
Found alternate solution
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.