Windows XP. OEM or Retail?

[calypso-325is]

Hey guys this might sound like a stupid question but I am building a new SLI rig and when it came time to looking at the operating systems I wasn't sure to buy OEM or retail version of XP. Is it ok to get OEM if I am using new hardware? Thanks in advance.

 

[Komataguri]

Hey guys this might sound like a stupid question but I am building a new SLI rig and when it came time to looking at the operating systems I wasn't sure to buy OEM or retail version of XP. Is it ok to get OEM if I am using new hardware? Thanks in advance.

Really, it dosn't matter other then the legality issues of say, in the future, you want to transfer your copy of XP to another PC.


Technically/Legally, you can't do that with OEM, While you can with retail.

 

[hulksterjoe]

also retail will cost you $$$ but give you "phone support" with microsoft...

Oem is cheaper but you get no support...other then what you can find on the web/ windows updates..

 

[ThomasE66]

I usually buy OEM because I never need to transfer an OS. I just buy a new license when I build a new box.

 

[djnes]

And if you do use the OEM software, you will be able to upgrade the current machine without making the license invalid. I'm not sure of the specifics, of when it's considered a "new machine", though, but you will be able to add more memory, new video card, processor, etc.

 

[ThomasE66]

And if you do use the OEM software, you will be able to upgrade the current machine without making the license invalid. I'm not sure of the specifics, of when it's considered a "new machine", though, but you will be able to add more memory, new video card, processor, etc.

Come to think of it, I've never been asked to reactivate on any of my machines...I never really gave it much thought.

 

[mattjw916]

Quite some time ago, M$ altered the activiation routine so that it wasn't so pickey about components being upgraded such as video card, HDD, etc due to potential public backlash dur to people being annoyed by being forced to "re-activate" the OS.

Of course, I have only activated it a few times since I get a free MSDN Universal subscription through work.

 

[Badger_sly]

Go with the OEM and save some cash.

And, you can move an OEM install to a new machine, or onto a major upgrade that the OEM was previously installed on, just as long as it's on only 1. The worst that will happen, possibly, is that it won't allow activation until you call a 1-800 # and talk to a CS rep who will ask if it's on 1 machine, then give you a code to type in to make the activation happen. I've had to do it several time, and it's no big deal.

 

[SJConsultant]

Go with the OEM and save some cash.

And, you can move an OEM install to a new machine, or onto a major upgrade that the OEM was previously installed on, just as long as it's on only 1. The worst that will happen, possibly, is that it won't allow activation until you call a 1-800 # and talk to a CS rep who will ask if it's on 1 machine, then give you a code to type in to make the activation happen. I've had to do it several time, and it's no big deal.

Please note the following information is only provided so you know how the OEM license is "supposed" to work and not necessarily what happens in practice.

A Windows OEM OS license is tied to the first "motherboard" it is installed on and only valid for that system. The EULA does not allow for moving the OEM software from one machine to another simply because it is only installed on *one* machine. Furthermore if you upgrade and replace the motherboard it in essence becomes a "new" computer and thus should have a new license purchased.

Although you might be able to move it from one machine to another, Microsoft does not have to reactivate it.

I seriously have to finish this OEM licensing FAQ.

 

[Phoenix86]

I seriously have to finish this OEM licensing FAQ.

*cracks whip*

Who let you out of your cage?

 

[Badger_sly]

Please note the following information is only provided so you know how the OEM license is "supposed" to work and not necessarily what happens in practice.

A Windows OEM OS license is tied to the first "motherboard" it is installed on and only valid for that system. The EULA does not allow for moving the OEM software from one machine to another simply because it is only installed on *one* machine. Furthermore if you upgrade and replace the motherboard it in essence becomes a "new" computer and thus should have a new license purchased.

Although you might be able to move it from one machine to another, Microsoft does not have to reactivate it.

I seriously have to finish this OEM licensing FAQ.

You're correct on the EULA in a general sense, but MS is somewhat flexible with it also, which is what I'm referring to. Hardware, one of which being the motherboard, can go bad, and a replacement of the same model might not be sold any more. Power surges, lightning, pet accidents, spilled drinks, etc. are some reasons why MS has to allow an OEM OS to be moved.

 

[Phoenix86]

You're correct on the EULA in a general sense, but MS is somewhat flexible with it also, which is what I'm referring to. Hardware, one of which being the motherboard, can go bad, and a replacement of the same model might not be sold any more. Power surges, lightning, pet accidents, spilled drinks, etc. are some reasons why MS has to allow an OEM OS to be moved.

But that's only for replacement, not upgrade, which is what most people expect they can do...

 

[Badger_sly]

But that's only for replacement, not upgrade, which is what most people expect they can do...

It's a gray area, that MS can't distinguish. That's why all they ask when you have to call up to activate is "is it installed on one computer only?" When you answer yes, they give the code to activate.

 

[Phoenix86]

It's a gray area, that MS can't distinguish. That's why all they ask when you have to call up to activate is "is it installed on one computer only?" When you answer yes, they give the code to activate.

I understand... I think they should just "give up" on the whole OEM=bound to mobo only.