Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
The toolkit for Windows 7-based Windows Embedded Standard 2011 (formerly code-named “Quebec”) comes with two components: Image Builder Wizard (IBW) and Image Configuration Editor (ICE). IBW provides a simplified interface to allow for quick and easy creation and prototyping of images. ICE contains more advanced options for editing configurations in greater detail.
IBW is based on Windows Setup, which is used to install both client and server Windows. IBW supports both “attended” and “unattended” installations. “Attended” refers to using the actual wizard to design and build an embedded runtime, while an “unattended” install is one which uses either an answer file created in ICE or a previously created WIM.
[The following article is authored by one of the Windows Embedded MVPs (Most Valuable Professionals). Our MVPs have a heavy background in Embedded systems and are a great repository of information on Windows Embedded products. We’re providing this space on our team blog as a service to our readers by allowing MVPs to share some of their knowledge with the rest of the community.]
A Windows Embedded Standard image, freshly built from Target Designer, cannot be booted into directly. Instead it has to go through an additional process called First Boot Agent (FBA). The FBA process contains all the installation logic normally found in the setup application of XP Professional. It is implemented as several components to be found in the Software\System\System Services\Base node of the component catalog.
Comments Product Updates
Windows Embedded Standard systems are built differently, and do not have the same setup experience as normal desktop Windows computers, but both have one thing in common: Windows Security Identifiers (SIDs).
Why is there a need for a special embedded power management in Windows Embedded Standard 2009? Does it behave differently than the desktop OS? These are valid questions about a small, but powerful component that can be found in the Systems\Management\Applications node of the Component Catalog.
In its disguise as “Remote Desktop” most computer users probably already have been in contact with Terminal Services. The name “Remote Desktop” describes the technology quite well, namely a desktop experience to a remote device.
When thinking of embedded usage scenarios for Terminal Services, device management and maintenance come to mind, of course, especially l if the device is headless and therefore hard to handle without a user interface. In addition, Terminal Services can save the development effort to provide , for example, a web-based configuration user interface. The user rights on the device can easily be managed locally or in an Active Directory domain in the same granular fashion one is used from a normal desktop system.