<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx</link><description>In MDT 2008, the Windows PE startup process was something close to this: Windows PE started CMD.EXE to run STARTNET.CMD. STARTNET.CMD started WPEINIT.EXE. WPEINIT.EXE initialized networking and optional components, then ran “WSCRIPT.EXE X:\Deploy\Scripts\LiteTouch.wsf”.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3260270</link><pubDate>Wed, 01 Jul 2009 10:52:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3260270</guid><dc:creator>thomasgud</dc:creator><description>&lt;p&gt;Great work Mike. What build is this? I have not seen this graphic with my 7100 build. &lt;/p&gt;
&lt;p&gt;Regards, Thomas&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3260412</link><pubDate>Wed, 01 Jul 2009 18:05:08 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3260412</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;This is with MDT 2010 Beta 2 (build 5.0.1210.0), which works with Windows 7 RC (build 7100).&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3261701</link><pubDate>Tue, 07 Jul 2009 00:05:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3261701</guid><dc:creator>M4g3</dc:creator><description>&lt;p&gt;I was wondering where did the shell go. Is there a way to completely block access to that shell?. For debugging it is great but for final deployment it poses a security risk (i.e. info such as passwds, keys and other sensitive information stored in unattend.xml could be obtained through it).&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3261705</link><pubDate>Tue, 07 Jul 2009 00:32:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3261705</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;You can turn off the F8 prompt by editing the winpeshl.ini file in the &amp;quot;Templates&amp;quot; directory. &amp;nbsp;Right now it says &amp;quot;/bootstrap&amp;quot;; change it to instead say &amp;quot;/bootstrapNoSF8&amp;quot;.&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3261812</link><pubDate>Tue, 07 Jul 2009 11:20:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3261812</guid><dc:creator>M4g3</dc:creator><description>&lt;p&gt;Thanks Michael. Is there a way to alter the default failure behaviour of WinPE? Atm it displays a Wizard error message, dumps the Logs to a share and exits to a shell. What i would like to have is no Wizard error message, no shell just dump the Logs and reboot. Is this possible?&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3261946</link><pubDate>Tue, 07 Jul 2009 17:40:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3261946</guid><dc:creator>M4g3</dc:creator><description>&lt;p&gt;Hmm actually what i would like to have is Wiard error message, logs dumped onto the share and then reboot (no shell). Is this possible? Also what is the best place to submit feture requests and bug reports for MDT 2010 Beta 2&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3261969</link><pubDate>Tue, 07 Jul 2009 18:38:11 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3261969</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;Not without modifying the LiteTouch.wsf script. &amp;nbsp;Right now, we will always display the wizard if an error occurs, and the machine won't reboot (it will just open a command prompt) if the process doesn't complete with a return code of 0.&lt;/p&gt;
&lt;p&gt;So the changes would have to reset the return code to 0 before it gets to the summary wizard display (so that SkipFinalSummary=YES works).&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3262000</link><pubDate>Tue, 07 Jul 2009 20:44:22 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262000</guid><dc:creator>M4g3</dc:creator><description>&lt;p&gt;Thx again :). I have noticed more actions are availble throught the database section including FinishAction option. I have set it to REBOOT but it seems that the process does not restart at the end of the sequence. Also i have been fighting with MININT folders and Sysprep folders being left behind containing unattend.txt and sysprep.inf (in XP case). The Logs say that the tas sequence completed successfully. I have tries invoking LTICleanup explicitly but that caused more problms. I use only LiteTouch (no sms, configmgr, etc). My workaround was to add a custom task at the end of the sequence that waits fot the TS process to finish, then removes MININT and sysprep folders and restarts the machine. However it would be grand to achieve that within the task sequence (i.e. full cleanup and reboot with FinishAction). How can i acheve that? Am i missing something?&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3262227</link><pubDate>Wed, 08 Jul 2009 18:42:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262227</guid><dc:creator>M4g3</dc:creator><description>&lt;p&gt;Oki doki the FinishAction is working now although i had to add it to CustomSettings.ini (besides the entry in the database). However the completion of the TS sequence does not clean up MININT and sysprep folders. Do i have to explility invoke LTICleanup.wsf or is there another way?&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3262230</link><pubDate>Wed, 08 Jul 2009 18:58:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262230</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;What was left in the MININT folder?&lt;/p&gt;
&lt;p&gt;We wouldn't normally clean up the sysprep folder - that's something the OS should take care of doing.&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3262279</link><pubDate>Wed, 08 Jul 2009 20:51:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262279</guid><dc:creator>M4g3</dc:creator><description>&lt;p&gt;MININT contains unattend.xml, unattend.xml.bak (unattend.txt in canse of XP) with plain text passwords and other sensitive info + some TS related dlls in a TOOLS/X64 subfolder.&lt;/p&gt;
&lt;p&gt;As for sysprep folder if no capture is specified should this file/folder exist?&lt;/p&gt;
&lt;p&gt;Cheers&lt;/p&gt;
&lt;p&gt;Lukas&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3262967</link><pubDate>Sat, 11 Jul 2009 17:11:47 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262967</guid><dc:creator>NathanR</dc:creator><description>&lt;p&gt;So is there a way of showing the cmd prompt now? &amp;nbsp;I'm trying to debug a capture image issue (image capture fails at about the 1.4Gb mark, wim gets deleted and rc = 2 is returned). &amp;nbsp;I was hoping to use /debug:true in the unattend.xml file in PE to trace what's happening but 2010 B2 doesnt' show it &amp;nbsp;(which is otherwise a great change).&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3262985</link><pubDate>Sat, 11 Jul 2009 20:44:39 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3262985</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;Yes, press the F8 key.&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3263045</link><pubDate>Sun, 12 Jul 2009 06:28:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3263045</guid><dc:creator>NathanR</dc:creator><description>&lt;p&gt;Sorry, I meant to show the cmd that executes the wpeinit.exe app. &amp;nbsp;Apols for the badly explained question.&lt;/p&gt;
&lt;p&gt;Didn't need to use the /debug:true switch after all. &amp;nbsp;Found the ztibackup_imagex.log and found that I was running out of space on the source HDD. &amp;nbsp;Ended up finding the issue in the MS KB.&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3277017</link><pubDate>Wed, 26 Aug 2009 13:06:35 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3277017</guid><dc:creator>wvanhiele</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I just noticed the &amp;quot;Run the Recovery Wizard&amp;quot; option in your winPE. How can i do that? Is it a custom created option?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3277114</link><pubDate>Wed, 26 Aug 2009 18:12:52 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3277114</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;It's not a custom option - it's built into the Windows 7 boot.wim. &amp;nbsp;So to get that to show up, we start with the Windows 7 boot.wim instead of the winpe.wim from Windows AIK. &amp;nbsp;(The Windows RE component isn't available in Windows AIK for compliance reasons.)&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3295907</link><pubDate>Mon, 23 Nov 2009 21:49:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3295907</guid><dc:creator>jsekel</dc:creator><description>&lt;p&gt;Michael,&lt;/p&gt;
&lt;p&gt;We have successfully moved from BDD to MDT 2010 except for one little niggle, the welcome screen (same as shown in this post)! &amp;nbsp;We can't seem to get it to stop showing up. &amp;nbsp;We have added skipbddwelcome to bootstrap.xml and custom.xml and even tried skipwizard too. &amp;nbsp;Once we click run it never prompts us again and installs perfectly but this little screen won't go away. &amp;nbsp;Can you point me in the right direction?&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Josh&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3295910</link><pubDate>Mon, 23 Nov 2009 22:17:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3295910</guid><dc:creator>mniehaus</dc:creator><description>&lt;p&gt;You need to generate new boot images once you change the bootstrap.ini to add the SkipBDDWelcome parameter. &amp;nbsp;(You can import the new WIM into WDS, or burn a new ISO to CD.)&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;
</description></item><item><title>re: MDT 2010 New Feature #8: No more visible command windows when booting Lite Touch Windows PE</title><link>http://blogs.technet.com/mniehaus/archive/2009/06/30/mdt-2010-new-feature-8-no-more-visible-command-windows-when-booting-lite-touch-windows-pe.aspx#3296038</link><pubDate>Tue, 24 Nov 2009 14:08:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3296038</guid><dc:creator>jsekel</dc:creator><description>&lt;p&gt;Duh!, we forgot to move the rebuilt image over to WDS.&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;
</description></item></channel></rss>