Activating a 32-bit 2003 Standard Server with a 64-bit key

[Justin Admin]

I built a Windows 2003 Standard server (32 bit) with software we currently own
thinking I could (in the next 30 days) go out, buy another copy, change the
key, and then activate it as per kb918342. About two weeks after I built the
server I discovered a copy of Windows 2003 Server x64 that we own that is not
in use. Since it's an x64 OEM version the current server won't accept the
key, throwing a "The product key used to install Windows is invalid" message.
Before it gets asked - yes the key and software are legit, both purchased
from Dell as OEM, and no the license/key in question is not in use.

Is there a way to "brute force" the key in and then activate it without
having to do a reinstallation from the ground up with the x64 software?

Thanks for any assistance you can offer.

-Justin

[Darrell Gorter[MSFT]]

Hello Justin,
Note the warning in that article:
Warning The steps in this article only apply to Volume License media. If
you follow these steps on OEM media or on retail media, you will not change
the product key.
That script is only for changing from one volume license key to a different
volume license key
in Windows 2003, you cannot change from one media type Product Key to a
different type of product key.
The Media and Key are tied together, so if you installed OEM media, only
OEM keys can be used.
If you install Volume media, only Volume product keys can be used.
The script in this article applies to volume media only.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> Thread-Topic: Activating a 32-bit 2003 Standard Server with a 64-bit key
|> thread-index: Achqk58yyfufB9myT9GFihZ06KFaVA==
|> X-WBNR-Posting-Host: 207.46.19.168
|> From: =?Utf-8?B?SnVzdGluIEFkbWlu?=
<[email protected]>
|> Subject: Activating a 32-bit 2003 Standard Server with a 64-bit key
|> Date: Fri, 8 Feb 2008 12:46:04 -0800
|> Lines: 15
|> Message-ID: <[email protected]>
|> MIME-Version: 1.0
|> Content-Type: text/plain;
|> charset="Utf-8"
|> Content-Transfer-Encoding: 7bit
|> X-Newsreader: Microsoft CDO for Windows 2000
|> Content-Class: urn:content-classes:message
|> Importance: normal
|> Priority: normal
|> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
|> Newsgroups: microsoft.public.windows.server.setup
|> Path: TK2MSFTNGHUB02.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:3552
|> NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
|> X-Tomcat-NG: microsoft.public.windows.server.setup
|>
|> I built a Windows 2003 Standard server (32 bit) with software we
currently own
|> thinking I could (in the next 30 days) go out, buy another copy, change
the
|> key, and then activate it as per kb918342. About two weeks after I
built the
|> server I discovered a copy of Windows 2003 Server x64 that we own that
is not
|> in use. Since it's an x64 OEM version the current server won't accept
the
|> key, throwing a "The product key used to install Windows is invalid"
message.
|> Before it gets asked - yes the key and software are legit, both
purchased
|> from Dell as OEM, and no the license/key in question is not in use.
|>
|> Is there a way to "brute force" the key in and then activate it without
|> having to do a reinstallation from the ground up with the x64 software?
|>
|> Thanks for any assistance you can offer.
|>
|> -Justin
|>

[Justin Admin]

Darrell, I went ahead and did a backup, format, and rebuild. I see what you
mean though about that article and volume licensing. I also didn't know that
the media and key are tied together, so thank you very much for your reply!
-Justin


> Note the warning in that article:
> Warning The steps in this article only apply to Volume License media. If
> you follow these steps on OEM media or on retail media, you will not change
> the product key.
> That script is only for changing from one volume license key to a different
> volume license key
> in Windows 2003, you cannot change from one media type Product Key to a
> different type of product key.
> The Media and Key are tied together, so if you installed OEM media, only
> OEM keys can be used.
> If you install Volume media, only Volume product keys can be used.
> The script in this article applies to volume media only.
> Thanks,
> Darrell Gorter[MSFT]