@madmacs,
Your post is right on point once again !!!!
My last posting begins with the statement:
"A machine may need Re-PAing even when using an MS OEM O/S Edition if (SUBSTANTIAL) machine reconfiguration can be accomplished on the (SAME) machine."
The operative word is (SUBSTANTIAL) as your friend found out the hard / easy way.
Best Regards,
Rick P.
How-To Geek Forums » Off Topic
Tip: Click Here to Update All Your PC's Outdated Drivers (Sponsored Link)
What is your experiance with Windows Product Activation?
(37 posts)
@raphoenix: I disagree. Sure you may to reactivate after installing new hardware but is calling Microsoft really that much harder then installing a motherboard or graphics card in the first place? I don't think so.
I think you would have to be installing a ton of new hardware every month before it would be an issue.
It seems really unlikly to happen. I know that I only install new hardware around every 2 years or so. I wouldn't mind calling Microsoft if Product Activation required it (I wouldn't know due to my last monthboard and graphics card upgrade being part of a new computer as my old desktop from 2001 / laptop from 2005 wasn't worth upgrading seperately). Even if I upgraded once a month, I don't think it would be a problem.
@jd2066,
Disagreement is fine.
If one enjoys phoning and talking with MS folks for no real reason, by all means do so as often as one likes.
In fact, I encourage such.
Sometimes when I'm bored, I just call up MS Support and ask; "What's Happening ??" to get a conversation started.
Listening to the Advertisements and Computer Tips is especially enjoyable while on hold.
Best Regards,
Rick P.
Whilst browsing, I found these paragraphs in an MS FAQs which is relevant in this context:
1. 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.)
2. 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.
3. 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.
4. 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.
@raphoenix:
Yes, calling Microsoft may not be the most fun thing and I have yet to get hold music/ads on a call to Microsoft (Only called about twice though).
Should you get ads while on hold every time you call then I agree with you that it's a bad thing to do and Microsoft should correct that.
I do think it's ok to enforce the Windows license with a simple 5 minute phone call. Microsoft spent years developing Windows and millions (maybe billions) researching and developing things like Windows Aero and the ribbion UI (Used in Office and it seems Windows 7)
Now, the fact that an easy to use hack for Windows XP Product Activation appeared within months/weeks does make it a little silly. Though Windows Genuine Advantage took care of that.
Windows Vista Product Activation on the other hand is very hard to get around. In part to see if it was possible I looked for an easy to use hack (Of which I mean a one click to install program/driver, I'm not going to alter the system files on the hard drive for it). It took a few months to find and only works because of the OEM BIOS loop hole in Windows Vista Product Activation. It even passes the Windows Genuine Advantage test.
Getting around Windows Genuine Advantage in Windows XP is even harder to do and requires a hacked WGA DLL file (I can do that as WGA is separate from the OS for Windows XP so it's won't affect stability of the OS).
I've pondered just switching to Linux so I don't have to deal with it but Desktop Linux isn't quite good enough for me yet (Or at least it wasn't a year ago when I tried Gentoo Linux, I've heard good things about Ubuntu).
> "Is my MS OEM Software License still good under the "defective motherboard clause" ??"
If you explain that to a Microsoft rep on the phone they should give you a new activation key.
I have no idea about Microsoft's offical position on it though.
@raphoenix:
Ok, I agree with you that it is bad if the phone call is not a simple 5 minute deal. When I last activated Windows XP Home around 2002/2003, that is what I recall it being. Maybe something has changed since then.
Also, I'm writing my posts very carefully to avoid that discussion happening again.
@raphoenix: If Microsoft on the phone is anything like Verizon Wireless Tech Support then I understand the phone issue, last night I had to wait on hold listening to how great the new BlackBerrys are until I got someone who told me my issue (Using SSL/TLS for email access) has been worked for a while and has no idea when it will be done. The really annoying thing there is that my phone gives me the SSL/TLS options but they don't function giving me the idea I could use them.
There is still one part of one of your last posts I don't quite get:
> "The Posters above are (NOT) reconfiguring a Builder Machine in between the original archived machine configuration archive file and a (new completely different) machine configuration onto which the archive file is UN-archived upon."
I only change my computer motherboard, processer, etc once every few years and after that only upgrade hard drives for space reasons so a phone call every few years doesn't seem like a problem even if it's not fun.
I would like to know how offten you change your hardware configuration that makes it a problem as I'm interested to know what issues other people have with Windows that I don't have to update my knowledge of Windows issues.
@jd2066,
I don't reconfigure the machines anymore as the MBs and HW are outdated and I know the machines' best configuration plus have the systems archived using Ghost and important data burned to optical storage.
-------------------------
Want to build an i7-X58 machine with the Latest and Greatest HW plus run Windows 7 Beta.
That plan is on hold now because of the HUGE cost (Thousands) and the current economic environment.
-------------------------
Since we are regulars, will stay in touch by E-mail.
Best Regards,
Rick P.
@raphoenix
I am somewhat confused as to a post of yours, and it may be due to a misunderstanding on my part:
To avoid this "hassle" especially on complex Builds and Machines:
1. Purchase MS O/S 3-5 computer volume license.
2. Purchase Retail MS O/S license.
3. Purchase OEM MS O/S with Cals license.
----------------------------------------------------------------------------
I am assuming the list is an OR list and not an AND list, but why would one want to spent more money on multiple licenses (with option 1), and I honestly do not know what "OEM MS O/S with Cals license" is.
It seems that if you purchase one retail license for Windows "INSERT VERSION HERE" you should be fine for re-builds/replacements/re-installations. The irritation from having to call Microsoft after "X" number of re-installs would be worth not having to purchase multiple licenses.
@jmcguire,
The above is a list of the type of licenses one may purchase from MS to (avoid) Manual Product Activations after Clean Installs.
----------
A MS Volume License is for folks that have multiple machines and want to use the same copy of the O/S and license on all their machines. The price for the license varies with the number of machines covered by the MS Volume License.
----------
Theoretically, one is suppose to be able to purchase one MS OEM License per machine and Clean Install the O/S forever on the SAME machine without a Manual PA.
----------
However with Custom Builder Complex Machines, the machine configuration can be changed substantially enough so that a Manual PA may have to be performed upon subsequent Clean Installs after an Initial Clean Installation with net PA.
----------
MS does (NOT) cater to Builders or Computer Enthusiasts as they comprise an infinitesimal market share of MS Business.
@raphoenix
Thank you for clearing that up. I am then assuming that if one purchases a single retail copy of Windows, it is then (theoretically) possible to clean install that copy on any build (as long as it is only on one computer at any given time) forever. I am also assuming these are the cases in which the PA will eventually fail after "X" number of installs?
@jmcguire,
Your assumption is correct however one is allowed to upgrade their machine incrementally (over time) as long as the incremental changes do not cause net PA to fail. (Read Link in my first post on thread).
The (over time) is operative as no one knows for sure how often MS dumps old net PA information from off their database and may vary by world region in different regulatory environments.
Folks have guessed at 3 months, 6 months, or 1 year time frames but I don't know.
The License Agreements and Eula's are forever changing at the whim of MS.
Here is link to MS License Agreements for All MS software. Enjoy :) :)
http://www.microsoft.com/about.....fault.aspx
--------------------
As always, the higher the License Price one pays for the software, the more clout one has with MS.
(1) OEM License with NO cals being the lowest clout. (Beggar's License)
Reply
You must log in to post.