6. What is the difference between OEM product and Full-Packaged Product (FPP)?
ANSWER. OEM products are intended to be preinstalled on hardware before the end user purchases the product. They are “shrink wrapped” and do not come in a box like the retail products do. Full-Packaged Product (FPP) is boxed with CD(s), manuals, and the EULA and is sold in retail stores in individual boxes. The End User License Agreements (commonly referred to as “EULAs”) for OEM and FPP products are slightly different. One main difference is that an OEM operating system license (such as the license for Windows) cannot be transferred from its original PC to another PC. However, the FPP version of Windows may be transferred to another PC as long as the EULA, manual and media (such as the backup CD) accompany the transfer to the other PC. Also, when a customer purchases an OEM product, the OEM license requires the OEM to provide support for the product.
9. Can I transfer my operating system license from an old PC to a new one?
ANSWER. Not unless it was purchased as a Full-Packaged Product from a retail store (i.e., Windows in a box). Current OEM licenses for all Microsoft operating system products are not transferable from one machine to another. The End User License Agreement (EULA) governs the terms for transfer of licenses. Some EULAs for copies of certain older OEM operating system products (i.e., MS-DOS®, Windows® 3.1, and Windows for Workgroups 3.1) distributed in 1995 or earlier may permit transfer of the OEM operating system software license under limited circumstances. (See Software Product Transfer section of your End User License Agreement.)
10. If I “retire” a PC with an OEM license on it, can I use that software on a new PC?
ANSWER. No. To put it simply, OEM product is “married” to the original PC on which it was installed. Current OEM licenses are not transferable from one machine to another. The software cannot be moved from PC to PC, even if the original PC it was installed on is no longer in use. This is true for all OEM software – operating systems and applications.
11. Rather than purchase completely new PCs, my organization performs in-place upgrades to the hardware on many of our computers. We often times only replace the motherboard, processor, and memory. Since the COA is still on the case and the OS is still installed on the hard drive, this computer is still licensed, right?
ANSWER. Generally, you may upgrade or replace all of the hardware components on your computer and maintain the license for the original Microsoft OEM operating system software, with the exception of an upgrade or replacement of the motherboard. An upgrade of the motherboard is considered to result in a "new personal computer." Microsoft OEM operating system software cannot be transferred from one computer to another. Therefore, if the motherboard is upgraded or replaced for reasons other than a defect then a new computer has been created, the original license expires, and a new full operating system license (not upgrade) is required. This is true even if the computer is covered under Software Assurance or other Volume License programs.
12. If I upgrade some of my PC components, do I have to purchase a new operating system?
ANSWER. The answer depends on the components that are upgraded or changed in the PC. The operating system licenses must remain with the device that retains the motherboard, chipsets, and chassis that include the serial number of the device. The operating system may be installed on a new/replacement hard drive as long as the operating system is first removed from the old hard drive.
Please refer to the section on “Modifications to hardware and how they affect the activation status of Windows XP” in the following link for a more detailed explanation regarding specific hardware changes. The same hardware component changes that can be made to a PC before requiring re-activation of Windows XP are the same changes that can be made before a PC is considered to be “new” - and when a new license for OEM software is required.
Modifications to hardware and how they affect the activation status of Windows XP
Product activation rechecks the hardware it is running only to help reduce illegal hard disk cloning – another prevalent piracy method. Hard disk cloning is where a pirate copies the entire image of a hard disk from one PC to another PC. At each login, Windows XP checks to see that it is running on the same or similar hardware that it was activated on. If it detects that the hardware is “substantially different”, reactivation is required. This check is performed after the SLP BIOS check discussed above, if the SLP BIOS check fails. This means that if your PC is pre-activated in the factory using the SLP pre-activation method, all the components in the PC could be swapped, including the motherboard, so long as the replacement motherboard was genuine and from the OEM with the proper BIOS. As noted above, installations of Windows XP made using volume licensing media and volume license product keys (VLKs) will not have any hardware component checking.
Q. Can a PC with an OEM Windows operating system have its motherboard upgraded and keep the same license? What if it was replaced because it was defective?
A. 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.
The reason for this licensing rule primarily relates to the End User Software License Terms and the support of the software covered by that End User Software License Terms. The End User Software License Terms is a set of usage rights granted to the end user by the PC manufacturer and relates only to rights for that software as installed on that particular PC. The system builder is required to support the software on the original PC. Understanding that end users, over time, upgrade their PCs with different components, Microsoft needed to have one base component "left standing" that would still define the original PC. Since the motherboard contains the CPU and is the "heart and soul" of the PC, when the motherboard is replaced (for reasons other than defect) a new PC is essentially created. The original system builder did not manufacture this new PC, and therefore cannot be expected to support it.
Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.
Comments (17)
Author
Commented:But there are rules that apply to being a System Builder - even if you do this as a "hobby" - including that you cannot supply yourself with an OEM licensed system where you are also the system manufacturer.
Newegg etc., sell OEM disks but how they are used is up to the purchaser. (The extreme analogy is, "we only sell the guns" :))
http://www.microsoft.com/OEM/en/licensing/sblicensing/Pages/licensing_for_hobbyists.aspx
You cannot legally buy reinstallation disks from other manufacturers unless they are being sold with a PC ("For distribution only with a NEW <insert name of manufacturer here> PC")
UNLESS you have purchased them DIRECT FROM THE MANUFACTURER TO REPLACE LOST OR DAMAGED MEDIA.
Commented:
Commented:
Commented:
(I avoid the use of the word "legal" because it carries too much weight in the eyes of many. For example, if one violates license terms, is that "illegal"? Often not. It is surely and simply a violation of the license terms. It takes action to determine what the consequences of this violation of terms might be. So you may be prevented from "Authenticating" an OS as a consequence. Or, you may be threatened into buying another license as a consequence (how many have?) . Or, you may be taken to court and then the court will decide the consequences. And, in some far-out cases, there may be civil or criminal charges levied by some government agency because the actions were allegedly *illegal*. Do you really think that some government is often going to jump on this? On what basis?)
One is advised: "Don't ask your lawyer: "Is this legal?". Rather ask: "Can I do this?"
The difference is in the practical application of the law through enforcement.
So, I can spit on the street with relative impunity even though it may be "illegal" on the books of the city or town. That's because nobody is going to enforce that law.
One can ask the same about licensing terms.
Don't ask your lawyer "Is this in violation of the license terms?" Rather ask: "What might happen if I violate this term in the license? Anything?" Often the answer is "nothing".
Now only you can decide if an action is morally defensible......
Here is food for thought re: the semantics:
From above:
Huh? Of course you can legally buy disks. They aren't contraband nor some controlled substance. The situation here really is that they come with an attached license. The real issue is "Can you buy licenses along with a disk and subsequently use those licenses / i.e. use the disks for installation and subsequently have the installed OS BE LICENSED".
Is it illegal to not be licensed? Or is it simply a state of being NOT LICENSED?
Maybe a better question is: "Can you legally SELL disks and promise licenses as well?"
I'm not a Microsoft basher. I have no intent to cheat them or pirate from them. And, I prefer to not be inconvenienced by their unenforceable terms. The best result in doing a repair is to end up with an Authenticated system that is indistinguishable from "what it should be". Preconditions like having holograms in hand seem silly to me. What is the end result? When the machine is inspected thereafter, where is the hologram now? Burned, lost, stolen ....?? How can it matter?
Thus the comment about "terms" is well made.
Now, I suppose that an argument can be made that users are protected from difficulty and time-consuming effort if they know up front what will assuredly work. I think that's what Masqueraid's paper here is about. It's a real service.
I'll still quibble about "legal" getting back to the original question:
Maybe this should be reworded:
And maybe even better, it should be:
These are just my humble thoughts. If you like 'em then you take your own chances.
Commented:
The article addresses the question, "... Can I legally transfer my OEM version of Windows to another PC? " That is NOT the same as the title of the article, which reads "... Can I transfer my OEM version of Windows to another PC?" ... which may be why some expect a different discussion.
Note the missing word ... "legally"
Your question, "... If I transfer my OEM version of Windows to another PC, am I breaking any laws?" => is essentially the same question.
Your other question, "... If I transfer my OEM version of Windows to another PC, can I retain the license for it? " => certainly implies a legal issue (i.e. clearly you can "retain the license" ... so the implication is that you're asking if it's legal).
I think what many folks want to know is simply "Will it work?" i.e. will it install; activate; and authenticate okay? Masqueraid already addressed this quite well in the article -- noting the distinction about whether it is "... physically possible to move the system ..." and if it is "... legal to do so."
If one doesn't care about the legalities, you can always simply try it ... if it activates okay, it's clearly going to work => and I'd certainly agree with your comments r.e. enforcement. It's rather unlikely that Microsoft is going to take legal action against an individual who installs an OEM license on a 2nd machine (i.e. a replacement motherboard) :-) In theory, it shouldn't activate ... but if it does, then it's going to work - period. It is, however, as the article makes clear, a violation of Microsoft's EULA to do so.
View More