<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Elbacom Techblog &#187; WEPOS/POSready</title>
	<atom:link href="http://www.elbacom.com/blog/category/weposready/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elbacom.com/blog</link>
	<description>Elbacom Techblog</description>
	<lastBuildDate>Wed, 01 Sep 2010 06:46:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>System Protection using Windows SteadyState on Windows XP Professional for Embedded Systems</title>
		<link>http://www.elbacom.com/blog/2010/02/system-protection-using-windows-steadystate-on-windows-xp-professional-for-embedded-systems/</link>
		<comments>http://www.elbacom.com/blog/2010/02/system-protection-using-windows-steadystate-on-windows-xp-professional-for-embedded-systems/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 10:46:12 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[Win7 FES]]></category>
		<category><![CDATA[Windows Embedded Enterprise]]></category>
		<category><![CDATA[XP FES]]></category>
		<category><![CDATA[XPe/WES]]></category>
		<category><![CDATA[XPeBuilder / WES Builder]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2010/02/system-protection-using-windows-steadystate-on-windows-xp-professional-for-embedded-systems/</guid>
		<description><![CDATA[The free Microsoft utility Windows SteadyState can be used on Windows XP Professional for Embedded Systems to prevent the OS from any changes. 
It offers a write filter which will redirect all writes to a cache file which can be reset on a reboot. This will generate a fresh system on every boot.
Windows Updates can [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.elbacom.com/blog/wp-content/uploads/2010/02/image.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; margin-left: 0px; border-left-width: 0px; margin-right: 0px" title="image" border="0" alt="image" align="right" src="http://www.elbacom.com/blog/wp-content/uploads/2010/02/image-thumb.png" width="244" height="179" /></a>The free Microsoft utility <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=D077A52D-93E9-4B02-BD95-9D770CCDB431&amp;displaylang=en" target="_blank">Windows SteadyState</a> can be used on Windows XP Professional for Embedded Systems to prevent the OS from any changes. </p>
<p>It offers a write filter which will redirect all writes to a cache file which can be reset on a reboot. This will generate a fresh system on every boot.</p>
<p>Windows Updates can be installed even when the write protection is on. Additional security policies can be applied on the system using SteadyState.</p>
<p><a href="http://www.elbacom.com/assets/files/attachments/SteadyState Installation.pdf" target="_blank">Download a manual for the installation and configuration from our website</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2010/02/system-protection-using-windows-steadystate-on-windows-xp-professional-for-embedded-systems/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Preventing account expiration in XPe/WES</title>
		<link>http://www.elbacom.com/blog/2010/01/preventing-account-expiration-in-xpewes/</link>
		<comments>http://www.elbacom.com/blog/2010/01/preventing-account-expiration-in-xpewes/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 09:23:04 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[XPe/WES]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2010/01/preventing-account-expiration-in-xpewes/</guid>
		<description><![CDATA[Per default user accounts will expire in Windows XP Embedded and Windows Embedded Standard.   To avoid this you can run the following commands for each user created:
net accounts /maxpwage:unlimited     net users Username /expires:never      net users Username /active:yes

]]></description>
			<content:encoded><![CDATA[<p>Per default user accounts will expire in Windows XP Embedded and Windows Embedded Standard.   <br />To avoid this you can run the following commands for each user created:</p>
<blockquote><p>net accounts /maxpwage:unlimited     <br />net users <strong>Username</strong> /expires:never      <br />net users <strong>Username</strong> /active:yes</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2010/01/preventing-account-expiration-in-xpewes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>POSReady 2009 and BGInfo &#8211; missing Network information</title>
		<link>http://www.elbacom.com/blog/2009/11/posready-2009-and-bginfo-missing-network-information/</link>
		<comments>http://www.elbacom.com/blog/2009/11/posready-2009-and-bginfo-missing-network-information/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 13:19:20 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[BGInfo]]></category>
		<category><![CDATA[POSReady]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2009/11/posready-2009-and-bginfo-missing-network-information/</guid>
		<description><![CDATA[If you like to use BGInfo on POSReady you will notice that the Gateway information and other network information is missing from the output.    The lack of this information is caused by a missing DLL file which is not included in POSReady 2009.    To enable this output copy over [...]]]></description>
			<content:encoded><![CDATA[<p>If you like to use <strong>BGInfo</strong> on POSReady you will notice that the Gateway information and other network information is missing from <a href="http://www.elbacom.com/blog/wp-content/uploads/2009/11/image.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; margin-left: 0px; border-top: 0px; margin-right: 0px; border-right: 0px" title="image" border="0" alt="image" align="right" src="http://www.elbacom.com/blog/wp-content/uploads/2009/11/image-thumb.png" width="244" height="206" /></a>the output.    <br />The lack of this information is caused by a missing DLL file which is not included in POSReady 2009.    <br />To enable this output copy over the &quot;<strong>inetmib1.dll</strong>&quot; file from an English XP Pro SP3 installation to the POSReady system.    <br />The file is located in the <strong>Windows\system32</strong> directory. If you refresh the information now using BGInfo all information is displayed.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/11/posready-2009-and-bginfo-missing-network-information/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Cloning images using WAIK and imagex</title>
		<link>http://www.elbacom.com/blog/2009/11/cloning-images-using-waik-and-imagex/</link>
		<comments>http://www.elbacom.com/blog/2009/11/cloning-images-using-waik-and-imagex/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 12:00:13 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[Embedded Server]]></category>
		<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[WES 7]]></category>
		<category><![CDATA[Win7 FES]]></category>
		<category><![CDATA[Windows Embedded Enterprise]]></category>
		<category><![CDATA[XP FES]]></category>
		<category><![CDATA[XPe/WES]]></category>
		<category><![CDATA[XPeBuilder / WES Builder]]></category>
		<category><![CDATA[cloning]]></category>
		<category><![CDATA[deployment]]></category>
		<category><![CDATA[imagex]]></category>
		<category><![CDATA[waik]]></category>
		<category><![CDATA[windows 7]]></category>
		<category><![CDATA[windows vista]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2009/11/cloning-images-using-waik-and-imagex/</guid>
		<description><![CDATA[This video demonstrates you the usage of imagex together with either Windows Vista AIK or Windows 7 AIK.   A detailed command description can be found here.
The video shows the capturing of an installed “ready-to-clone” image where it will be saved to an external harddrive.   The second part will show the deployment [...]]]></description>
			<content:encoded><![CDATA[<p>This video demonstrates you the usage of imagex together with either Windows Vista AIK or Windows 7 AIK.   <br />A detailed command description can be <a href="http://www.elbacom.com/blog/2009/05/creating-and-deploying-images-using-waik-and-imagex/" target="_blank">found here</a>.</p>
<p>The video shows the capturing of an installed “ready-to-clone” image where it will be saved to an external harddrive.   <br />The second part will show the deployment to a fresh system where the target disk still needs to be prepared.</p>
<p><iframe height="600" marginheight="0" src="http://www.elbacom.com/blog/player/player.php?filename=ImageX%20Deployment.wmv&amp;title=ImageX Deployment" frameborder="0" width="800" marginwidth="0" scrolling="no"> </iframe></p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/11/cloning-images-using-waik-and-imagex/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Driver Extractor for XP Embedded and Windows Embedded Standard</title>
		<link>http://www.elbacom.com/blog/2009/10/driver-extractor-for-xp-embedded-and-windows-embedded-standard/</link>
		<comments>http://www.elbacom.com/blog/2009/10/driver-extractor-for-xp-embedded-and-windows-embedded-standard/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 09:52:16 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[Win7 FES]]></category>
		<category><![CDATA[Windows Embedded Enterprise]]></category>
		<category><![CDATA[XP FES]]></category>
		<category><![CDATA[XPe/WES]]></category>
		<category><![CDATA[XPeBuilder / WES Builder]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2009/10/driver-extractor-for-xp-embedded-and-windows-embedded-standard/</guid>
		<description><![CDATA[ (v0.9)
Driver Extractor is a tool which makes creating SLD components for drivers very easy.     All you need to do is to run the tool on the target machine with XP, Vista or Windows 7 and all device drivers installed.     Then you just need to select the [...]]]></description>
			<content:encoded><![CDATA[<p><iframe height="20" marginheight="0" src="/blog/downloadlink.php?filename=DriverExtractor.zip" frameborder="0" width="200" marginwidth="0" scrolling="no"> </iframe>(v0.9)</p>
<p>Driver Extractor is a tool which makes creating SLD components for drivers very eas<a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; margin-left: 0px; border-left-width: 0px; margin-right: 0px" title="image" border="0" alt="image" align="right" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb.png" width="407" height="266" /></a>y.     <br />All you need to do is to run the tool on the target machine with XP, Vista or Windows 7 and all device drivers installed.     <br />Then you just need to select the devices for which the drivers should be exported into an SLD file and click export.     <br />Driver Extractor will then copy all the needed files and creates a component for XPe/WES with Repository for you.     <br />After importing the component to the database you can easily create your image.</p>
<h3>Requirements</h3>
<ul>
<li>.NET Framework 3.5 SP1 </li>
<li>Windows Operating system with all needed device drivers installed </li>
<li>WMI Support (if running on an embedded OS) </li>
<li>Windows must be installed on C:\Windows in the current version </li>
</ul>
<h3>How To Use</h3>
<ol>
<li>Run DriverExtractor.exe on the target device. The Windows version should be XP as the exported drivers are taken from the current installation. If you use Vista it will take Vista driver which might not work under XP! </li>
<li>Check the devices for which you want to export the drivers.      <br /><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image1.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb1.png" width="244" height="160" /></a> </li>
<li>Click Actions / Export Selected.      <br /><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image2.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb2.png" width="244" height="160" /></a> </li>
<li>Choose an output directory. The tool will create a separate folder for each component named by the devices name.      <br /><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image3.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb3.png" width="244" height="230" /></a> </li>
<li>Import the component (located in the output directory\Devicename\sld directory) into the Database by using the Component Database Manager      <br /><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image4.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb4.png" width="244" height="78" /></a> <a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image5.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb5.png" width="122" height="133" /></a><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image6.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb6.png" width="133" height="131" /></a>&#160; </li>
<li>Add the component to your configuration </li>
</ol>
<p>&#160;</p>
<h3>Description</h3>
<h5>Menus</h5>
<table border="0" cellspacing="0" cellpadding="2" width="715">
<tbody>
<tr>
<td valign="top" width="239">File / End</td>
<td valign="top" width="474">Ends the program</td>
</tr>
<tr>
<td valign="top" width="239">Actions / Export Selected</td>
<td valign="top" width="474">Exports the drivers for the selected devices</td>
</tr>
<tr>
<td valign="top" width="239">Actions / Select All</td>
<td valign="top" width="474">Selects all devices</td>
</tr>
<tr>
<td valign="top" width="239">Actions / Deselect All</td>
<td valign="top" width="474">Deselects all devices</td>
</tr>
<tr>
<td valign="top" width="239">Actions / Refresh</td>
<td valign="top" width="474">Refreshes the device list</td>
</tr>
<tr>
<td valign="top" width="239">View / Files of selected device          <br />Contextmenu / Show Driver Files</td>
<td valign="top" width="474">Shows the needed driver files for the current selected device</td>
</tr>
<tr>
<td valign="top" width="239">View / Properties          <br />Contextmenu / Properties</td>
<td valign="top" width="474">Opens the Windows properties for the current selected device</td>
</tr>
<tr>
<td valign="top" width="239">? / About</td>
<td valign="top" width="474">Displays information about the tool</td>
</tr>
<tr>
<td valign="top" width="239">&#160;</td>
<td valign="top" width="474">&#160;</td>
</tr>
</tbody>
</table>
<h5>Toolbar</h5>
<p><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image7.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb7.png" width="118" height="29" /></a>&#160;</p>
<p><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image8.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb8.png" width="28" height="29" /></a> Refreshes the device list</p>
<p><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image9.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb9.png" width="25" height="29" /></a>&#160; Shows the needed driver files for the current selected device</p>
<p><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image10.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb10.png" width="27" height="28" /></a> Exports the drivers for the selected devices</p>
<p><a href="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image11.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://www.elbacom.com/blog/wp-content/uploads/2009/10/image-thumb11.png" width="27" height="29" /></a> Opens the Windows properties for the current selected device</p>
<h5></h5>
</p>
<p><iframe height="20" marginheight="0" src="/blog/downloadlink.php?filename=DriverExtractor.zip" frameborder="0" width="200" marginwidth="0" scrolling="no"> </iframe>(v0.9)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/10/driver-extractor-for-xp-embedded-and-windows-embedded-standard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hide &#8220;Windows is starting up&#8221;, &#8220;Windows is shutting down&#8221;, &#8230; windows</title>
		<link>http://www.elbacom.com/blog/2009/09/hide-windows-is-starting-up-windows-is-shutting-down-etc-windows/</link>
		<comments>http://www.elbacom.com/blog/2009/09/hide-windows-is-starting-up-windows-is-shutting-down-etc-windows/#comments</comments>
		<pubDate>Mon, 21 Sep 2009 08:22:35 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[Windows Embedded Enterprise]]></category>
		<category><![CDATA[XP FES]]></category>
		<category><![CDATA[XPe/WES]]></category>
		<category><![CDATA[XPeBuilder / WES Builder]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2009/09/hide-windows-is-starting-up-windows-is-shutting-down-etc-windows/</guid>
		<description><![CDATA[There are two ways how you can remove these messages in Windows.
1. Use Minlogon    &#160; Minlogon will remove all the status messages and the logon window and logs the system on using the SYSTEM account.     &#160; Normally this works fine but if you need to access domains this [...]]]></description>
			<content:encoded><![CDATA[<p>There are two ways how you can remove these messages in Windows.</p>
<p>1. Use Minlogon    <br />&#160; Minlogon will remove all the status messages and the logon window and logs the system on using the SYSTEM account.     <br />&#160; Normally this works fine but if you need to access domains this solution will not work for you.     <br />&#160; Also there are some other things (Cardspace,..) which will not work with Minlogon as it’s a minimum implementation of Windows Logon.</p>
<p>If you cannot use Minlogon you can go with the default Windows Logon and set the following Registry Key:</p>
<p>2. Windows Logon with hidden status windows    </p>
<p>&#160; Create the following registry entry in the runtime image or add the following key to your Target Designer Image Configuration:</p>
<blockquote><p>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]      <br />&quot;DisableStatusMessages&quot;= dword:00000001</p>
</blockquote>
<p>&#160; After this key has been set all the status windows will disappear.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/09/hide-windows-is-starting-up-windows-is-shutting-down-etc-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to add/remove languages to a finished POSReady image?</title>
		<link>http://www.elbacom.com/blog/2009/05/how-to-addremove-languages-to-a-finished-posready-image/</link>
		<comments>http://www.elbacom.com/blog/2009/05/how-to-addremove-languages-to-a-finished-posready-image/#comments</comments>
		<pubDate>Thu, 28 May 2009 15:10:27 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2009/05/how-to-addremove-languages-to-a-finished-posready-image/</guid>
		<description><![CDATA[Installing and removing languages in POSReady is really easy.
All you need is the installation DVD.

Insert it into the target machines DVD drive and an autorun splash screen will appear.
Click “Install additional languages for the POSReady user interface”
Select the languages you wish to install
Select the language you wish to use as default languages for all new [...]]]></description>
			<content:encoded><![CDATA[<p>Installing and removing languages in POSReady is really easy.</p>
<p>All you need is the installation DVD.</p>
<ol>
<li>Insert it into the target machines DVD drive and an autorun splash screen will appear.</li>
<li>Click “Install additional languages for the POSReady user interface”</li>
<li>Select the languages you wish to install</li>
<li>Select the language you wish to use as default languages for all new users accounts from the dropdown below the language list</li>
<li>Click Install</li>
<li>Reboot</li>
</ol>
<p>To change the language for an existing user</p>
<ul>
<li>Open Control Panel</li>
<li>Open Regional Settings</li>
<li>Switch to the Languages tab</li>
<li>Select the language you wish to use from the “Language used in menus and dialogs” dropdown</li>
<li>Click OK</li>
<li>Logoff</li>
<li>Relogon</li>
</ul>
<p>This video will guide you through all the steps mentioned above.</p>
<p> <iframe height="600" src="http://www.elbacom.com/blog/player/player.php?filename=PosRdyInstallMUI.wmv&amp;title=Installing MUIs in POSReady 2009" width="800" scrolling="no" marginheight="0" marginwidth="0" frameborder="0"> </iframe></p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/05/how-to-addremove-languages-to-a-finished-posready-image/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating and deploying images using WAIK and imagex</title>
		<link>http://www.elbacom.com/blog/2009/05/creating-and-deploying-images-using-waik-and-imagex/</link>
		<comments>http://www.elbacom.com/blog/2009/05/creating-and-deploying-images-using-waik-and-imagex/#comments</comments>
		<pubDate>Wed, 27 May 2009 13:37:00 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[WES 7]]></category>
		<category><![CDATA[Win7 FES]]></category>
		<category><![CDATA[Windows Embedded Enterprise]]></category>
		<category><![CDATA[XP FES]]></category>
		<category><![CDATA[XPe/WES]]></category>
		<category><![CDATA[XPeBuilder / WES Builder]]></category>
		<category><![CDATA[Cloning WAIK imagex Windows PE network deployment]]></category>

		<guid isPermaLink="false">http://www.elbacom.com/blog/2009/05/creating-and-deploying-images-using-waik-and-imagex/</guid>
		<description><![CDATA[Before beginning with the image creation or deployment – please download the WAIK tools from Microsoft (http://www.microsoft.com/downloads/details.aspx?FamilyID=C7D4BC6D-15F3-4284-9123-679830D629F2&#038;displaylang=en) and create either a bootable DVD or bootable USB stick which contains imagex. For this please follow the documentation that comes with the WAIK tools. 

Preparation

Please follow the preparation steps for both – image creation and image deployment as you’ll need to have a working network connection. 

Setting up a DHCP server

You can skip this step if you have a DHCP server running in your network. 

Create a new dialup connection – the settings like number, etc. are not important. 
Open the settings of the created dialup connection and enable internet sharing for the local network adapter which will be connected with your target device. 
Check the IP-address of the local network adapter – it should be 192.168.0.1

Create a network share

On your development machine set up a network share where the image will be located. Please make sure you can access the network share from another pc and that you have write access to this share. 

Mapping a network drive in Windows PE

Boot the target machine from the previous created media. 
In the command prompt type ipconfig to check if the pc has a valid ip address. You can use ping (e.g. ping 192.168.0.1) to test if the connection to the development pc works. 
Map a network drive to your development pc.
net use N: \\<IP-Address>\<Sharename> [/User:<pcname>\<username> <Password>]

Sample
net use N: \\192.168.0.1\images /User:devmachine\administrator admin 









Create an image

To create an image we will use the imagex tool which comes with the WAIK tools. For more information on imagex please have a look on Microsoft Technet http://technet.microsoft.com/en-us/library/cc722145.aspx 

Type the following command
imagex /capture C: N:\image.wmi “Master image”

You can also use additional paramters such as /compress to compress the image. For additional arguments please type imagex /?

Deploy an image

Before we will deploy the image we will prepare the target disk to make sure that the image can boot after the deployment. 

Preparing the target disk

Run diskpart and type the following commands
LIST DISK


DISKPART> list disk 

Disk ### Status Size Free Dyn Gpt
-------- ---------- ------- ------- --- ---
Disk 0 Online 149 GB 0 B
Disk 1 Online 149 GB 0 B





Use this command to find out the disk id of the disk that should be used as target.  

SELECT DISK 0 (instead of 0 use the appropriate disk id of your target disk)
CLEAN (this will remove all partitions on the target disk)
CREATE PARTITION PRIMARY (this creates a primary partition on the target disk)
ACTIVE (set the previous created partition active)
ASSIGN LETTER = C (assign the drive letter C)
FORMAT FS=NTFS QUICK (do a quick ntfs format)
EXIT (quick diskpart)



Deploy the image

Run the following command to deploy the image from the network share
imagex /apply n:\image.wim 1 c: 
Reboot your machine – it should now boot from the image properly.]]></description>
			<content:encoded><![CDATA[<p>Before beginning with the image creation or deployment – please download the WAIK tools from Microsoft (<a title="http://www.microsoft.com/downloads/details.aspx?FamilyID=C7D4BC6D-15F3-4284-9123-679830D629F2&amp;displaylang=en" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=C7D4BC6D-15F3-4284-9123-679830D629F2&amp;displaylang=en">http://www.microsoft.com/downloads/details.aspx?FamilyID=C7D4BC6D-15F3-4284-9123-679830D629F2&amp;displaylang=en</a>) and create either a bootable DVD or bootable USB stick which contains imagex. For this please follow the documentation that comes with the WAIK tools.</p>
<h3>Preparation</h3>
<p>Please follow the preparation steps for both – image creation and image deployment as you’ll need to have a working network connection.</p>
<h3>Setting up a DHCP server</h3>
<p>You can skip this step if you have a DHCP server running in your network.</p>
<p>Create a new dialup connection – the settings like number, etc. are not important. </p>
<p>Open the settings of the created dialup connection and enable internet sharing for the local network adapter which will be connected with your target device. </p>
<p>Check the IP-address of the local network adapter – it should be 192.168.0.1 </p>
<h3>Create a network share</h3>
<p>On your development machine set up a network share where the image will be located. Please make sure you can access the network share from another pc and that you have write access to this share.</p>
<h3>Mapping a network drive in Windows PE</h3>
<p>Boot the target machine from the previous created media. </p>
<p>In the command prompt type <em>ipconfig</em> to check if the pc has a valid ip address. You can use <em>ping</em> (e.g. <em>ping 192.168.0.1</em>) to test if the connection to the development pc works. </p>
<p>Map a network drive to your development pc. </p>
<blockquote><p><em>net use N: \\&lt;IP-Address&gt;\&lt;Sharename&gt; [/User:&lt;pcname&gt;\&lt;username&gt; &lt;Password&gt;]<span style="text-decoration: underline">Sample          <br /></span>net use N: <a>\\192.168.0.1\images</a> /User:devmachine\administrator admin </em></p>
</p>
</blockquote>
<h3>Create an image</h3>
<p>To create an image we will use the imagex tool which comes with the WAIK tools. For more information on imagex please have a look on Microsoft Technet <a title="http://technet.microsoft.com/en-us/library/cc722145.aspx" href="http://technet.microsoft.com/en-us/library/cc722145.aspx">http://technet.microsoft.com/en-us/library/cc722145.aspx</a></p>
<p>Type the following command    <br /><em>imagex /capture C: N:\image.wmi “Master image”You can also use additional paramters such as /compress to compress the image. For additional arguments please type imagex /? </em>
</p>
<h3>Deploy an image</h3>
<p>Before we will deploy the image we will prepare the target disk to make sure that the image can boot after the deployment.</p>
<h3>Preparing the target disk</h3>
<p>Run <em>diskpart </em>and type the following commands     <br /><em>LIST DISK</em> </p>
<blockquote><p>DISKPART&gt; list disk</p>
<p>Disk ###&#160; Status&#160;&#160;&#160;&#160;&#160; Size&#160;&#160;&#160;&#160; Free&#160;&#160;&#160;&#160; Dyn&#160; Gpt      <br />&#160; &#8212;&#8212;&#8211;&#160; &#8212;&#8212;&#8212;-&#160; &#8212;&#8212;-&#160; &#8212;&#8212;-&#160; &#8212;&#160; &#8212;       <br />&#160; Disk 0&#160;&#160;&#160; Online&#160;&#160;&#160;&#160;&#160;&#160; 149 GB&#160;&#160;&#160;&#160;&#160; 0 B       <br />&#160; Disk 1&#160;&#160;&#160; Online&#160;&#160;&#160;&#160;&#160;&#160; 149 GB&#160;&#160;&#160;&#160;&#160; 0 B</p>
</blockquote>
<p>Use this command to find out the disk id of the disk that should be used as target.</p>
<blockquote><p><em>SELECT DISK 0</em>&#160; (instead of 0 use the appropriate disk id of your target disk)       <br /><em>CLEAN</em>&#160;&#160; (this will remove all partitions on the target disk)       <br /><em>CREATE PARTITION PRIMARY</em>&#160; (this creates a primary partition on the target disk)       <br /><em>ACTIVE</em> (set the previous created partition active)       <br /><em>ASSIGN LETTER = C</em> (assign the drive letter C)       <br /><em>FORMAT FS=NTFS QUICK</em> (do a quick ntfs format)       <br /><em>EXIT</em> (quick diskpart)</p>
</blockquote>
<h3>Deploy the image</h3>
<p>Run the following command to deploy the image from the network share </p>
<blockquote><p><em>imagex /apply n:\image.wim 1 c:</em> </p>
</blockquote>
<p>Reboot your machine – it should now boot from the image properly. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/05/creating-and-deploying-images-using-waik-and-imagex/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Do I need to enter a different license for each image?</title>
		<link>http://www.elbacom.com/blog/2009/05/do-i-need-to-enter-a-different-license-for-each-image-with-xp-embedded-windows-embedded-standard/</link>
		<comments>http://www.elbacom.com/blog/2009/05/do-i-need-to-enter-a-different-license-for-each-image-with-xp-embedded-windows-embedded-standard/#comments</comments>
		<pubDate>Wed, 27 May 2009 09:38:11 +0000</pubDate>
		<dc:creator>Wolfgang Unger</dc:creator>
				<category><![CDATA[Licensing]]></category>
		<category><![CDATA[WEPOS/POSready]]></category>
		<category><![CDATA[WES 7]]></category>
		<category><![CDATA[XPe/WES]]></category>
		<category><![CDATA[XPeBuilder / WES Builder]]></category>

		<guid isPermaLink="false">http://localhost/wordpress/2009/05/do-i-need-to-enter-a-different-license-for-each-image-with-xp-embedded-windows-embedded-standard/</guid>
		<description><![CDATA[No, you do not need to enter a separate license for each cloned image.
Why?
The licensing of Windows Embedded works different than for normal Windows versions.
A image is fully licensed if you put a license sticker onto the device.
If you need more details you can contact us any time!
For more details on how to create a [...]]]></description>
			<content:encoded><![CDATA[<p>No, you do not need to enter a separate license for each cloned image.</p>
<h3>Why?</h3>
<p>The licensing of Windows Embedded works different than for normal Windows versions.</p>
<p>A image is fully licensed if you put a license sticker onto the device.</p>
<p>If you need more details you can contact us any time!</p>
<p>For more details on how to create a full version image for XPe/WES have a look at the “How to enter the product key in XP Embedded / Windows Embedded Standard?” post.</p>
<p><em>This is only valid for the following products:</em></p>
<ul>
<li><em>XP Embedded / Windows Embedded Standard</em></li>
<li><em>WEPOS / POSReady</em></li>
<li><em>Windows CE</em></li>
</ul>
<p><em>All other products are licensed differently.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.elbacom.com/blog/2009/05/do-i-need-to-enter-a-different-license-for-each-image-with-xp-embedded-windows-embedded-standard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
