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

Discussion in 'Server Setup' started by Nimral, Jun 2, 2009.

  1. Nimral

    Nimral Guest

    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?


    Nimral, Jun 2, 2009
    1. Advertisements

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

    This posting is provided "AS IS" with no warranties, and confers no rights
    Darrell Gorter[MSFT], Jun 2, 2009
    1. Advertisements

  3. Nimral

    Nimral Guest

    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


    Nimral, Jun 4, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.