Archived from groups: microsoft.public.windowsxp.general (
More info?)
On Sat, 3 Sep 2005 09:44:04 -0700, "Carey Frisch [MVP]"
<mrxp2004@nospamyahoo.com> wrote:
>OEM System Builder Packaging, Licensing, and COA Changes
>
>Frequently Asked Questions:
>
>Why is Microsoft making these changes?
>
>System builders have been asking us for a 1-pack for quite some time.
>Creation of the 1-pack has given us the opportunity to make changes which
>simplify the distribution requirements of the OEM system builder license.
>
>When will these changes take place?
>
>All changes – 1-pack, new system builder license, and new system builder COA
>label - will occur in the August 2005 timeframe.
>
>Why did you take away the ability to distribute Windows XP with
>non-peripheral hardware?
>
>In the previous license, while individual Windows XP licenses that were part
>of the 3-pack could be distributed to other system builders with
>non-peripheral hardware, the recordkeeping requirements when distributing in
>this manner were significant. For example, the distributing system builder
>had to ensure the acquiring system builder’s acceptance of the license and
>had to keep records of any such distribution to show that this requirement
>was met. With the availability of the 1-pack, a system builder can order in
>units of one and redistribute that unopened 1-pack to another system builder
>without any hardware, non-peripheral or other, thus eliminating the need for
>this non-peripheral language. A system builder who acquires the unopened
>1-pack can clearly see and be bound by the break-the-seal agreement.
>
>Can I distribute an unopened 1-pack to an end-user?
>
>OEM system builder software is designed for OEM system builders for
>preinstallation on new PCs. The outside of the pack states “Intended for PC
>and server manufacturers or assemblers ONLY”. While unopened packs can be
>distributed to other system builders, they are not intended for end-users. If
>an end-user opens the pack, they are bound by the break-the-seal agreement
>which requires them to preinstall the product using the OPK, support the
>product, and other requirements not appropriate for an end-user who does not
>have the skills and technical knowledge of a system builder. An exception to
>this is when the end-user is actually assembling their own PC, in which case,
>that end user is considered a system builder as well, under the definition in
>the OEM system builder license agreement.
>
>Why do we now have to preinstall applications like Microsoft Office?
>
>We wanted to make the OEM System Builder license consistent in the
>preinstallation requirements for Windows XP and application products like
>Office. In addition, we wanted to ensure the best possible out-of-box
>experience for end users with regard to applications such as Office, which we
>believe will be achieved when Office is preinstalled onto that new PC.
>
>Why does the 1-pack look just like the 3-pack? (note this question will not
>be applicable for North America where the 1-pack packaging will be different
>than the rest of the world)?
>
>In the interest of time and in order to get the 1-pack out in the August
>timeframe, we made the decision to maintain the existing 3-pack packaging. We
>have explored many alternatives and to date the most cost effective and
>readily available solution was the 2-inch box. We are continuing to evaluate
>packaging options and are working on smaller box options.
>
>Why isn’t the OPK included in the 1-pack? How do we get the OPK?
>
>Because a system builder needs only one copy of the OPK, which can be
>acquired via the 3-pack, we heard feedback that including the OPK in every
>1-pack was wasteful and unnecessary because most system builders already had
>an OPK. The OPK will continue to be included in every 3-pack and we are
>looking into other ways for system builders to obtain an OPK.
>
>What do we do with existing inventory of product with the “old” OEM System
>Builder License and/or COA label?
>
>We realize there will be an overlap period between licenses and both license
>types will be in the market for some overlapped period of time. If you are
>carrying inventory of OEM
>System Builder product with the former license agreement/COA, those license
>agreement terms and conditions will be in effect until you distribute the
>product. As you order new
>inventory with the “new” license, the new license terms and conditions will
>be in effect.
>You can continue to distribute any inventory of existing product once the
>new license is out – we do not expect you to replace or exchange your
>existing inventory of product with the “former” license agreement.
>Why are you changing the COA label?
>We are changing the OEM system builder COA label to help differentiate it
>from the COA
>label that is included on direct OEM software. We have found that COAs from
>the direct OEM channel are often distributed illegally to the broader
>channel. With this new COA, you and your customers will be able to
>differentiate OEM system builder product. This is part of our continuing
>effort to help curb piracy and counterfeiting.
>What are the territory restrictions in the new license? Why did you add these?
>Section 3.2 of the new license addresses export restrictions and states the
>following:
>3.2 You may only distribute this package, individual software licenses and
>hardware units within the territory described at
>http://microsoft.com/oem/sblicense/territory. You acknowledge and agree that
>you will not export this package to locations outside of this territory.
>We added this language to the agreement because we have been seeing a
>significant amount of English OEM system builder product, designated for
>distribution in one country, show up in another country, leading to
>cross-border issues.
>
>I’m a PC refurbisher. Can I preinstall OEM System Builder software on the
>systems I refurbish?
>
>Yes, if you are refurbishing a machine you can preinstall OEM system builder
>software onto that system. Please note that software distribution would be
>subject to the distribution requirements documented in section 4 of the OEM
>system builder license.
>
>Where can I go for more information?
>
>Please visit www.microsoft.com/oem/licensechanges or
>http://oem.microsoft.com/licensechanges (registration required) for more
>information.
If the above is actually the case. People are going to get ticked,
That won't be able to reinstall the operating system. (I always do
that to get rid of the unnecessary stuff).
Greg Ro
Facebook
Twitter
Instagram