http://groups.google.com.au/groups?a...0 06&safe=off
Is where I posted the previous version.
--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"David Candy" <.> wrote in message news:...
It available as a PDF online. I posted it many times in the past.
See this for a link
http://66.102.7.104/search?q=cache:N...=en&lr=lang_en
--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Vanguard" <vanguard.code@comcastNIX.net> wrote in message news:u00twePEGHA.3068@TK2MSFTNGP10.phx.gbl...
> "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
> news:OJJ1EnIEGHA.644@TK2MSFTNGP09.phx.gbl...
>>
>> I have attended several Microsoft seminars on licensing. Here are some
>> relevant portions of the current OEM agreement.
>
> Does Microsoft make this information available online, or do I have to pay
> big bucks to attend a seminar?
>
>> "4. SOFTWARE DISTRIBUTION.
>> 4.1 We grant you a nonexclusive right to distribute an individual software
>> license only with a fully assembled
>> computer system. A "fully assembled computer system" means a computer
>> system consisting of at least a central processing unit, a motherboard, a
>> hard drive, a power supply, and a case.
>> 4.2 Each individual software license must be distributed pursuant to the
>> end-user license agreement ("EULA")
>> that accompanies the individual software license. Under the terms of the
>> EULA, you are the licensor."
>
> Yep, that would explain how the "qualifying hardware" becomes their entire
> computer system. Definitions in the *end* user license are more vague. We
> aren't an OEM so I've never really had a chance to see what OEM'ers have to
> agree to. I do know that our end-user retail OEM copies are much more
> pricey than the per-license cost for an OEM'er building complete hosts and
> including Windows with them.
>
>> "6. PREINSTALLATION REQUIREMENT. When you distribute an individual
>> software license for a desktop operating system or application software,
>> you must preinstall it on the fully assembled computer system’s hard drive
>> using the OEM Preinstallation Kit ("OPK") provided in this package or
>> otherwise made available by us. This preinstallation requirement does not
>> apply to server software. For a list of available OPKs, information about
>> using
>> OEM preinstallation tools, OPK support and how to obtain OPKs, see
>> www.microsoft.com/oem/sblicense/OPK.
>> Preinstallation is limited to one copy of each individual software
>> license. You may not copy or modify the OPK or
>> OPK instructions. You may not distribute the OPK or OPK instructions to an
>> end user."
>
> Thanks for the link. I'll go do some more checking there.
>
>> I understand that in certain cases for very large OEMs this agreement may
>> be slightly different but I have been assured by a Microsoft licensing
>> specialist that the essence is the same. OEM Offiice product cannot be
>> sold without installing it on a system. Once it is sold to the end user
>> (your $7M lab) Microsoft may make a seperate agreement with you.
>
> Our Unix admin in our QA group was the one that dealt with the licenses. I
> did have to call Microsoft (which took several calls and getting bounced
> around) to find out if our intentions were okay with Microsoft. I didn't
> want just to tech support jockey saying it was okay and had to find some
> mid-management rep to okay our intentions, but they weren't going to let me
> bother their legal department about it.
>
>> In your post you refer to "Microsoft-branded retail OEM version of
>> Windows"
>
> I meant that the CDs were Microsoft branded (i.e., they say Microsoft) and
> are not vendor-specific versions where the vendor manufactured their own
> installation/recover/restoration CD with the vendor's label on it, or that
> it was, for example, some Dell bastardized installation which installs a
> setup of software that is different (more limited, other fluff software)
> than the one you get with the Microsoft-branded CD. Just because the OEM
> says it is Windows doesn't mean it is exactly the same Windows that
> Microsoft itself distributes.
>
>> There is no retail OEM version of Windows and the OP was not about OEM
>> Windows in any case.
>
> Huh? So why is "OEM" in the Subject header of the OP? Sounded like he was
> asking about OEM versions.
>
> Thanks for the info. Looks like some more reading for me. Any links to
> what might be a boilerplate OEM contract from Microsoft? I'll dig around a
> bit over at the OEM System Builder site that you provided. We don't build
> our hosts for redistribution but a buddy of mine is thinking of building
> some hosts for Point-Of-Sale that have Windows running on them.
>
> --
> __________________________________________________ _____
> ** Post replies to the newsgroup. Share with others. **
> For e-mail, remove "NIX" and append "#VC811" to Subject.
> __________________________________________________ _____
>