Win 7 Ultimate OEM Question

S

Sancti0n

n00b
Joined
Jul 28, 2007
Messages
23
If I understand correctly, if I install an OEM version of WIn 7 Ultimate, than it is tied to THAT rig and ONLY that rig permanently. I can't install/activate it on any other rig. Even if the one it was installed on is turned off/disconnected/destroyed/never-to-be-used-again, I won't be able to install/activate it on any other machine because it's OEM (OEM = 1-time use). Is that correct?

If that's true, what happens if I have to replace something? Like a video card or RAM stick(s).? Or if my primary drive dies and I have to do a complete reinstall? Would I have to buy another OEM disk?
 
An OEM license is tied to the first machine it is activated on and is non transferable. You should however, be able to change ram, video card or hard drive without a problem. It's when you do a motherboard swap that it gets hairy. In any case you can just call Microsoft and explain the situation and 9 times out of 10 they will activate it for you.
 
Lost this one by a few seconds. What Audiochris said, is definitely the case, so don't stress.
 
OEM copies are tied to the motherboard so replacing video cards, RAM, etc shouldn't cause any problems. If your computer hard disk dies and you need to reinstall then you can reinstall.
 
WOW! Thanks for the quick replies! I kinda thought the mobo would be the "key" piece but I wasn't sure. I also thought I had read a couple stories about people having to buy another OS after doing just a vid card/sound card/etc. However what I read here tends to make more sense. Maybe those folks that had probs had other stuff going on ;)
 
Legally OEM software is tied to the motherboard. Technically it is not and nothing stops you from transferring it.

As for upgrading hardware, according to Microsoft, you can replace the motherboard as long as it's one the manufacturer said it can be used as a replacement, ie. CPU/chipset compatibility.

Microsoft Licensing FAQ said:
Generally, an end user can upgrade or replace all of the hardware components on a computer—except the motherboard—and still retain the license for the original Microsoft OEM operating system software. If the motherboard is upgraded or replaced for reasons other than a defect, then a new computer has been created. Microsoft OEM operating system software cannot be transferred to the new computer, and the license of new operating system software is required. If the motherboard is replaced because it is defective, you do not need to acquire a new operating system license for the PC as long as the replacement motherboard is the same make/model or the same manufacturer's replacement/equivalent, as defined by the manufacturer's warranty.
Click to expand...
 
Since most boards are not available when machines croak several years down the road, MS will typically allow you to reactivate with a replacement setup I was able to do that when the MB on my old PC toasted several components (power rectifier failed) and it got repalced with a C2D setup on my XP box....did have to talk to a rep and explain what happened
 
Just to let you it is against EULA since 2008 to use OEM software for personal usage:

http://www.microsoft.com/oem/en/licensing/sblicensing/pages/licensing_for_hobbyists.aspx

Microsoft said:
There is a growing market for "do-it-yourself" home PC hobbyists who assemble PCs from components for their own use. Microsoft retail software licenses are the appropriate licenses for the do-it-yourself market. OEM System Builder software is not intended for this use, unless the PC that is assembled is being resold to another party. ​​​​​​​​​​​​​​​​​​​​​
Click to expand...

I would assume if an OEM copy was purchased prior to 2008 and their rule change they could not retroactively tell you that a legally purchased copy OEM license was now illegal.

Not really sure why Microsoft wants to alienate this relatively small group of their customers.
 
Tsaar said:
Not really sure why Microsoft wants to alienate this relatively small group of their customers.
Click to expand...

I wouldn't say it's about alienating anyone - the "rules" are quite clear that those persons aren't supposed to be using OEM System Builder editions for personal use, period. There's no way to "get around it" and any attempts at rationalizing the work-arounds based on how the EULA might be interpreted don't matter: people aren't supposed to do it, period.

Besides, Microsoft doesn't sell OEM System Builder versions direct (in the most common sense); the third party retailers like Newegg, etc are the ones doing it and they use the excuse of "it can't be sold without a piece of hardware" rationalization most of the time - you end up having to purchase something along with the OEM System Builder copy so they can tell Microsoft "yes, we did sell an OEM System Builder copy of Windows but they were buying parts to build a machine for sale so, we have abided by the terms of our licensing agreement."

Pretty lame but, there it is I suppose.

It's their product, they can set the requirements as they want, and they have but people could care less and abuse it, basically.
 
Bahamut said:
I wouldn't say it's about alienating anyone - the "rules" are quite clear that those persons aren't supposed to be using OEM System Builder editions for personal use, period. There's no way to "get around it" and any attempts at rationalizing the work-arounds based on how the EULA might be interpreted don't matter: people aren't supposed to do it, period.

Besides, Microsoft doesn't sell OEM System Builder versions direct (in the most common sense); the third party retailers like Newegg, etc are the ones doing it and they use the excuse of "it can't be sold without a piece of hardware" rationalization most of the time - you end up having to purchase something along with the OEM System Builder copy so they can tell Microsoft "yes, we did sell an OEM System Builder copy of Windows but they were buying parts to build a machine for sale so, we have abided by the terms of our licensing agreement."

Pretty lame but, there it is I suppose.

It's their product, they can set the requirements as they want, and they have but people could care less and abuse it, basically.
Click to expand...

I said alienating because prior to 2008 they acknowledged in the EULA that if the OEM license was installed on a computer that you were building then you were classified as a "system builder".

Also, the "sold with a piece of hardware" rule changed in 2005 (this was straight from the OEM EULA), and that is when Microsoft acknowledged the DIY market.
 
You must log in or register to reply here.
Back
Top