What is Windows IoT/Embedded
Windows IoT/Embedded— the family of Microsoft operating systems designed for use on computing devices that perform specialized functions that are not general purpose office and home PC.
Purchase process of Windows IoT/Embedded
Step by step guidance to get started with Microsoft IoT/Embedded product family:
Step 1: Sign Microsoft Customer License Agreement (CLA ). Electronic form, usually it takes several hours. Valid for 5 years.
Step 2: Sign an agreement with Quarta IoT LLC, paper form, 1 day. Valid for 5 years.
Step 3: Agree with the manager about the type of license and cost, and place an order for the required number of licenses (rights to use).
Step 4: Pay the invoice received by email and get the rights to install and distribute under the act of transfer of rights, as well as stickers-certificates of authenticity. Usually 1-2 days, but some items are delivered to order - 1-2 weeks.
Step 5: Download the distribution kit in electronic form. The multiple activation key is requested in a separate form or placed on the certificate sticker.
In the future, with new orders, it is enough to repeat steps 3 and 4
To get started, leave your contacts and comments below - we will assign you a personal manager who will send you a CLA application form and an agreement form. If you are interested in cost - briefly describe your device and indicate the processor model. This will speed up the cost calculation process.
Frequently asked Questions
What is the difference between Windows IoT/Embedded channel from others
- licenses has a lower cost, and the licensing model is simpler: one key for all devices, activation is not required in some versions ;
- a separate OEM channel with its own license agreements optimized for manufacturers;
- long period of OS availability for acquisition: 10–15 year;
- there are products in the Windows IoT/Embedded product family that are no longer available in other channels (Windows 7, Windows 8.1);
- guaranteed 10 years support of all releases;
- ready-made OS images with free testing up to 6 months;
- license stickers and multiple activation keys;
- for Windows 10 the price depends on the performance of the CPU: the slower the CPU, the lower the price
Who is the IoT/Embedded-dustributor
Windows Embedded and Windows 10 IoT are sold through a special Microsoft distribution channel and are not available from "classic" Microsoft distributors
Quarta IoT LLC — official Microsoft IoT distributor with over 20 years of experience with Microsoft technologies.
Quarta IoT LLC — official Microsoft IoT distributor with over 20 years of experience with Microsoft technologies.
What is an IoT/Embedded – device
According to Microsoft policy, the Windows Embedded and Windows 10 IoT Enterprise LTSC line of operating systems can be used only on computer devices with a specific purpose. Unfortunately, we will not be able to supply these operating systems for universal office and home PCs. If you are in doubt whether an IoT/Embedded license is right for you, describe the device and usage scenario, and we will help you.
What is CLA Agreement
The same way as in OEM supply channel, you need to sign an agreement with Microsoft - the Customer License Agreement (CLA). The agreement is signed electronic and is valid for five years. The agreement describes all general rights of manufacturer to Microsoft Windows Embedded and Windows IoT software. When fill the contact details in the questionnaire received from our employee, you will receive a link to an electronic document that you will check and sign by clicking the "Sign" button. It should be done once, at the beginning of work, after 5 years it will be possible to update the CLA by clicking on the appropriate link.
Activation keys
There are 2 types of key, which is selected depending on the needs of manufacturer. The dongle type is indicated in the product name, for example "Win 10 IoT Ent 2019 LTSC MultiLang ESD OEI High End EPKEA". Pay attention to this when ordering!
1. EPKEA: Multiple Activation Master Key. Obtained for an OS image by submitting a request form to Microsoft, after signing the CLA. Convenient for most manufacturers, since it does not require a key to be entered into each image, it is enough to add it once to the master image before pouring it onto the equipment.
2. PKEA: Separate key for each OS image. For special cases, for example, when the image is delivered separately from the device (Field Upgrade), not to transfer the multiple activation key to the customer.
1. EPKEA: Multiple Activation Master Key. Obtained for an OS image by submitting a request form to Microsoft, after signing the CLA. Convenient for most manufacturers, since it does not require a key to be entered into each image, it is enough to add it once to the master image before pouring it onto the equipment.
2. PKEA: Separate key for each OS image. For special cases, for example, when the image is delivered separately from the device (Field Upgrade), not to transfer the multiple activation key to the customer.
Licensing
Due to the peculiarities in licensing for corporate clients (Enterprise customer) specified in the Customer License Agreement (CLA) (for information only) and Program Execution Guide (PEG), you can supply equipment and Windows IoT/Embedded to the customer in the 3 options:
*When a device is delivered to an end customer without Windows IoT/Embedded pre-installed, COA labels anyway must be delivered with the device by placing it on the device or, if it is not possible or practicable, on accompanying media or documentation. Also, you need to provide an image of the operating system
- With a pre-installed application and Windows IoT/Embedded (for all variants);
- No pre-installed application, only with Windows IoT/Embedded (only for delivery to a corporate client);
- No pre-installed application and no pre-installed* Windows IoT/Embedded (for enterprise delivery only).
*When a device is delivered to an end customer without Windows IoT/Embedded pre-installed, COA labels anyway must be delivered with the device by placing it on the device or, if it is not possible or practicable, on accompanying media or documentation. Also, you need to provide an image of the operating system