Re: OEM activation - where do I stand?




Paul wrote:

Some years ago I bought an OEM version of Windows XP with some hardware. I as understand it the license is tied to the first machine it's installed on - fair enough. At the time I read some posts relating to what constitutes a 'new' machine and it all seemed a tad vague but the option to repair/upgrade seemed ok.

Anyway, the OS has been clean installed a few times. Before Christmas I replaced the motherboard and processor, neither were dead but I was getting the odd BSOD. All the other hardware remained the (hardrive, gfx card, memory etc. even the case with the license sticker on). XP indicated hardware changes and then happily activated itself online. I assumed that all was well since Windows activated itself and thought no more of it. I've since added an extra stick of memory.

Yesterday I had a total harddrive failure (and yes, no back up) so replaced the harddrive and did a clean install. This time when I tried to activate Windows it wouldn't as it claimed that the product key and be activated too many times.

I phoned the automated line and entered the product key. I was then ask (again automated) whether the product was pre-installed or bought retail. Actually it's neither, it wasn't pre-installed and was bought (legitimately) retail but isn't a 'retail' product. I chose pre-installed since I guessed it was asking if it was OEM. I was then asked whether I'd recently installed new hardware. No indication of what 'recently meant. I said yes, as technically I had, although XP had activated itself after this and the hardware change hadn't prompted the current activation issue. Then, was it the motherboard, again I said yes although again, this hadn't prompted the current activation issue.

My activation was declined as changing the motherboard apparently was not allowed according to the license (not actually stated in the license - I think I bought it in 2004, it may have changed since but presumably can't be applied retrospectively). I could have said that I'd bought the product retail (true and it wasn't pre-installed) and that I hadn't changed hardware recently (true in the sense that the recent hardware change didn't prompt this activation, XP activated itself and ran happily for some time after the change and there's also no definition of what constitutes 'recent').

Anyway, I spoke to a representative and said that I'd had a harddrive failure and done a clean install. He activated Windows XP for me. I then ask clearly whether I was properly licensed as I'd bough Windows OEM with hardware and had since changed the motherboard. He stated quite clearly that I was fully licensed, I restated that I'd changed the motherboard and was told that this didn't matter.

So, I'm assuming that I'm ok but things are rather unclear. The bottom line for me is that after the motherboard change Windows itelf activated itself (with an OEM product key) which I assume confirms legitimacy, and ran happily thereafter. The subsequent activation issue was a hardware failure one and I only needed contact Microsoft as I'd used up my allocation of activations for the given license (a pain if you do clean installs). The MS reps. response to my clear question tends to confirm this. Windows Genuine Validation code happily validate my installation.

But I'm still not 100% sure. Obviously I don't want to buy a retail XP but want to be clear I'm properly licensed.

Discuss!

I obviously don't

The status of your license is exactly as you described it. Of
course, it would take a lawyer to interpret what you said and
how it relates to the interpretation of the legalese of the EULA
which, BTW, is beyond the normal understanding of any customer
services representative, especially an out-sourced one in some
international locale. Of course, any lawyer would have advised
you to state the facts...which is that the hard drive broke and
was replaced. That is all that was needed to be said and not one
iota more in this situation. There was no need to have volunteered
any more.

WPA is a failure because there are not enough unique keys for
each and every product that requires activation. There is only
a 120-day supply of these product keys and they must be used
several times within the 120-day cycle. MS made the erroneous
assumption that nobody would be only so many activations (or
re-activations) for any given key during that time. Hence, its
database would kick out any over-used, rigutfully or wrongfully,
product key.
.



Relevant Pages

  • Re: No OS disk with purch refurb laptop
    ... to install with, and then register/validate with this product key. ... supply the product key of my own license during ... then you will need an OEM Windows distribution to install from. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: [Xnew] Overriding score of 9999
    ... As for it being tied to the hardware... ... Manufactures use a pool of keys to install windows--and believe it or not, the one they used to install the OS might not be the one on the sticker. ... Sometimes the product key in the registry will be different than the key on the Product Key sticker--some larger manufactures have an OEM 'pool' of keys they use. ...
    (news.software.readers)
  • Re: XP Pro installed, XP Home license
    ... The seller has assured me that it is OK to use a home license with PRO, and that it installs just fine that way. ... even a new windows vista you can install in this machine with same product key. ...
    (microsoft.public.windowsxp.basics)
  • Re: OEM activation - where do I stand?
    ... All the other hardware remained the (hardrive, gfx card, memory etc. even the case with the license sticker on). ... Yesterday I had a total harddrive failure so replaced the harddrive and did a clean install. ... This time when I tried to activate Windows it wouldn't as it claimed that the product key and be activated too many times. ...
    (microsoft.public.windowsxp.general)
  • Re: OEM activation - where do I stand?
    ... All the other hardware remained the (hardrive, gfx card, memory ... etc. even the case with the license sticker on). ... the harddrive and did a clean install. ... I phoned the automated line and entered the product key. ...
    (microsoft.public.windowsxp.general)