Embedded Licensing

Purchasing Windows Embedded tools and products

The Windows Embedded comparison table can assist in determining which Microsoft Embedded product is right for you.
Once you have established the best product for your needs, the following purchase process can be followed:

  1. Evaluate the product
    Trial software enables you to evaluate the product prior to purchase. Download or order a copy of the trial version, or contact Avnet Embedded to obtain the trial version of the Windows Embedded product that best fits your needs. With the trial software you can build devices that use Windows Embedded technologies.
  2. Acquire product development tools
    After you’ve completed your evaluation of the Windows Embedded product, contact Avnet Embedded to assist you with getting the appropriate development kit.
  3. Acquire runtime licenses for commercial shipment
    Once you complete testing and development and are ready to bring your embedded system to market, it’s time to procure your runtime licenses and certificates of authenticity (COAs) from Avnet Embedded for each unit that you ship. The cost for each runtime license may vary, based on the volume of licenses purchased over a given period of time.
  4. Subscribe to Microsoft Developer Network (MSDN)
    A Microsoft Visual Studio Professional Edition with MSDN subscription provides a cost-effective way to license Microsoft platforms and tools, receive technical support and obtain early access to the latest Microsoft updates available. MSDN benefits provide developers of embedded devices with a single subscription for access to the Visual Studio suite of software development tools and the following Windows.

 

 

Windows Embedded OEM CLA licensing process

The Embedded OEM Customer License Agreement (OEM CLA) is required to be signed for all Microsoft products purchased through Avnet Integrated Solutions. As a Microsoft Authorised Embedded Distributor, Avnet Integrated Solutions facilitates the licensing process between the Embedded OEM Customer and Microsoft Windows Embedded. The OEM CLA includes the general terms and conditions that govern the licensing of Microsoft Embedded Licensed Products. Embedded OEM customers obtain an electronic OEM CLA form from Avnet Embedded as a link by e-mail. Click the link in the e-mail and fill in and submit the CLA electronically. You will then get a request back from Microsoft to electronically sign the OEM agreement. Once Microsoft electronically countersigns the OEM CLA, an Embedded OEM customer may order runtime licenses through Avnet Embedded.

If you have a third-party installer, please nominate this company as an “Outsource Manufacturer” (OM) in the additional right agreement (ARA) inside the CLA form. An outsource manufacturer can buy the licenses and install the images in the name of an OEM.
You can nominate a “Third Party Integrator” (TPI) as well. A TPI can develop the operating system image and software solution for the OEM. One company can be nominated for both roles. The OEM Customer License Agreement (OEM CLA) remains valid for two years. Microsoft generally contacts OEM customers 45 days prior to their OEM CLA expiration date by e-mail. Your Avnet Integrated Solutions representative will contact you as well. There is only one OEM CLA for all embedded products.

 

 

More tips from your Avnet Embedded team

How to sign the Microsoft Embedded eCLA

  1. Request the eCLA link from your local Avnet Integrated Solutions representative.
    Avnet Integrated Solutions will then enter your contact details into a Microsoft online tool and Microsoft will send you an email with a link to the eCLA.
  2. Microsoft will review the OEM data and send an email directly to the “signer’s” email address with a link to electronically sign the eCLA document. Please note that you can redirect the request to another internal email to sign the agreement. Please eSign the CLA via the online electronic process.
  3. Congratulations! You are now an embedded OEM and are allowed to buy and use Microsoft embedded licenses under the embedded OEM license terms!

If you have questions about the eCLA process, please contact us at microsoft@remove-this.avnet-embedded.eu

 

 

Third-Party integrator

Third-party integrators are companies that the OEM can engage with to create and/or test an image, application, or software driver for systems using Microsoft Embedded products. The OEM must request and receive approval by Microsoft to use a third-party integrator using the Third-Party Integrator Schedule attached to the CLA.

 

 

Outsource manufacturer

An Outsource Manufacturer (OM) is a third party that the OEM can contract to do any of the following:

  • Install an image on an embedded system
  • Manufacture an embedded system
  • Prepare the embedded system for distribution
  • Distribute embedded systems

The OEM must request and receive approval by Microsoft to use a third-party Outsource Manufacturer using the appropriate form available from Avnet Embedded or downloadable from the MyOEM Portal.
The OM can purchase Microsoft Embedded runtime licenses from Avnet Embedded, identifying the OEM and CLA#.
It is common for OEMs to also designate Avnet as an Outsource Manufacture to provide the above listed services on behalf of the OEM. If you have any interest in Avnet Embedded providing embedded software services, please contact your local Avnet Integrated Solutions representative.

 

 

What is a COA?

Each runtime license contains a sticker that is known as a “Certificate of Authenticity” (COA). This is an anti-piracy device, OEM product-tracking device and proof of license for Microsoft OEM products. The COA is non-removable, sequentially numbered and contains additional anti-piracy features. It should be permanently affixed to an accessible location on or within each embedded system. If attaching the COA is problematic, a waiver may be obtained from Microsoft, which allows an unattached COA to accompany the system.

 

 

Reconciling COAs

It is the OEM customer’s responsibility to accurately reconcile the total number of COAs received with the number of systems shipped with Microsoft software. OEM customers should maintain appropriate records regarding the disposition of all COA labels, including serial number tracking of any COAs damaged as part of the manufacturing process.

 

 

Product IDs (PIDs/Keys)

The Product ID (PID) is also known as an Activation Key. This 5X5 sequence of 25 numbers and letters (12345-12345-12345-12345-12345) is used to make the installed Microsoft product “Production Ready.” If the PIP is not activated, installation expires
after 120 days.

Windows for Embedded Systems (FES), Embedded Enterprise (“For Embedded Systems”(FES)) and Embedded Server – These products have each system’s PID printed on the individual COA.

CE, WEPos, POS Ready2009, XP Embedded, Windows Embedded Standard 2009, WES 7 & 8, Win10 IoT and Industry 8.1 – For these licenses, the PID is not printed on the COA.

POSReady7, Industry 8, WES 7 & 8 – For these licenses, the PID is not printed on the COA (Certificate of Authenticity). Instead, you must request a PID application from Avnet Embedded at: microsoft@remove-this.avnet-embedded.eu

For PIDs/Keys, please send PID/Key requests to: microsoft@remove-this.avnet-embedded.eu

 

 

Additional Terms (ATs)

ATs (formerly “Additional Licensing Provisions” or ALPs) define distribution rights and restrictions specific to each individual Microsoft Embedded Licensed Product. To track inventory and accommodate customer packaging requests, the Avnet Integrated Solutions part number, which corresponds to the Microsoft part number, signifies how many runtime licenses and COAs are in each envelope.

For example, an envelope containing one (1) runtime license of Microsoft part #7WT-00011 would be identified as “7WT-00011-1PK”, with larger pack sizes containing “-10PK”, “-100PK” and “-1000PK” suffixes.

 

 

Licensing Provisions

Each envelope has a “Break the Seal” (BTS) Agreement. Breaking the seal to open the envelope signifies that the embedded OEM customer accepts the terms and conditions of the LTs. Once the seal is broken, the runtimes cannot be sent back to Avnet Integrated Solutions or Microsoft. Printed versions of the ATs are attached to the front of the runtime license envelope. However, a copy of these documents can also be obtained from Avnet’s Microsoft team or downloaded from the Microsoft MyOEM Portal.

 

 

Microsoft Software Licensing Terms (LTs)

Each OEM is required to ship with each system the End User Licensing Terms (LTs). This document serves the same function as the End User License Agreement (EULA) that appears on the screen when a customer activates a non-embedded product. For embedded products, this comes in the form of a printed document that includes the name of the embedded OEM. These license terms are an agreement between the end user and the Embedded OEM.

A template for this document is available from your Avnet Integrated Solutions Microsoft team or can be downloaded from Microsoft’s MyOEM Portal. There are different versions of this document for the different types of Microsoft embedded products.

 

 

Recovery Media

OEMs who use Microsoft Embedded are required to deliver the Embedded OS preinstalled on the system. The OEM is also permitted to create media for image recovery, update or field upgrade. Only an OEM or Microsoft Authorised Replicator can
create an image disk. Avnet Integrated Solutions has partnered with several Microsoft Authorised Replicators and can supply the OEM with the image media, making sure that the media meets the guidelines set by Microsoft.