October, 2009

Creating cloud-connected
"intelligent" elevators
with Microsoft Azure services
Introducing Microsoft
Azure Intelligent
Systems Service
How big data
creates new
marketing options
for retailers
Enabling productivity
with the
Internet of Things



  • Windows Embedded Blog

    WMI Command-line Tool is not Completely Localized in Std 2009

    The Windows Management Instrumentation Command-line tool is not completely localized because the file CLIEGALI.MFL for the appropriate MUI language is not brought into the runtime when it is built in Target Designer. This is the file that defines the localized WMI namespace root\cli\MS_xxx, where xxx is the LCID for a language (e.g. 411 for Japanese). This file, for every language, does exist in the repositories but is not owned by any component.

    To solve this problem copy the file (for the specific language you need) from the embedded repositories to the runtime, and place it under %Windows%\MUI\Fallback\<LCID>.

    If wmic.exe has been run at least once it gets a little more complicated. When you run wmic for the first time, it compiles its MOF and MFL files (Cli.mof, Cliegaliases.mof, and Clialiases.mfl, etc), which get written into the WBEM repository (%WINDOWS%\system32\wbem\Repository) along with MOF/MFL files from other WMI providers. To resolve the problem in this case:

    1. Copy the file over to the XPe device and then

    2. Compile CLIEGALI.MFL after copying it to the runtime as follows:

    Open a command window and run the following command:

    mofcomp %Windows%\MUI\Fallback\<LCID>\CLIEGALI.MFL

    Comments Product Updates

  • Windows Embedded Blog

    Adding Custom Files And Creating an IBW Disk in Windows Embedded Standard 2011

    Note: The content in this blog is for users who are familiar with using Image Configuration Editor (ICE) to create a fully resolved answer file. If you would like to learn how to create a fully resolved answer file, please refer to this blog article.

    ICE provides easy ways to add custom files to your Windows Embedded Standard 2011 image and generate a bootable IBW Disk. This blog article explains how these are done in ICE.

    If you’ve chosen to install the Windows Embedded Standard toolkit with Typical option, you should find the DS in <Root Drive>\Program Files\Windows Embedded Standard Windows Embedded Standard 2011\DS. In the DS, there is a folder called “$OEM$ FOLDERS”. From Windows explorer, create a folder structure MyApps\$OEM$\$1\App1 as shown below.


    Comments Product Updates

  • Windows Embedded Blog

    Installing VS2005 or VS2008 redistributable files on Windows Embedded Standard 2009

    There have been several forum posts about including the redistributable files for Visual studio 2005 or Visual Studio 2008 in a runtime image so that applications built using these versions can run. Windows Embedded Standard 2009 database does not have componentized versions of the redistributable files for these versions of VS. The easiest way is to include the redist files as part of the application during development. If you are not the developer of the application then there are a few options.

    • You could create a new component with an FBA Generic Command that calls the redistributable package installer during FBA. You should set the FBA phase to between 8500 and 12,000 so that it runs later in the FBA sequence. If the redist package supports a quiet flag, and a silent install is desired, specify the appropriate switches in the Arguments property of the FBA Generic Command, such as

    “%11%\cmd.exe” for FilePath and

    “/c <path>\vcredist_x86.exe /q” for Arguments property.

    • Calling the redist executable directly will fail. You could just as easily do a RunOnce command in a new component, but an FBA Generic Command provides more control over the order that this command will run, especially if you have other components that are also doing custom actions during FBA.
    • You could also componentize the redist installer, which requires breaking the setup apart into the associated files and registry data and creating a component containing those resources.

    Comments Product Updates

  • Windows Embedded Blog

    BitLocker in Windows Embedded Standard 2011

    In this blog article I will be talking about a new security feature in Windows Embedded Standard 2011 (“Quebec”). This security feature has been part of Windows Operating System since Vista timeframe. I will touch upon the usefulness of this feature. The main idea of this article is to go over the procedure of adding this package to your image and using it afterwards.

    BitLocker in Windows Embedded Standard 2011 – Overview

    Windows BitLocker Drive Encryption (BitLocker) is a new security feature that provides better data protection for your device by encrypting all data stored on the Windows Embedded Standard 2011 operating system volume. BitLocker allows an admin of a machine to encrypt volumes to protect data contained on them.


    Comments Product Updates

  • Windows Embedded Blog

    Creating Fully Unattended (“Hands-Free”) Setup and Deployment of Windows Embedded Standard 2011

    PLEASE NOTE: The settings described in this article apply to Windows Embedded Standard 2011 CTP. The required settings may change slightly for the release to manufacturing (RTM) version of Windows Embedded Standard 2011, but for the most part the approach outlined in this article should apply to the RTM release.

    One very common scenario for users of Windows Embedded Standard 2011 is to develop a completely unattended, or “hands-free”, setup. In this scenario, a Windows Embedded Standard 2011 image can be created on a target device without a single human interaction once the Setup program has been properly started (and even this can be automated with the help of a well-crafted autorun volume). For this article, a fully unattended setup will result in the target device auto logging in and reaching the desktop.

    In order to help you achieve this scenario, I will touch on the different components and stages of the setup process. From a very high level, an unattended setup of Windows Embedded Standard 2011 is achieved by providing answers to every question that the setup process has. If Setup has answers to all of its different questions, then there will be no need for a UI to ask a human what to do. These answers will be provided to Setup in the form of an unattend (a.k.a. “answer”) file. This unattend file is an XML file either created by the Windows Embedded Standard 2011 Image Configuration Editor (ICE) or by hand for those who prefer.


    Comments Product Updates

Page 1 of 2 (8 items) 12