|
Elo
Technical Support Knowledge Base
|
ZEBRA
Customer Support Standard
|
Operating System Licensing Policy: Standalone Sales and NO OS Hardware Limitations
Audience: Elo Customers, Partners, and Distributors
Article type: Customer Advisory / Policy Guide
Applicable Products: EloPOS™, I-Series for Windows, Elo Touch Computers, and Custom Kiosk Engines
Information Overview:
To help our customers successfully manage their software deployments, this article explains Elo’s operating system licensing policies. It covers why standalone Windows licenses cannot be purchased separate from hardware, why Windows recovery media cannot be supplied for units purchased as NO OS, and how to correctly install Windows on these systems.
1. Why Standalone Operating Systems Cannot Be Purchased Separately from Hardware
Elo distributes pre-installed Windows operating systems strictly as a Microsoft Original Equipment Manufacturer (OEM). Under our partnership agreements with Microsoft, there are specific legal guidelines that govern how these licenses are distributed:
- Hardware-Bound Licensing: OEM licenses are legally tied to the specific physical device with which they were originally bundled. Elo is contractually prohibited from distributing standalone Windows software licenses, product keys, or installation media unbundled from physical hardware.
- Authorized Distribution Channels: Elo is licensed to sell complete, integrated hardware and software solutions, not standalone software packages. Customers seeking standalone retail licenses (Full Packaged Product) or corporate volume licenses must purchase them directly from Microsoft or an authorized Microsoft software reseller.
2. Licensing Limitations of "NO OS" Hardware Units
Elo offers "NO OS" configurations for customers who intend to use alternative operating systems (such as Linux) or who utilize their own pre-existing corporate Microsoft Enterprise Volume Licensing agreements.
If you purchase a NO OS hardware unit, please be aware of the following technical and licensing restrictions:
- Absence of Firmware License (OA 3.0): On devices manufactured with a pre-installed Windows operating system, a unique Digital Product Key (DPK) is injected directly into the motherboard’s UEFI/BIOS (specifically inside the ACPI MSDM table) during factory production. Motherboards on "NO OS" units do not contain this embedded digital license.
- Incompatibility with Elo Factory Recovery Images: Elo’s factory recovery images are custom-built to restore the operating system on hardware originally shipped with Windows. Because a "NO OS" unit does not have a factory-injected BIOS key, deploying an Elo recovery image to it will fail activation.
- Legal Limitations on Media Distribution: Elo support teams cannot legally supply Windows installation media, product activation keys, or recovery restore images for serial numbers originally purchased as NO OS units.
3. How to Put a Copy of Windows on an Elo "NO OS" Unit
If you have a NO OS unit and wish to run Windows on it, you can successfully deploy the operating system by following the official licensing and installation pathway:
Required Steps for Windows Installation:
- Obtain a Windows License: Purchase a valid Windows retail license or utilize your organization’s Microsoft Volume Licensing/Enterprise Agreement (such as an Enterprise Agreement or Cloud Solution Provider subscription) through an authorized Microsoft reseller.
- Create Installation Media: Go to the official Microsoft website and use the Microsoft Media Creation Tool to generate a bootable USB installation drive for your licensed Windows version.
- Install Windows and Drivers: Install Windows from the bootable USB drive. After the installation is complete, download and install the certified Elo touchscreen, chipset, and graphics drivers directly from the official Elo Touch Solutions Support Portal to ensure full hardware compatibility.
4. Related Resources
For step-by-step instructions and technical setup details, please review these related articles:
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article