[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.]
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.
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).
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