Windows IoT Enterprise LTSC

What is Windows IoT Enterprise LTSC?
Windows IoT Enterprise LTSC (Long-Term Servicing Channel) is a specialized version of Windows tailored for embedded and fixed-purpose devices like ATMs, kiosks, industrial controllers, and medical equipment. It prioritizes long-term stability by avoiding feature updates and offering only essential security and quality improvements for up to 10 years.

What’s the difference between Windows IoT Enterprise LTSC and standard Windows versions like Pro or Enterprise?
LTSC versions are built for devices that require minimal change and high uptime. Unlike Windows Pro or Enterprise (GAC), which receive frequent feature updates, LTSC focuses solely on stability. It’s optimized for embedded systems and licensed for OEM hardware, while GAC versions are intended for general computing.

What processor classes are supported under the Windows 10/11 IoT licensing model?
Windows IoT Enterprise supports a range of processor classes: High-end (Intel Xeon, Core i7/i9), Value (Core i3/i5, Ryzen 5), Entry (Celeron, Atom), and Base (i.MX 8/93). Licensing costs are aligned with processor performance.

Does Windows 11 IoT Enterprise LTSC support ARM processors?
Yes. Windows 11 IoT Enterprise LTSC 2024 supports ARM64 architecture, including processors like Qualcomm Snapdragon and NXP i.MX 9 series, enabling lightweight and power-efficient designs.

Use Cases & Benefits

Who should use Windows IoT Enterprise LTSC?
This version is ideal for OEMs building devices that must operate reliably for extended periods—common in industrial automation, medical monitoring, point-of-sale systems, and digital signage.

Why is LTSC preferred for embedded systems over GAC versions?
LTSC avoids disruptive updates, ensures better compliance with regulatory requirements, reduces total cost of ownership, and minimizes the risk of system instability caused by new features.

Can I use Windows Pro instead of LTSC for an embedded device?
While technically possible, it’s not recommended. Windows Pro is designed for general-purpose computing, lacks embedded-specific features like device lockdown and COA-based licensing, and receives frequent updates.

Can I control when and how updates are applied to LTSC devices?
Yes. LTSC gives you full control over update schedules, making it suitable for environments where stability and uptime are critical.

Windows IoT Licensing and Channels

How is Windows IoT Enterprise LTSC licensed?
It uses a value-based licensing model tied to processor performance tiers (Base, Entry, Value, and High-end). Licenses are bound to the device and delivered via COA stickers.

What is a COA (Certificate of Authenticity)?
The COA is a physical sticker placed on the device, representing the official license. It comes in two formats: ePKEA (one key per OEM) and PKEA (unique key per device).

What’s the difference between OEM IoT Embedded and CSP Volume licensing?
OEM IoT Embedded licensing is for dedicated-purpose systems and allows global deployment. CSP Volume licensing is upgrade-only, tied to end users, and not suitable for embedded appliances.

What’s the difference between ePKEA and PKEA licensing?
ePKEA uses a single key across devices for easier deployment, while PKEA assigns a unique key per unit, offering more granular tracking.

Windows Server IoT

What is Windows Server IoT?
Windows Server IoT is a binary-equivalent version of Windows Server available in both Standard and Datacenter editions, but it is licensed specifically for fixed-purpose appliances and embedded systems.

It is distributed through the OEM IoT embedded channel and is intended for dedicated use scenarios. This version follows Microsoft’s Long-Term Servicing Channel (LTSC), offering a longer support lifecycle and tailored usage rights for edge and IoT applications.

What’s the difference between Windows Server IoT and general-purpose Windows Server?
While both versions share the same features and capabilities, Windows Server IoT is designed for OEMs and is sold only through the embedded channel. It is licensed per device using a Certificate of Authenticity (COA), whereas general-purpose versions are licensed per user or per company through volume or CSP licensing.

Windows Server IoT supports global deployment and has a lifecycle of 10 years, in contrast to the 2–3-year lifecycle and limited use scope of general-purpose server licenses.

Can I use the product keys of the general-purpose channel to activate Windows Server IoT?
No, while both versions share the same features and capabilities, with Windows Server IoT you will need to download the Windows Server IoT version from www.microsoftoem.com and use the product key that’s printed on the Windows IoT COA which you can buy from Arrow.

What is the minimum licensing requirement for Windows Server IoT?
To comply with Microsoft’s licensing terms, OEMs must license a minimum of 16 cores per physical server, regardless of how many cores the server has.

Each processor must have at least 8 cores licensed. If additional cores are needed, add-on licenses are available in 4-core increments.

How do I license virtualization and failover scenarios with Windows Server IoT?
Licensing must cover the worst-case scenario where all virtual machines (VMs) may run on a single host. For example, in a failover configuration, even passive or backup servers must be fully licensed.

The Datacenter edition is recommended for these situations, especially in hyper-converged systems, because it allows unlimited VM instances.

Do these special editions require Client Access Licenses (CALs)?
Microsoft offers several CAL-free editions under the IoT channel, each designed for specific use cases. These special editions are exempt from CAL requirements, which can significantly reduce licensing costs and complexity for OEMs deploying dedicated-purpose server appliances.

Who is eligible to purchase and use Windows Server IoT licenses?
Only OEMs with valid CLA building fixed-purpose systems with the operating system and application pre-installed on the device are eligible. These licenses are not intended for resale to end-users or for use on general-purpose servers.

SQL Server IoT

What is SQL Server IoT?
SQL Server IoT is a special license-only edition of Microsoft SQL Server, designed specifically for embedded and dedicated-purpose devices. It provides the same binaries and capabilities as the commercial version of SQL Server, including support for advanced analytics and seamless cloud integration with Azure services. However, it is distributed exclusively through the OEM embedded channel and intended for use in fixed-function appliances.

How is SQL Server IoT different from commercial SQL Server?
While both versions offer the same technical capabilities, SQL Server IoT is sold only through the OEM IoT channel and is licensed on a per-device basis using a Certificate of Authenticity (COA). In contrast, commercial SQL Server is available via volume or CSP licensing and follows per-user, per-core, or per-VM licensing models.

SQL Server IoT is intended for fixed-purpose appliances with pre-installed, single-purpose applications, whereas the commercial version is suited for broad enterprise use. From a cost perspective, SQL Server IoT is significantly more economical for OEM deployments.

What types of devices benefit from SQL Server IoT?
SQL Server IoT is ideal for OEM-built appliances that require robust data handling and reliability. These include medical data management systems, retail point-of-sale (POS) back-end analytics, industrial edge servers for telemetry and diagnostics, and telecommunications servers with integrated analytics.

How is SQL Server IoT licensed?
SQL Server IoT offers two licensing options:

1. Server + CAL: Purchase a SQL Server instance license and acquire separate Client Access Licenses (CALs) for each user or device that accesses the server.
2. Per Core: Purchase SQL Server Per Core licenses, with a minimum of four cores. This option allows for unlimited users and devices.

Can I run SQL Server IoT on a virtual machine (VM)?
Yes, SQL Server IoT can run on a VM; however, the licensing requirements apply to the physical host machine. OEMs must still license all physical cores of the host system if SQL Server IoT is deployed in a virtualized environment, similar to standard SQL Server licensing policies.

Can I use SQL Server IoT in regulated industries?
Absolutely. SQL Server IoT includes advanced features like SQL Ledger, which provides cryptographic verification of data changes. This makes it particularly well-suited for industries with strict regulatory requirements such as finance, healthcare, and government sectors.

I have received a SQL Server IoT COA, where is the product activation key?
The product activation key for SQL Server is already embedded in the OPK which you can download from www.microsoftoem.com.

Getting Started

How do I get started with Windows IoT Enterprise LTSC, Windows Server IoT, and SQL Server IoT?
Begin by signing a Microsoft Customer License Agreement (CLA), then consult Arrow to select the right SKUs and processor tiers. Order your COAs and utilize Arrow’s services for image creation, branding, and deployment. Get started by filling out the CLA form or contact Arrow at windowsiot@arrow.com. Our experts will reach out to you within 24 hours.

Where can I find the Microsoft IoT parts list, including part numbers and lifecycle information?
Visit the Parts List section on Arrow.com to access the full Microsoft IoT parts list. It includes details such as part numbers, part names, COA types (ePKEA, PKEA), as well as key lifecycle dates like End of Life (EOL) and End of Support (EOS). This resource helps you identify the right SKUs for your device and ensures compliance with Microsoft’s licensing timelines.

Why is it important to understand the End of Support (EOS) and End of License (EOL) dates for Windows IoT products?
Planning ahead allows you to update your platform, initiate migration, or apply for downgrade rights in time—avoiding last-minute disruptions to your product lifecycle.

• When a product reaches End of Support, Microsoft stops providing security patches, hotfixes, and technical assistance—posing potential compliance and security risks.
• When a product hits End of License, it can no longer be shipped with a valid COA, which impacts manufacturing and distribution.

For a most up-to-date roadmap of Windows 11 IoT, Windows 10 IoT, Windows Server IoT, and SQL Server IoT, please refer to our Roadmap and Support Schedule page.

What is the typical workflow for licensing and deploying a Windows IoT system?
Start by consulting Arrow, sign the CLA, select SKUs, download ADK and customization tools, request keys, build and test your image, apply COAs, and begin shipping your devices.

Does Arrow provide system integration services?
Yes. Arrow offers full imaging, lockdown, hardware branding, and global logistics support to help streamline your deployment process.