DISMUI has received many new features and has been optimized – therefore it made it to Version 2.
The tool also received a dedicated site on the Elbacom website.

New Features

Automated Offline Servicing

POSReady 7 does not support online servicing of the operating system. Therefore DISMUI offers the "Service image offline" option which will automate the offline servicing for you. The configuration can be done online but all the servicing operations will be done in an on-the-fly created Windows PE environment!

This method can be used for Windows Embedded Standard 7 too.

DISMUI needs two files from the Setup media to create the Windows PE system. Please ensure that you have a setup media connected when choosing this option.

Footprint Calculation

DISMUI will calculate the estimated OS footprint when selecting or deselecting feature packages. This will inform you how your current selection will impact on the operating systems size.

Operating System Detection

When launching DISMUI it will detect on which operating system it runs on. The best option (Online, Online with offline servicing, Offline) will be chosen based on the current system. It will also disable the online mode when running on a full Windows 7 system. On Windows PE it will automatically find the image location.

Update Check

DISMUI now offers the ability to check for new updates from within the tool.

Icons

The tool has now received icons that were missing in the previous version to make it look more complete.

Required Components

DISMUI will now include all required components to run out-of-the box (or out-of-the-zip).

Other changes

• Improved automatic detection of distribution share
• Improved detection of MUI DVD
• Improved responsiveness while executing tasks
• Bugfixes & Other small improvements

Branding

We now offer to create a customized branded version of DISMUI.

If you are interested please contact us for more information.

DISMUI has been updated to fix some issues when installing Feature Packages in Offline Mode.

For bigger packages there was a need to create a scratch directory. DISMUI 1.4.2.1 is now creating a temporary scratch directory to solve the issue. This directory will be removed afterwards.

Other improvements:

• DISMUI detects if it is running under Windows PE (e.g. POSReady 7 Setup) and switches to Offline Mode and searches for the Windows installation automatically
• Logfiles are now saved in the correct location
• Scratchdir handling

A new version of DISMUI is now available. The new version features enhanced support for POSReady 7.

The following features have been added:

• Language Pack OPK DVD is now supported as Distribution Share Directory
  By selecting the DVD drive that contains the language pack DVD from the OPK you can easily add and remove language packs from your POSReady installation
• Language Pack directory of POSReady 7 OPK DVD added automatically
  DISMUI now adds the LangPacks directory of the POSReady 7 DVD automatically.
• Minor bug fixes

The videos can be found in his blog on MSDN:

Windows 7 features for Embedded

Custom Media Center Experience with Windows Embedded Standard 7

DLNA support in Windows Embedded Standard 7

The article is about the following scenario:

• You develop a Windows Embedded Standard 7 or Windows Embedded Standard 7 Service Pack 1 image for your device.
• You added "Performance Monitoring" package in your answer file using Image Configuration Editor.
• You added "Enhanced Write Filter with HORM" package in your answer file to protect the system (C:) volume.
• You deployed your image without executing "winsat prepop".
• You enabled EWF for the runtime image.

The complete article including the workaround can be found here.

The Windows 7 Boot Updater enables you to do the following customizations:

• Change the bootanimation
• Use a static image as bootlogo either as a fullscreen image or instead of the animation
• Change the texts and their positions
• Change the colors

The tool updates the bootscreen and also the resume animation when the device is resuming from hibernation.

Several checks assure that the update process of the customization was successful.

The tool works with the Standard Boot Environment and also with the Enhanced Write Filter Boot Environment of Windows Embedded Standard 7.

For more information and pricing please go to the Coder for Life website:

www.coderforlife.com/projects/win7boot/elbacom

Please note that the tool is modifying system files. So after a Windows Update there is a possibility that the bootlogo reverts to the original version.
The customization of the files is allowed in the ALTs of you Windows Embedded Standard product. However Microsoft will not support this change.
Elbacom and Coder for Life are not responsible for any damages – there is no warranty and no liability for any damages!

The script is designed to be run directly on the Windows Deployment server. To be able to run the script there are the following requirements.

Requirements

• Windows Deployment Server Role installed on a Windows Server
• Windows Deployment Server with a fixed IP Address
• Windows Automated Installation Kit 3.0 installed on the Windows Deployment Server
• Windows Embedded Standard 7 – Image Build Wizard DVD located in the DVD drive of the WDS Server

Usage

To execute the batch file copy and paste it to notepad on your Windows Deployment Server. Save it as createIBWBootImage.bat.

Launch the “Command Line for Deploymenttools” from the installed WAIK Tools with Administrator Permissions.

Start the createIBWBootImage.bat with the following arguments:

createIBWBootImage.bat <IBW Disk Drive/Path> <x86|x64> <IP Address of WDS Server> <Username> <Password>

The specified user must have permissions to access network shares on the server!

The batch file will then create a local copy of the IBW Disk and it will create a network share on the WDS.
After that it will create a new Windows PE image and modify the startcmd.net to map a network drive to the IBW Disk Share on the WDS.and launch the Setup.exe from the mapped network share. The modified image will then be added to the WDS Boot Image automatically.

After the image creation has succeeded you can boot from PXE and select the “Windows Embedded Standard 7 – Image Builder Wizard – x86” Image to start the installation.

Script

@echo off

REM ###########################################
REM # Create IBW PXE Boot Image for WDS
REM # (c) Elbacom created by Wolfgang Unger
REM ###########################################

IF "%1" == "" goto Usage
IF "%2" == "" goto Usage
IF "%3" == "" goto Usage
IF "%4" == "" goto Usage
IF "%5" == "" goto Usage

IF EXIST C:\WES7_IBW\%2 GOTO DIREXISTS

echo Creating Local IBW Image…
md C:\WES7_IBW\%2
xcopy %1\*.* C:\WES7_IBW\%2 /H /E /Y /C /V

:DIREXISTS
echo Creating Share
net share WES7IBW%2 /DELETE
net share WES7IBW%2=C:\WES7_IBW\%2

SET WORKDIR=C:\winpetemp

echo Creating Windows PE…
start /w cmd /c copype %2 %workdir%

echo Mounting Windows PE WIM…
dism /mount-wim /wimfile:%workdir%\winpe.wim /index:1 /mountdir:%workdir%\mount

echo Applying Startup Commands…
echo @echo off > %workdir%\mount\Windows\system32\startnet.cmd
echo echo Initializing… >> %workdir%\mount\Windows\system32\startnet.cmd
echo wpeinit.exe >> %workdir%\mount\Windows\system32\startnet.cmd
echo echo Connecting to server… >> %workdir%\mount\Windows\system32\startnet.cmd
echo net use N: \\%3\WES7IBW%2 /user:%4 %5 >> %workdir%\mount\Windows\system32\startnet.cmd
echo echo Launching Setup… >> %workdir%\mount\Windows\system32\startnet.cmd
echo N:\setup.exe >> %workdir%\mount\Windows\system32\startnet.cmd

echo Unmounting Windows PE WIM…
dism /unmount-wim /mountdir:%workdir%\mount /commit

echo Adding Image to Windows Deployment Services Server…
WDSUTIL /Verbose /Progress /Add-Image /ImageFile:%workdir%\winpe.wim /ImageType:Boot /Name:"Windows Embedded Standard 7 – Image Build Wizard – %2" /Description:"Windows Embedded Standard 7 – Image Build Wizard via PXE – %2" /Filename:WES7IBW%2.wim

echo Cleaning Up…
del %workdir% /s /q
rd %workdir% /s /q

echo Done!

GOTO Done
:USAGE
echo Usage: createIBWBootImage.bat IBW_Disk_Drive/Path Architecture WDS_IP_Address Username Password
echo Example: createIBWBootImage.bat D: x86 192.168.0.200 Domain\Administrator Pa$$w0rd
echo –
echo Architecture can be either x86 or x64
echo Username needs to have permission to access shares on the WDS Server!

:DONE

DISMUI was updated to work with the CTP2 of Windows Embedded POSReady 7. The tool allows you easily add and remove Feature Packages in POSReady 7 CTP2 via a graphical user interface.

The new version fixes minor issues when using a POSReady 7 CTP Distribution Share.

Changes:

• Fixes when using a POSReady 7 CTP Distribution Share
• Suppresses Conflict Dialog when no packages are available to select
• Permanent Packages check in Conflict Dialog

Another great feature is that Windows Embedded Device Manager 2011 is able to control the write filters which might be enabled on your devices. Normally when a system has a write filter enabled and updates are applied the updates are gone again after a reboot – this is because the filter drivers redirect all changes made to the disk into a RAM overlay which gets reset on reboot.
When deploying updates via the Device Manager the system will handle this case properly by deactivating and reactivating the filter drivers automatically.

The tool works with all Windows Embedded Standard and Ready operating systems such as:

• Windows XP Embedded
• Windows Embedded Standard 2009
• Windows Embedded Standard 7
• Windows Embedded for Point of Service
• Windows Embedded POSReady 2009

and because it is based on System Center Configuration Manager 2007 it can handle all Windows Embedded Enterprise systems as well.

More information about the tool can be found here:
http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-device-manager.aspx

Toolkit Update via ECE:
https://ece.partners.extranet.microsoft.com/ece/Embedded/Products/ProductSupplements/Embedded/EmbeddedStandard7/DisOEM-WES7MnthlyUpdsandFeatures.htm

Apart from the Service Pack 1 for the operating system the package also adds new features such as WMI layer for filter drivers, SKU Compliance packages, etc. For a full list and more details have a look at the previous Service Pack 1 feature post.