How to license Microsoft Windows Embedded

Windows Embedded licensing is defined in a way to allow a low upfront investment as the majority of the cost involved only applies once your device is ready for shipment and successful selling.

A general illustration on how to license Microsoft Windows Embedded products is described below. The licensing process may vary per product and is subject to change, so please check with your local Avnet Silica Microsoft Embedded Expert for exact details.

Licensing steps:

Stage 1

Pre-Sales

• Embedded OEM Customer (OEM) contacts Avnet Silica, Microsoft Authorized Embedded Distributor.
• OEM obtains evaluation software or purchases a full version toolkit from Avnet Silica.
• Avnet Silica provides a link per e-mail of appropriate Embedded OEM Customer License Agreement (OEM CLA) and Additional Licensing Provisions (ALPs) at time of toolkit purchase.
  

Embedded OEM Customer License Agreement (OEM CLA)

Standard general terms and conditions that must be signed by and OEM in order to acquire Microsoft Embedded licensed products. See section CLA for more details.

Additional Licensing Provisions (ALP)

ALPs define product use rights and restrictions specific to each individual Microsoft Embedded licensed product. The ALPs can be found on the Associated Product Material (APM) packaging supplied by Avnet Silica, provided from a Microsoft Authorized Replicator (AR). See section BTS / ALP form more details.

Stage 2

Sign OEM CLA (Agreement)

• OEM Customer signs OEM CLA electronically.
• For eligible products, Avnet Silica provides the OEM Preinstallation Kits.
  

OEM Preinstallation Kit (OPK)

Microsoft provides the software to create the image as a download from a secured website. The access can be granted after the CLA is activated. In the Embedded Channel some products were designed as desktop products, however Microsoft has included licensing provisions or embedded restrictions which indicate how the product can be customized.

Stage 3

Sales

• OEM completes development of the master embedded image.
• OEM contacts Avnet Silica to order Runtime Licenses and Associated Product Materials (APM).
  

Runtime Licenses

Allows the OEM to replicate the Image based on the Microsoft Embedded Licensed Product, across a line of Embedded Systems. After ordering Runtime Licenses the OEM will receive the Associated Product Materials (APM) from Avnet Silica. APM are materials Microsoft may change from time to time but are required for distribution of the Embedded System. APM typically consists of two items—the COA and the ALP which include licensed product specific End User License Agreement (EULA) terms. Each Embedded System aimed for distribution requires a Runtime License.

Stage 4

Sales

• Customer enters runtime key into embedded Image.
  

Runtime Key (PID)

An alpha-numeric string, located on the COA or specifically requested from Microsoft, designated to each Microsoft product that provides a unique identification number. Runtime Keys are used to prove authenticity and flash an Image across a line of embedded systems.

Stage 5

Distribution

• Customer manufactures and distributes embedded systems with a Certificate of Authenticity and End User License Agreement as specified in the CLA.
  

Certificate of Authenticity (COA)

A serialized label, affixed to devices containing Embedded Microsoft operating systems. The COA is the primary antipiracy and product tracking tool and establish a proof of license. The product specific name is printed on the label. See section COA for more details.

End User License Agreement (EULA)

As the terms and conditions must be passed on to the end user, the EULA needs to be shipped together with the OEMs device. See section COA for more details.

Microsoft OEM Customer License Agreement for Embedded Systems ("CLA")

To use Microsoft Embedded or IoT products, you need to become an OEM. That’s done by entering into an OEM Customer License Agreement (CLA) with Microsoft. The agreement gives OEM right to you and requires a special handling of the licenses. It grants you worldwide selling rights for your solution, based on hardware, software and your application. Your allowed to create own recovery medias and use language independent licenses. The CLA will be done over a secured internet portal from Microsoft.

The CLA is cost free and does not include any minimum quantity or pricing. It’s a base licenses agreement, covering all available products in this licensing option.

The actual CLA version 7.0 consist of the CLA itself, the PEG (Program Execution Guide) and the OPD (OEM Policy Document).

Please contact us for further information about the CLA and licensing process.

License Terms (formerly EULA)

Microsoft Software License Terms (License Terms) for Embedded Operating Systems is the new name for the formerly "End User License Agreements" or "EULAs". License Terms are terms of use that govern an end customer's use of Licensed Products on Mobile Devices, Specialized Servers, and other Embedded Systems.

OEMs must include the appropriate License Terms with each Embedded System or Device that they distribute. The end user must be informed before the purchase, that license terms apply. Please contact us at microsoft[at]avnet[.]eu, if you need the latest License Terms.

msembedded content library/avnethome/licensing/licensing/mse licensing how to text (lc) MSe Licensing how to text (LC)

MSe Licensing how-to side menu (GBLS)

Read about further licensing topics:

• How to license Microsoft Windows Embedded
• Additional Rights Agreements
• License Sticker
• Product Identification
• OEM Preinstallation Kit
• Customer License Agreement
• Additional Licensing Provisions
• End of License and End of Support Dates
• License Terms

msembedded content library/avnethome/licensing/licensing/mse licensing how-to side menu (gbls) MSe Licensing how-to side menu (GBLS)

MSe SHARED general Contact box (GBL)

Contact Us

Need local assistance for your Microsoft Embedded Solution? Let us know!

msembedded content library/shared elements/mse shared general contact box (gbl) MSe SHARED general Contact box (GBL)

About Avnet

• About Avnet Inc.
• Investor Relations
• Global Avnet News
• Avnet EMEA Overview
• Careers

Resources

• Design Hub
• IoT Podcast
• Avnet Newsletters
• Training & Events
• Certifications

Help

• Accessibility
• Environmental, Social and Governance
• Human Rights
• Conflict Mineral Policy
• Contact Us

To view the site in German language, you need to set the preferred language of your browser to German.

Your Privacy Your Privacy When you visit any web site, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer. Strictly Necessary Cookies Always Active Strictly Necessary Cookies These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site may not work then. Cookies used

ak_bmsc This cookie is associated with Akamai and is used to differentiate between traffic from humans and bots

avnetCookieAcceptance This cookie is to track if you have accepted the cookie policy. It will be random characters to create a unique id for you. This id will be stored in a database on a server that Avnet owns and would be used to filter the cookies that you have chosen to allow/deny.

bm_sv This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website.

LtpaToken2 This cookie contains the value of WebSphere Application Server LTPA token used for single sign on.

pathNameAbacus This cookie is used to return the user back to the previous page after Login is completed.

pathNameEbv This cookie is used to return the user back to the previous page after Login is completed.

pathNameSilica This cookie is used to return the user back to the previous page after Login is completed.

speedboatQuery This cookie is used to return the user back to the previous page after Login is completed.

speedboatQueryAbacus This cookie is used to return the user back to the previous page after Login is completed.

speedboatQueryEbv This cookie is used to return the user back to the previous page after Login is completed.

speedboatQuerySilica This cookie is used to return the user back to the previous page after Login is completed.

BIGipServerisam-webseal-pci.443 This cookie is set from the Big IP proxy servers that provide additional security on Avnet's websites

Performance Cookies Performance Cookies These cookies allow us to count visits and traffic sources, so we can measure and improve the performance of our site. They help us know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies, we will not know when you have visited our site. Cookies used

s_ecid This cookie is set by the customer’s domain after the AMCV cookie is set by the client. The purpose of this cookie is to allow persistent ID tracking in the 1st party state and is used as a reference ID if the AMCV cookie has expired.

s_cc This cookie is set and read by the JavaScript code to determine if cookies are enabled (set to “True”)

s_sq This cookie is set and read by the JavaScript code when the SelectMap functionality or the Activity Map functionality are enabled; it contains information about the previous link that was selected on by the user.

Targeting Cookies Targeting Cookies These cookies are set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant ads on other sites. They work by uniquely identifying your browser and device. If you do not allow these cookies, you will not experience our targeted advertising across different websites. Cookies used

demdex Audience Manager sets this cookie to assign a unique ID to a site visitor. The demdex cookie helps Audience Manger perform basic functions, such as visitor identification, ID synchronization, segmentation, modeling, reporting, and so on.

everest_g_v2 Created after a user initially clicks a client's ad, and used to map the current and subsequent clicks with other events on the client's website.

More Information Cookie policies In the spirit of fair and transparent processing of personal data, this policy provides detailed information about how and when we use cookies and/or other analytics tools. This cookie policy applies to any Avnet product or service that links to this policy or incorporates it by reference. Abacus Cookie Policy
Americas Cookie Policy
APAC Cookie Policy
EBV Cookie Policy
EMEA Cookie Policy
Japan Cookie Policy
Silica Cookie Policy

Your privacy is important to us.
We use cookies to enhance your experience when visiting our websites: performance cookies show us how you use this website, functional cookies remember your preferences and targeting cookies help us to share content relevant to you. Select "Accept all" for giving your consent to all cookies, select "Cookie settings" for managing the different cookies or select "Reject all" for using only strictly necessary cookies. You can change your cookie settings at any time by clicking on the cookie settings link on the website.