Foreword -- Contributed by Lynda Allen and the Windows Embedded Test Team, this whitepaper gives a high-level summary of the differences between the existing product, Windows Embedded Standard 2009 (based on Windows XP) and Windows Embedded Standard 2011, based on Windows 7. It focuses on some of the operating system (OS) feature differences, and compares the tools and OS building models.A comparison between Windows Embedded Standard 2009 and Windows Embedded Standard 2011
by Lynda Allen
Overview
Windows Embedded Standard 2011 (formerly code-named
“Quebec”) is the next generation platform within the Windows Embedded Standard
portfolio and delivers the power, familiarity and reliability of the Windows 7
operating system in a highly customizable and componentized form. This article
will give a high-level summary of the differences between the existing product,
Windows Embedded Standard 2009 (based on Windows XP) and this latest product.
It will focus on some of the operating system (OS) feature differences, as well
as compare the tools and OS building models.
It must be noted that not all the features and technologies
listed in this comparison will be immediately available on Windows Embedded
Standard 2011. Some of these features or technologies may be partially
available immediately, or be made available in subsequent releases after the
initial product has been released. Features that are available immediately are
designated with an asterisk (“*”).
General Comparison
|
|
Windows
Embedded
Standard 2011 |
Windows
Embedded
Standard 2009 |
|
Windows
7 technologies |
Same
as Windows 7
Business Edition * |
Subset
of Windows 7
features available |
|
Image
Build Tools |
Windows
Embedded Studio:
|
Windows
Embedded Studio Toolkit:
-
Target
Designer
-
Component
Designer
-
DB
Manager
-
Target
Analyzer
-
SDI
support
|
|
Image
Build Model |
Image
configured on device or on developer machine *
Image
is assembled on the device *
Features
can be added post-build directly to device *
Distribution
share to
hold files and packages * |
Image
is configured and assembled on developer machine
Image
is deployed to device
Adding
features requires an image refresh
Component
database and
repository |
|
Processor
and Hardware
Support |
32-bit(x86)
and 64-bit (x64)*
Minimum
1GB storage and
512MB RAM * |
32-bit
(x86)
Minimum
128MB storage and
256MB RAM |
|
OS
Image Footprint |
Minimum
Image size >
300 MB |
Minimum
Image size >
40 MB |
|
OS
Building Blocks |
OS
feature packages~ 100s (partial *)
Driver
packages ~1000
Embedded
Core * |
OS
components~ 1000
Driver
components~9000 |
|
Localization |
Developer
Tools
OS
Image (partial *)
Documentation |
OS
Image
Documentation
(localized
into a sub set of languages) |
|
Deployment
Methods |
Windows
Deployment Servicing (WDS) *
Windows
Pre-installation Environment (WinPE) 3.1 or latest *
CD\DVD
boot and
USB
Boot *
Remote
Boot
|
PXE
Boot, Remote installation
Windows
Pre-installation Environment (WinPE) 1.0
CD\DVD
boot and USB Boot
Remote
Boot
|
|
Embedded
Enabling
Features |
Write
Filter parity with Standard 2009
Potentially
SD Boot and VHD boot
Improved
custom shell support *
Device
Update Agent (DUA)
|
Enhanced
Write Filter (EWF), File Based Write Filter (FBWF), Registry
Filter (RegFilter)
CD\DVD
boot and USB Boot
Custom
shell support
Device
Update Agent (DUA)
|
|
Servicing |
OEM
Servicing
Device
Automatic Servicing (Windows Update) *
Device
Manual Servicing |
OEM
Servicing
Device
Manual Servicing |
|
Activation |
Not
required |
Not
required |
|
Customer
Connection to the Product Team |
Support
for Software Quality Metrics (SQM) in developer tools
Links
to forums, MSDN,
and product team blogs |
Links
to team blogs and
forums |
Details
Setup
The setup experience in Windows Embedded Standard 2011 is improved by simplifying the installer process since SQL Express does not have to be installed as a prerequisite. Setup does require .NET 3.5, which is included in the installer and will automatically be installed if it is not present on the developer workstation.
Other differences between Windows Embedded Standard 2011 and Windows Embedded Standard 2009 include:
- Windows Embedded Standard 2009 has a component database, and Windows Embedded Standard 2011 has distribution shares (one for x86 and another for amd64) that contain the feature sets.
- Windows Embedded Standard 2009 MUI packs need to be installed separately, while Windows Embedded Standard 2011 includes the language packs in the distribution shares.
- Windows Embedded Standard 2009 integrates Remote Boot Server setup into the installer; Windows Embedded Standard 2011 does not include Windows Deployment Server in its setup.
Build Tools
The build tools are completely new for Windows Embedded Standard 2011. Image Configuration Editor (ICE) is used to customize a Windows Embedded Standard 2011 image. Windows Embedded Standard 2009 has three tools, Target Designer, Component Designer and Database Manager, in its suite of tools.
In Windows Embedded Standard 2011, there is an improved process to search for file names and registry keys/values/data in ICE. New functionality includes:
-
Ability to import packages into the distribution share.
-
Ability to encrypt passwords in unattend files and hide sensitive data.
-
Ability to create a configuration set.
-
Easy deployment options through media creation in ICE.
-
Ability to insert path of 3rd party drivers.
-
Ability to specify OEM folder paths in order to install applications.
-
Concept of including or omitting optional dependencies during image configuration.
Deployment
Windows Embedded Standard 2011 contains Image Builder Wizard (IBW), which allows the rapid development of images by booting into IBW, customizing the composition of the image, and installing directly to the device. IBW also allows for installations with answer files or configuration sets and can be run from a USB flash drive. Standardized answer files can be used across deployment stages – including initial setup, Sysprep, and re-deployment. Windows Embedded Standard 2009 requires that the image be configured and built on a developer workstation in Target Designer and then deployed to the device.
Windows Embedded Standard 2011 supports well known utilities which are also used for Windows Client and Windows Server to facilitate mass deployment of images created on the factory floor:
- Windows Deployment Server is the replacement for PXE installations that utilized Remote Boot Server in Windows Embedded Standard 2009.
- Windows Embedded Standard 2011 fully supports Sysprep scenarios as defined for non-embedded Windows versions. Windows Embedded Standard 2009 uses the System Cloning Tool, and partially supports Sysprep.
- Windows Embedded Standard 2011 WIM images can be applied with the ImageX utility provided in WinPE 2.0.
Drivers
Inbox drivers in Windows Embedded Standard 2011 are offered as driver packages and not components as in Windows Embedded Standard 2009. There are currently around 400 driver packages versus 9000 driver components in Windows Embedded Standard 2009. In addition, Windows Embedded Standard 2011 includes basic drivers by default in the Embedded Core, which will get installed if you choose not to add specific driver packages.
Tap.exe is available in Windows Embedded Standard 2011, as it is in Windows Embedded Standard 2009, but can be run as part of an IBW installation. Hardware files created by tap.exe (.pmq files) can be imported into IBW in Windows Embedded Standard 2011, as they could be in Target Designer in Windows Embedded Standard 2009.
Drivers can be added to an image in various ways in Windows Embedded Standard 2011- using IBW or the DISM.exe utility online or offline. Driver packages are serviceable in Windows Embedded Standard 2011 in the same way that feature sets are serviceable.
There are language resources for some drivers in Windows Embedded Standard 2011 that are not available in Windows Embedded Standard 2009. Some drivers will only work on 32-bit or 64-bit platforms- in Windows Embedded Standard 2009 only x86 drivers are supported. As with Windows Embedded Standard 2009, driver installation scenarios in Windows Embedded Standard 2011 depend on the correct devices being installed, as well as the necessary dependencies to be satisfied.
Servicing
The way Windows Embedded Standard 2011’s OS image is serviced is completely different than Windows Embedded Standard 2009. The differences are as follows:
- File/registry key/Inf file based servicing has been replaced by Component Based Servicing (CBS). In the CBS model, system inventory is maintained through the Component Servicing Infrastructure (CSI) layer in the OS. System integrity is better guaranteed by a servicing component encompassing a set of dependent files and registry keys so all dependencies are well enforced. CBS resolves inconsistent system states when pending reboot by treating system changes as atomic transactions. All installations (not just servicing installations) are handled by CBS through the CBS and CSI servicing APIs, and applicability is determined by querying the CBS and CSI metadata. With CBS, updates do not overwrite existing files; therefore, if an update is uninstalled the system will roll back to its previous version, which avoids an unstable system state.
- Windows Embedded Standard 2011 has a new tool called Package Scanner, which allows easy identification of updates that are applicable to your device. It also allows removal, or scavenging, of all previous versions of an update that have been updated with a newer version.
- Service packs can be applied directly to a runtime, either online or offline. With Windows Embedded Standard 2009 an image refresh is required.
- Windows Embedded Standard 2011 utilizes Windows Update for feature
updates (but not for driver updates), which has a rich control panel
applet and some command line tools to check, download and install the
update packages . This is not available in Windows Embedded Standard
2009.
Existing Features
File Based Write Filter (FBWF)
File Based Write Filter FBWF is a write filter which helps maintain a stateless disk by redirecting all disk writes on a protected file system to an in memory cache in a transparent manner. On reboot, all the file data is lost and the user is reverted back to the original disk.
The scenario of protecting the disk from writes is not different in Windows Embedded Standard 2011 or Windows Embedded Standard 2009, but in Windows Embedded Standard 2011 there is:
- Limited support for amd64
- Support for reparse points
- Better integration with removable devices and stability fixes
Power Management
The Power Management package enables users to manage the power plan on machines. In Windows Embedded Standard 2011, there is new functionality, such as new parameters for powercfg.exe and the availability of the power policy, and power meter WMI providers for power management.
The new parameters enabled for powercfg.exe are:
-
-requires (enumerates application and driver power requests).
-
-requestsoverride (sets a power request override for a particular process, services, or driver).
-
-energy (evaluates the system energy efficiency). This functionality is only enabled by adding an optional dependency when configuring the image.
-
Powercfg.cpl -this also requires an optional dependency to be satisfied.
Power management works with FBWF enabled, and works on both x64 and x86 systems.
Directory Services
The Directory Services package manages the naming and address relationship of objects within a networking system. Directory services also provide security and access control, such as integrating with Access Control Lists. The DNS snap-in, viewing property pages and searching for people or printers requires an optional dependency for MMC to be included.
Shell
In Windows Embedded Standard 2011, all shell feature sets offer an improved taskbar, full-screen previews and jump lists to recently used files. The shell feature sets also support desktop enhancements like Snaps and window transparency.
Device Management
The Devices and Printers package offers one place to connect, manage and use printers, phones and other devices. Device Stage is a new technology that helps you interact with any compatible device connected to your computer. From Device Stage you can see the device status and run common tasks from a single window. Device manufacturers can also customize Device Stage.
File System
Windows Embedded Standard 2011 may offer VHD boot support in the future. It does offer new functionality in disk management, such as shrinking a volume to free up space. In Windows Embedded Standard 2009 the volume has to be deleted in order to free up space.
.NET Framework
Windows Embedded Standard 2011 includes .Net Framework 3.5 SP1, while Standard 2009 includes .Net Framework 3.5 by default.
Installers (Third-Part App Support)
Windows Embedded Standard 2011 includes MSI Installer 5.0, while Windows Embedded Standard 2009 has version 3.5.
Remote Desktop
Both Windows Embedded Standard 2011 and Windows Embedded Standard 2009 use Remote Desktop Protocol 6.1.
Microsoft Management Console (MMC)
Windows Embedded Standard 2011 includes the MMC 6.1, while Windows Embedded Standard 2009 includes MMC 5.1.
New Features in Standard 2011
Graphic API
The Graphic API feature set is new in Windows Embedded Standard 2011, offering a hardware-accelerated API and Microsoft Windows Codecs Extended Library.
Dialog Filter
Dialog Filter is new in Windows Embedded Standard 2011. It provides the ability to automatically send window messages to most windows appearing on the active desktop, such as “close”, “cancel”, or “continue”. The customer can configure Dialog Filter through an editor tool to send any button message to a process message loop and declare which messages are sent to specific windows.
Windows Embedded Standard 2011 includes the installable features that support branding. The embedded developer can remove branding from the logon and desktop backgrounds, including strings and brands found during power management transitions.
Secondly, Windows Embedded Standard 2011 exposes the same credential provider interface as Windows 7. Credential provider samples are provided in a separate MSDN download.
- Message Box auto reply is provided in both Windows Embedded Standard 2011 and Windows Embedded Standard 2009. Message Boxes are largely replaced by a new control, Task Dialogs, for Windows Embedded Standard 2011. The embedded developer should use the Dialog Filter to manage windows on the active desktop.
- Dialog Filter includes a 64-bit service and a 32-bit service (Wow64) in the Windows 7 64-bit edition and will process window messages from both 32-bit and 64-bit window processes without observed differences.
PowerShell v2
Windows Embedded Standard 2011 includes the PowerShell 2 feature set, which is a new command line shell and task-based scripting technology that provides administrators with comprehensive control and automation of system administration tasks, increasing administrator productivity. Windows PowerShell includes numerous system administration utilities, consistent syntax and naming conventions, and improved navigation of common management data such as the registry, certificate store, or Windows Management Instrumentation (WMI). Windows PowerShell also includes an intuitive scripting language specifically designed for IT administration.
Internet Explorer 8
Internet Explorer 8 is included in Windows Embedded Standard 2011Standard 2011, while Windows Embedded Standard 2011 2009 ships with Internet Explorer 6 or 7. IE8 provides new and enhanced features, such as tabbed browsing, RSS Feeds, anti-phishing, improved viewing and printing experience, and improved security.
Unified Background Process Manager
The Unified Background Process Manager (UBPM) feature set is a new infrastructure in Windows 7 that will manage both tasks and services. UBPM is an improvement over the previous Task Scheduler component that ships in Windows Embedded Standard 2009, as it brings cohesive behavior for tasks and services and adds value in serviceability by ensuring both Task Scheduler and services will automatically benefit from updates made to the UBPM engine.
BitLocker
BitLocker Drive Encryption is a data protection feature in Windows Embedded Standard 2011. Having BitLocker integrated with the operating system addresses the threats of data theft or exposure from lost, stolen, or inappropriately decommissioned computers. BitLocker can work with or without the Trusted Platform Module (TPM), which is a hardware component installed in many newer computers by the computer manufacturers.
Speech Recognition
In Windows Embedded Standard 2011, the Speech Recognition feature was added into the Speech feature set. With Speech Recognition, the system can understand spoken word and natural language and translate language in text format or perform the spoken commands.
Networking and Sharing Center
The Network and Sharing Center in Windows Embedded Standard 2011 puts you in control of your network connectivity. It's a place where you can check your connection status, view your network visually and troubleshoot connection problems. The Network and Sharing Center informs you by summarizing network info in the form of a network map and provides a graphical representation if a connection is down.
Copyright (c) 2009 Microsoft Corp. All rights reserved. Reproduced by WindowsForDevices.com with permission.
About the author: Lynda Allen has been a member of Microsoft's Windows Embedded Test team for more than five years, and originally hails from South Africa.
Previous whitepapers devoted to Windows Embedded Standard
Previous whitepapers devoted to Windows XP Embedded
news feed
