Server 2003 Enterprise Activation problem.

Client has a running Server 2003, enterprise edition machine.  Don't know if this is from volume or retail media..

Previous consultant illegally installed using an invalid license key.  The machine is activated, but refuses to install SP1 due to the bad key.

We purchased a license for the machine but are having problems changing the license key.

I've attempted to change the key by modifying the OOBETimer data.

When I re-launch the activation tool, it reports that the machine is still activated.

Anyone seen this?  How can I change the license key?

Thanks!


LVL 7
scdavisAsked:
Who is Participating?
 
redseatechnologiesCommented:
Petri has a VBS script to do this as well, which would be worth looking at;

http://www.petri.co.il/change_the_serial_in_windows_xp.htm

It is also entirely possible that the new key you have is not compatible with the version of windows installed (the version installed could be an OEM version, or a retail version, or a manufacturers version - while the new key may not be)

In which case, a reinstall may be the only way forward.  Which is what I would suggest anyway - if someone has installed a cracked version of windows, who knows what else they have done

-red
0
 
redseatechnologiesCommented:
Hi scdavis,

Macig Jellybean's keyfinder has an option to change the key;

http://www.magicaljellybean.com/keyfinder.html

There is also the MS way (ignore that it says XP)

http://support.microsoft.com/default.aspx?scid=kb;en-us;328874

Hope that helps,

-red
0
 
scdavisAuthor Commented:
JellyBean lets me view the product key, but the Change option is not enabled.

Microsoft script returns a generic error 0x80041001

0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
scdavisAuthor Commented:
Sorry - Ressea's suggest of using the VBS scripts didn't answer the question.  

0
 
redseatechnologiesCommented:
Well then the new key you have is incompatible with the version of windows installed, reinstall windows, as recommended in my previous post.

If you really dont want to do that, you could call MS and pay their $500 fee to try to help you over the phone.  My bet is they are going to tell you to reinstall anyway though

-red
0
 
scdavisAuthor Commented:
Darth,

None of these people answered the question.  Please leave the question OPEN until someone actually answers it, or declare it unanswerable.  It's not appropriate to award points to someone that didn't actually answer the question.


I want to put this on the record, again, because it isn't clear, I think:

The installation will not let me enter a new key.  Dosen't matter what it was initially, as there's no apparent way to input the new (legal) OL key.

To Repeat:
- msoobe registry changes don't work.
- magic JellyBean won't allow change of the key (option is greyed-out)
- VBScript reg mod returns 0x80041001, as I noted above.


Thanks, folks.  No offense intended.
0
 
redseatechnologiesCommented:
When you are reinstalling, are you doing a repair install, or installing over the top?  Do the latter.

Also, when you reinstall, what kind of disk are you using?  A supplier disk (like a Dell Windows CD?) these frequently do not ask for serial numbers.

I would call MS, get a genuine cd (for like $20) and then install over the top.  You should only lose your service packs and patches, which should be installed immediately.

-red
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.