Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
ABOUT PRODUCT UPDATES
Join the discussion of the latest updates and improvements to Microsoft’s full line of Windows Embedded offerings.
Many of you must be wondering what SMI settings are and how these settings could be used to configure Windows Embedded Standard 7 image. Let me explain…
Settings Management Infrastructure (SMI) is a schema that is used to define mutable operating system settings. A mutable setting is a variable setting in which the value of the setting can be changed, either by other components or by the user or administrator. For example, user-preferred fonts and font colors are mutable settings.
Mutable settings can reside in any settings store in the operating system, such as the registry, .ini files, or some other public store, such as the IIS Metabase or the WMI repository. These settings are exposed to OEMs and Corporations to enable customization and make deployment of the OS easier.
In Windows Embedded Standard 7, these settings are included with each component in a Feature Package. In ICE, once you select a feature package to be included in your answer file, you will be presented with a list of settings that correspond to every component in the package you selected.
Comments Product Updates
This is the third and final blog in a series of articles which discusses the troubleshooting and diagnosis of driver installation issues in Windows Embedded Standard 7. Previously we presented the format of the SetupAPI.dev.log file and an example driver installation scenario. Now we will begin by enumerating some common driver installation issues you may encounter in Windows Embedded Standard 7.
In Part 1 of this series we figured out where the logs are located. In Part 2, we learned how IBW works and what messages get written to which log files. In this final section, we’ll dig deep into the logs to determine the cause of our problem and how to fix it.
Now that we have some way of viewing the logs, we can start to figure out what went wrong.
*Updated with links to Part 2 and 3 -4/13/10*
So, you’re installing a Standard 7 image through IBW, and partway through installation, you get a nice little popup that looks something like this:
* Updated 4/5/10 with clearer instructions for step 1*
In my last blog, I gave an overview of how AppLocker can help you lock down what applications can run on your Windows Embedded Standard 7 device. To demonstrate how AppLocker works, I’ll walk through an example of how to create a rule to block Internet Explorer from running. Here’s how, step by step:
1. AppLocker can be configured through wizards in the Local Group Policy Editor, which you can start by running “gpedit.msc”. AppLocker is located under “Computer Configuration -> Windows Settings -> Security Settings -> Application Control Policies” in that window. Navigate to the Executable Rules option in the navigation on the left. In the Action menu, click Create New Rule.