Configuring Components - Microsoft Windows Embedded Standard 2009 Developer Resource Kit Componentizing Windows...

Configuring Components
A description of every feature component can be found in the " Windows Embedded Standard 2009 Components.xls" spreadsheet. Use the spreadsheet to help you search for, pick and choose the components needed for your device.
This section contains additional component-specific tips and tricks. For debugging component problems, refer to the Troubleshooting document.
Automatic Logon
Use the Automatic Logon component to automatically log on the user every time the system boots. This component has configurable settings allowing you to enter the default domain name, user name, and password. Keep in mind that if the user changes these values later in the runtime, the Autologon feature will fail.
Bluetooth
Bluetooth Support in Microsoft Windows XP Embedded with Service Pack 2
.NET Framework 1.1
The .NET Framework 1.1 component is included in Windows XP Embedded SP2 onwards.
.NET Framework 2.0
The .NET Framework 2.0 component is available as a component or you can install it using its Installer after your XPe image has completed FBA. The recommended approach is to use the Installer for the purpose of forward compatibility.
For more information, please open this link: Microsoft Windows XP Embedded SP2 Resource Kit. Then open the following document found at that link:
Installing_DotNet_Framework.doc
.NET Framework 3.0 SP1 Setup
The .NET Framework 3.0 Setup feature is a component. However, as with several other features originally introduced with Update Rollup 1.0, the feature itself actually is installed via an installer application (dotnetfx3.exe) near the end of FBA. The .NET Framework 3.0 component contains a list of prerequisite dependencies i.e. a list of components that must also be installed for the feature to install and function, along with the dotnetfx3.exe installer. The Settings page contains a checkbox that you must check if you want to "Install .NET Framework 3.0 XP-Pro Install Package during FBA". When you do so, an FBA Generic Command is preconfigured to run the installer at FBA phase 11000. Otherwise you need to make provisions for running dotnetfx3.exe as a post-FBA step.
.NET Framework 3.5 Setup
This component also sets up its installer application near the end of FBA.
File System
For an overview of FAT, HPFS, and NTFS File Systems, see the following article in the Microsoft Knowledge Base:
Overview of FAT, HPFS, and NTFS File Systems
IIS
See MSDTC
Internet Protocol Version 6 (IPV6)
For the IPV6 network stack, service and utilities, include these components:
TCP/IP Version 6
TCP/IP Version 6 Service
TCP/IP Version 6 Utilities
Refer to the corresponding XPe component help in Target Designer for more information.
One way to install the IPV6 protocol stack, is to run 'ipv6 install' after FBA has completed. However there is a preferred way to install the stack, via Netsh. To include netsh.exe in your design, add the Network Command Shell component. For more information regarding its use with IPv6:
Using the Netsh command-line tool to configure the IPv6 protocol instead of using the IPv6.exe utility
Migrating IPv6.exe Commands to Netsh Command
Utilities unique to IPV6 are ipsec6.exe, ipv6.exe, and ping6.exe.
Since XPe is a componentized representation of XP Pro, you can use MSDN content describing IPV6:
IPv6
How to install and uninstall IPv6
IPv6 Guide for Windows Sockets Applications
IPv6 Transition Technologies White Paper (principally applies to Windows Server 2008 and Vista but it is a good description of the technology in general).
In order to have a better understanding of the mapping of IPv6 features to versions of Windows XP or Server, refer to this link:
Microsoft's Objectives for IP Version 6
MSDTC and Cloning
MSDTC and/or IIS may fail after an image has completed the cloning process.
The cloning process (whose internal process name is sysprep, a mechanism that was inherited from XP Professional's Sysprep tool) uses the MINIOC.INF file to notify various services that are sensitive to system identity changes, when cloning is about to begin (SysprepBeforeExecute) so they can prepare themselves for the system identity change (SID). After sysprep completes, it then notifies the services listed in the (SysprepInitExecute) section of MINIOC.INF so they can reinitialize themselves.
Here is a typical MINIOC.INF:
[SysprepInitExecute]
msdtcprx.dll,SysPrepDtcReinstall
catsrvut.dll,SysprepComplus
scecli.dll,SceSysPrep
setup\iis.dll,SysPrepRestore
setup\tsoc.dll,SysPrepRestore
[SysprepBeforeExecute]
setup\msmqocm.dll,SysprepDeleteQmId
setup\iis.dll,SysPrepBackup
setup\tsoc.dll,SysPrepBackup
These services may fail to start back up again after Sysprep completes.
There are potentially several things that could cause these services to fail:
1. By far, the most common problem occurs when FBRESEAL is run more than once
against the image. The OEM should carefully review the entire process to ensure
that this does not happen. When you include the System Cloning Tool component in
your configuration, by default it will run FBRESEAL automatically when FBA
finishes. Then when the OEM runs FBRESEAL to prepare for deployment, this is the
same as running it twice. To prevent this, in the System Cloning Tool Settings, set Reseal Phase to Manual, or go into the Advanced Settings of the
System Cloning Tool settings and change cmiResealPhase from 12000, to 0.
2. If you have any custom applications that use or rely on MSDTC (or IIS), it is
possible they are preventing MSDTC (or IIS) from re-initializing itself, and the solution is
to ensure they are not running when cloning occurs.
If you have a custom designed or third party service that has a static dependency on ole32.dll, iphlpapi.dll and/or secur32.dll, it can interfere with stopping or starting of MSDTC. Try ensuring that your service is stopped before cloning starts up.
Interestingly, the service only has to reference the above as static link-time DLLs, and not actually call into them.
Workaround 1:
Stop any of your custom services that have static dependencies on
ole32.dll, iphlpapi.dll and secur32.dll (use the depends.exe tool to identify these
dependencies). Restart the services after cloning completes.
Workaround 2:
Issue the following commands after cloning completes, in order to
restart MSDTC and IIS. Use RunOnceEx and/or configure it to run after the shell has fully launched.
msdtc -install -a
msdtc -resetlog
iisreset /restart
Network Command Shell
For information about working with the network command shell (Netsh.exe), visit the following Microsoft Web site:
Working with Netsh in Windows XP Embedded
For information about using command-line options with Netsh.exe, see the following article in the Microsoft Knowledge Base:
How to Use the Netsh.exe Tool and Command-Line Switches
NTFS encrypted file system support
You can encrypt the contents of a folder or individual files in your runtime by adding the NTFS component and the NTFS Format/Tools component to your configuration.
Security Template components
The following link describes how to create a custom security component for the Microsoft Management Console (MMC) Snap-in interface.
How to Create a Custom Security Template
For additional information, see the following article in the Microsoft Knowledge Base:
How to add custom registry settings to Security Configuration Editor
Sysprep (Windows System Preparation)
Use this component only in combination with SCCM.
System Center Configuration Manager (SCCM)
For resealing your image, use the System Cloning Tool.
Windows Firewall/Internet Connection Sharing (ICS)
This component is perhaps the single most important network security related feature. Click on the following links for more information:
How to Configure Windows Firewall in Windows XP Embedded with Service Pack 2
843090 Description of the Windows Firewall feature in Windows XP Service Pack 2
875357 Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
|