Share via

Windows XP Embedded Licensing Requirements and Guidelines

  • Article

The following information provides guidance in licensing the Microsoft XP Embedded tools for developing your devices and in licensing Microsoft Windows XP Embedded run-time images for distribution with your devices. This topic contained is informational and is provided as a convenience. If there is any conflict between this information and the licenses for Windows XP Embedded or Runtimes, the terms of the licenses will control.

The licensing process for Windows XP Embedded involves:

  • Purchasing a Windows XP Embedded License to begin building your device image.
  • Purchasing a Windows XP Embedded Runtime License for each device that you will sell.

Windows XP Embedded Licenses

To create a customized Windows XP Embedded image, you must first purchase a license for Windows XP Embedded, which contains Windows Embedded Studio, the development tools necessary to build your image.

Each Windows XP Embedded Toolkit License allows you to install one copy of the Windows® Embedded Studio for Windows XP Embedded development tools, and one copy of the component database and Microsoft SQL Server Desktop Engine (MSDE). With a single Windows XP Embedded Toolkit License, you can install all of these on the same computer, or you can install the development tools on one computer, and the component database and MSDE on another computer. In a team environment, you must purchase an additional Windows XP Embedded Toolkit License for each computer on which you install the Windows Embedded Studio development tools - that is one toolkit license for each computer you use for developing or building images.

Runtime Licenses

A runtime operating system license is required in order to sell devices that contain the customized Windows XP Embedded image. Windows XP Embedded run-time image licenses can be ordered in single units.

To reproduce and distribute Windows XP Embedded, you must acquire one (1) Windows XP Embedded run-time image license for each computing device or system that incorporates the Windows XP Embedded operating system. Each Windows XP Embedded run-time image license includes a serialized PID number and a Certificate of Authenticity (COA) sticker. A valid PID number is necessary to generate a target operating system image for distribution. A Certificate of Authenticity sticker must be attached directly to each device or system that incorporates the Windows XP Embedded operating system. If the PID number is not valid, or you do not specify a PID when you build a configuration, Windows XP Embedded will not generate a distributable image. Instead, it will create a 90 to 180 day evaluation-only version of your run-time image.

Device Limitations/Limited Use of Product

Licensee may not use or include Windows XP Embedded, the Windows XP Embedded run-time images, or any components thereof, in (i) the development of a general purpose computing device or (ii) any device or system in which a malfunction of the operating system would result in foreseeable risk of personal injury, death to the operator of the device or system, or to others, or severe physical or environmental damage.

Definition of an Embedded System

An "embedded system" is any computer system or computing device that performs a dedicated function or is designed for use with a specific embedded software application.

Embedded systems may use a ROM-based operating system or they may use a disk-based system, like a PC. But an embedded system cannot be used as a commercially viable substitute for multipurpose computers or devices.

This limits the use of office automation/personal computing functions (e-mail, word processing, spreadsheets, database, network browsing, scheduling, and personal finance) permitted with the particular embedded licensed product.

Windows XP Embedded is licensed for devices that perform Office Automation and Personal Computing Functions only to the extent that the Office Automation and Personal Computing Functions: (i) directly support the operation of, and are an integral part of, the Embedded Application (defined below); and (ii) operate only when used with the Embedded Application (that is, the Office Automation and Personal Computing Functions shall only permit creation, play, display, or communication of content that is directly related to the commercial or industrial processes or tasks that the device is specifically designed to address).

An "Embedded Application" means industry- or task-specific software programs and/or functionality that provide the primary functionality of the device and which offer significant functionality in addition to Windows XP Embedded.

Definition of General Purpose Device

A "general purpose device" is any computer device or system whose functionality allows unrestricted use of, or access to, "Office Automation and Personal Computing Functions." Office Automation and Personal Computing Functions refer to consumer or business tasks or processes, including (but not limited to): e-mail, word processing, spreadsheets, database, network/Internet browsing, scheduling, and personal finance. Office Automation and Personal Computing Functions include features and functions derived from Windows XP Embedded, as well as features and functions derived from other software used on the device.

For more information, see your License Agreement on the Windows XP Embedded discs, and Licensing a Run-Time Image in the Windows XP Embedded Studio Help.

Last updated on Wednesday, October 18, 2006

© 2006 Microsoft Corporation. All rights reserved.