2003 Server R2: changing OEM --> OEM license key

Hi all,

weeks ago someone mixed up the cardboard boxes and installed and activated a
Windows 2003 R2 Server belonging to one customer using a different customer's
OEM license key.

Reinstalling the server should be avoided, a lot of installation work has
already been sunk into the server configuration.

I tried a lot, e.g. the OOBETimer registry hack trick, and the "delete
wpa.dbl and wpa.bak" trick, nothing seems to works with OEM licenses,
whenever I run msoobe.exe /a it tells me the server is already activated.

How can I invalidate the license/activation so I can enter and activate the
correct OEM key?

Thanx,

AL.

Hello,
Renaming the wpa.dbl and wpa.bak is the correct solution.
After doing this you do need to reboot, the machine should require
activation.
OOBETimer should have no effect for this scenario
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
> Thread-Topic: 2003 Server R2: changing OEM --> OEM license key
> thread-index: AcnjW1e9r/WbDwNeSLKOOH2EZn2QAg==
> X-WBNR-Posting-Host: 80.246.32.33
> From: =?Utf-8?B?TmltcmFs?= <>
> Subject: 2003 Server R2: changing OEM --> OEM license key
> Date: Tue, 2 Jun 2009 01:23:01 -0700
> Lines: 20
> Message-ID: <7971251C-28E6-4874-A836->
> 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.3168
> Newsgroups: microsoft.public.windows.server.setup
> Path: TK2MSFTNGHUB02.phx.gbl
> Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:6600
> NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> X-Tomcat-NG: microsoft.public.windows.server.setup
>
> Hi all,
>
> weeks ago someone mixed up the cardboard boxes and installed and
activated a
> Windows 2003 R2 Server belonging to one customer using a different
customer's
> OEM license key.
>
> Reinstalling the server should be avoided, a lot of installation work has
> already been sunk into the server configuration.
>
> I tried a lot, e.g. the OOBETimer registry hack trick, and the "delete
> wpa.dbl and wpa.bak" trick, nothing seems to works with OEM licenses,
> whenever I run msoobe.exe /a it tells me the server is already activated.
>
> How can I invalidate the license/activation so I can enter and activate
the
> correct OEM key?
>
> Thanx,
>
> AL.
>
>

Hi Darrel,

thanks for the info. It worked like a charm :-) Seems that the OOBETimer
hack does the trick for Volume License, while deleting the wpa files does for
OEM versions.

Thanks very much

AL.

""Darrell Gorter[MSFT]"" wrote:

> Hello,
> Renaming the wpa.dbl and wpa.bak is the correct solution.
> After doing this you do need to reboot, the machine should require
> activation.
> OOBETimer should have no effect for this scenario
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> > Thread-Topic: 2003 Server R2: changing OEM --> OEM license key
> > thread-index: AcnjW1e9r/WbDwNeSLKOOH2EZn2QAg==
> > X-WBNR-Posting-Host: 80.246.32.33
> > From: =?Utf-8?B?TmltcmFs?= <>
> > Subject: 2003 Server R2: changing OEM --> OEM license key
> > Date: Tue, 2 Jun 2009 01:23:01 -0700
> > Lines: 20
> > Message-ID: <7971251C-28E6-4874-A836->
> > 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.3168
> > Newsgroups: microsoft.public.windows.server.setup
> > Path: TK2MSFTNGHUB02.phx.gbl
> > Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:6600
> > NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> > X-Tomcat-NG: microsoft.public.windows.server.setup
> >
> > Hi all,
> >
> > weeks ago someone mixed up the cardboard boxes and installed and
> activated a
> > Windows 2003 R2 Server belonging to one customer using a different
> customer's
> > OEM license key.
> >
> > Reinstalling the server should be avoided, a lot of installation work has
> > already been sunk into the server configuration.
> >
> > I tried a lot, e.g. the OOBETimer registry hack trick, and the "delete
> > wpa.dbl and wpa.bak" trick, nothing seems to works with OEM licenses,
> > whenever I run msoobe.exe /a it tells me the server is already activated.
> >
> > How can I invalidate the license/activation so I can enter and activate
> the
> > correct OEM key?
> >
> > Thanx,
> >
> > AL.
> >
> >
>
>