Originally posted by: MrChad
Originally posted by: Kremerica
Yeah I called a couple times, talked with 3 different CSRs and all the times they offered volume licensing. The main selling point was that if I had 5000 computers, I wouldn't have to keep each COA, Serial Number, etc. for each of the 5000 computers stored in a room or file somewhere, the volume license would be much easier to manage the licenses. But since I have roughly 40 computers, then OEM is much cheaper.
Keep in mind that OEM software is tied to the machine on which it is installed. If you retire the machine, you retire the OEM software with it. Volume licensing is much easier to keep track of, and if you upgrade machines, you don't need to worry about purchasing new software.
Chad,
Agreed I do see the benefits of volume licensing, but cost is our main motivator. We have looked at computer life at our company and find that we keep computers roughly 5 years and have only had 1 instance of a motherboard failure. So from a cost perspective the OEM licenses will pay for themselves over time.
After talking with another somewhat more knowledgeable CSR at Microsoft, he directed me to the OEM licensing agreement...
OEM License Link
(If you can't get the PDF link, you can goto MS website and search for OEM license)
It appears that a person has a couple ways in which to buy and use OEM software legally.
The main thing I notice is the definition of "
system builder."
5th sentence: ?
System builder? means an original equipment manufacturer, or an assembler, reassembler,
or installer of software on computer systems.
Someone who installs software can be considered a "system builder." So in this instance, I am considering myself a system builder. I accept all the liability of the system builder. Meaning I can't get tech. support from MS. I am suppose to provide tech. support to anyone who buys the installed product from me. I can't return the package once opened. The license is only good on the computer it is installed on, and cannot be transferred etc.
Sentence 2: "
You accept this license when you open this package."
Sentence 4: "
If you do not open this package, you may distribute it to another system builder."
If I were to buy un-opened OEM software, it would fall into this category. The 4th sentence allows me to legally buy (AND sell) it from/to internet sites or companies that also claim to be "system builders." I'm no lawyer, but buying it is legal in my mind.
Then, when the package is opened, this is when you must agree to the rest of the license. This means you install it on a "fully assembled computer system? and it lives and dies with that machine.
OK, now with all that said and done, there is one wrinkle!
While looking around at the OEM license. I searched MS' site and found a System builder license for January 2007 and newer OEM software. (but not office 2007)
System Builder license WEBPAGE
January 2007 and newer OEM System Builder License PDF
In the above 2007 OEM license, MS more clearly states that you must be a "
pre-installer" of software to be considered a "system builder."
This is still open for interpretation. I think that if I build or buy a barebones system, and I install the software before an "end-user" gets the computer, then I am still considered a "pre-installer." (just my thoughts)
Others might claim a preinstaller is something different.
MS also more clearly states the definition of a "fully assembled computer." And I thought it was interesting that instead of having just a "hard drive" the computer can have flash (NAND) memory now.
(I am still looking at the 2007 license in more depth)
At this point, I have convinced myself that as long as I meet the definition of "system builder" and I purchase sealed OEM packs from other "system builders" then I am fully within the license terms of MS OEM software.
tell me what you think.