Re: 1st home built computer
- From: Barry Watzman <WatzmanNOSPAM@xxxxxxxxxx>
- Date: Sun, 03 Sep 2006 19:55:13 -0400
The reality of all of this is very, very nebulous. Bottom line, if it won't reactivate, you call Microsoft and you have a "discussion" with them. If you tell them that you are replacing a motherboard (which is true in a sense, even if in fact you are building an entirely new computer), they have no way of knowing "why" you are doing this. The bottom line here is that the whole situation is ambiguous and comes down to judgement, often depending on which agent you get, what kind of a mood they are in, and how convincing you and your statements are. You might get reactivated, you might not.
[All of this applies to an OEM copy; for a retail copy, moving the license from one machine to another is permitted, as long as it's only installed on one single machine.]
I went through an entirely legitimate situation recently where I installed XP on a new machine, activated, discovered a defect in the motherboard, replaced the motherboard, discovered a defect in the replacement, and installed a 3rd motherboard. I was able to get MS to allow 3 (entirely legitimate) activations within 6 weeks, but it wasn't fun. This was a retail copy.
One of the real downsides of WGA is that in order to run windows update and get all of the updates, you are forced to activate more or less immediately. I used to install, but not activate for the allowed 30 days of "unactivated use". At least that way, you discovered the problems before activation. Now, however, you can't download the updates without activation, which largely destroys the ability to use the system unactivated for 30 days. That's unfortunate, because those 30 days served a very real purpose as related to determining and establishing the reliability of a new build.
BC wrote:
GHalleck wrote:.
RBM wrote:
You're probably going to need a new COA license for the XP<<snipped>>
Not if the Windows XP version is a retail, box and that it
has been uninstalled from the first machine.
Unfortunately, according to Microsoft's website, looks like he will need to at least buy a new OEM version of XP:
http://forums.microsoft.com/Genuine/ShowPost.aspx?PostID=670449&SiteID=25
**Quote from link, not from me:**
It is true that one cannot transfer an OEM license to a new machine, but the purpose of that restriction is not to prevent end users from having a malfunctioning computer repaired, and I don't understand why some people choose to interpret it that way.
The purpose of that restriction is to prevent unscrupulous system builders from offering to peel the license sticker from the case and reuse it, or simply build a new computer in the existing case to "save the cost" of a new license.
However, you will notice that this clause in the license agreement does give the consumer one "out", which is that one may replace a defective motherboard with another one of similar specifications, and still preserve their license.
It is only if a motherboard is replaced to obtain a "performance upgrade" that a new license is required.
**End quote**
And, from
download.microsoft.com:
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.
download.microsoft.com/download/4/e/3/4e3eace0-4c6d-4123-9d0c-c80436181742/OSLicQA.doc
**end quote**
It does look like a full retail package license differs:
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.
7. How do I know whether I have a genuine OEM license for my operating system?
ANSWER. Microsoft has a website that helps customers determine if they have acquired genuine Microsoft products at
http://www.microsoft.com/howtotell.
After reviewing the site, if you believe that your Microsoft product may be suspect or counterfeit, you should report this suspected piracy in the tool provided on the website. Alternatively, you may call 1-800-RULEGIT or e-mail piracy@xxxxxxxxxxxxx to report any suspected counterfeit or pirated software.
8. What do I do if I realize that I do not have a full license for Windows, or if I received a donated PC that did not come with an operating system license?
ANSWER. If you do not have a genuine operating system license, you can acquire a Full-Packaged Product (FPP) version of the product from your local retail store. Or you may purchase an OEM version of an operating system from a Microsoft System Builder, subject to the requirement that you purchase hardware with that OEM version of the product. At that time, you should receive a genuine EULA, Certificate of Authenticity (COA), and manual. Visit the Microsoft How to Tell website to determine whether you have genuine software and licensing; http://www.microsoft.com/piracy/howtotell.
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.
http://microsoft.com/piracy/basics/activation/windowsproductactivationtechnicalmarketbulletin.doc
HTH,
BC
- References:
- Re: 1st home built computer
- From: DRS
- Re: 1st home built computer
- From: RBM
- Re: 1st home built computer
- From: GHalleck
- Re: 1st home built computer
- From: BC
- Re: 1st home built computer
- Prev by Date: Re: 1st home built computer
- Next by Date: Re: Slightly OT but important
- Previous by thread: Re: 1st home built computer
- Next by thread: Re: 1st home built computer
- Index(es):
Relevant Pages
|