May, 2010

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

    Digital Signage and Windows Embedded Standard 7

    Last week at the Screenmedia Expo Europe 2010 in London, Intel® and Microsoft announced the commercial availability of their joint platform for Digital Signage media players, and the availability of the Digital Signage Evaluation Kit (DSEK-10). The DSEK is a reference platform that is designed to help digital signage developers quickly prototype and develop digital signage solutions. The DSEK is based on an Intel® Core i5-based reference design and Windows Embedded Standard 7 OS.

    The device itself is made up of:

    • Intel® Core™ i5 Processor (520-M) with Intel® Active Management Technology
      • - 3MB Cache, 2.40 GHz
      • - 2 processor cores, 4 software threads
      • - Integrated Graphics Engine
      • - Hardware Accelerated HD Video Decoder
      • - Mobile Intel® QM57 Express Chipset
    • 2GB SODIMM DDR3 1333MT/s memory x2 (total of 4GB)
    • SATA 2.5” Hard Disk
    • IEEE802.11a/b/g/n Intel Wireless PCI Express* Half Mini Card (6200)
    • Small form factor (185mm x 125mm x 55mm) with an aluminum chassis and an EPIC based mainboard
    • Gigabit Ethernet interface (Intel® 82577 Gigabit Ethernet PHY)


    Comments Product Updates

  • Windows Embedded Blog

    EWF – Mass deployment check list for Windows Embedded Standard 7

    For the past several months we have received several mass deployment related queries for EWF. Many customers had skipped or were unaware of the Sysprep requirement. To help customers we have compiled a checklist for use during mass deployment of images containing EWF. Hope it helps!

    1. Install and fine tune the master image. Disable HORM and EWF. Restart the machine.

    2. Sysprep (available in %WINDIR%\System32\Sysprep directory) the image by running <sysprep.exe /generalize /oobe /shutdown>. This will generalize the image and render all system components (including write filters) and settings suitable for mass deployment. Upon completion the machine will be shutdown.


    Comments Product Updates

  • Windows Embedded Blog

    Mass Deployment and BitLocker – The “Gotcha”

    As mentioned in the blog articles “Image Builder Wizard – Quick and Easy Embedded OS Creation – Part 1” written by Robert and “BitLocker in Windows Embedded Standard 2011” written by Hema – the BitLocker feature requires two partitions. The first partition is a system partition contains the BCD (Boot Configuration Data) store and remains unencrypted. The second partition is the partition that contains Windows, programs, etc and can be encrypted. IBW does a good job in ensuring that the user is required to partition with a separate system partition if the user has added the BitLocker feature. It is able to do that because it has an awareness of whether the feature is added by the user.

    What’s the “Gotcha” you may ask? Well, during Mass Deployment scenarios, such as using WDS or IBW to deploy a custom WIM, the disk partitioning dialog has no awareness of whether the BitLocker feature is in the image. That means that it is possible under these circumstances to create a system with the BitLocker feature and only have one partition. This is not a supported setup for BitLocker and the feature will not enable or allow the Windows partition to become encrypted.



    Comments Product Updates

Page 1 of 1 (3 items)