<?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>Automatically update MDT 2010 boot images in WDS</title><link>http://blogs.technet.com/b/mniehaus/archive/2009/09/09/automatically-update-mdt-2010-boot-images-in-wds.aspx</link><description>You’ve probably gone through this cycle if you are using WDS to PXE boot computers to start bare metal Lite Touch deployments: Import new drivers or change bootstrap.ini. “Update deployment share” to generate new WIMs. Import new WIMs into WDS. Fortunately</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Automatically update MDT 2010 boot images in WDS</title><link>http://blogs.technet.com/b/mniehaus/archive/2009/09/09/automatically-update-mdt-2010-boot-images-in-wds.aspx#3508516</link><pubDate>Wed, 11 Jul 2012 15:13:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3508516</guid><dc:creator>Mehdi</dc:creator><description>&lt;p&gt;Hi guys,&lt;/p&gt;
&lt;p&gt;When i use the scirpt i have this message at the end of the update of the deploymentshare.&lt;/p&gt;
&lt;p&gt;About to run command: WDSUTIL /Replace-Image /Image:&amp;quot;Lite Touch Windows PE (x86)&amp;quot; /ImageType:Boot /Architecture:x86 /ReplacementImage /ImageFile:&amp;quot;C:\Users\tissirm\AppData\Local\Temp\32\MDTUpdate.10468\ISO\Sources\Boot.wim&amp;quot; WDSUTIL rc = -1056702168 &amp;nbsp;Exit code = 1&lt;/p&gt;
&lt;p&gt;Can you help me?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3508516" width="1" height="1"&gt;</description></item><item><title>re: Automatically update MDT 2010 boot images in WDS</title><link>http://blogs.technet.com/b/mniehaus/archive/2009/09/09/automatically-update-mdt-2010-boot-images-in-wds.aspx#3303279</link><pubDate>Thu, 31 Dec 2009 19:25:21 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3303279</guid><dc:creator>Denver_80203</dc:creator><description>&lt;p&gt;Powershell and I even got the image name! &amp;nbsp;WDSUTIL doesn't seem to mind spaces in it's command line structure (odd but this script fails when I used quotes). &amp;nbsp;Not bad for my first crack at Powershell scripting.&lt;/p&gt;
&lt;p&gt;# The script:&lt;/p&gt;
&lt;p&gt;#------------------------------&lt;/p&gt;
&lt;p&gt;$Stage = (Get-ChildItem env:STAGE).value&lt;/p&gt;
&lt;p&gt;If ($Stage -eq &amp;quot;ISO&amp;quot;) {&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;$DeployRoot = (Get-ChildItem env:DEPLOYROOT).value&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;If ($DeployRoot -like &amp;quot;\\*\*&amp;quot;) {&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;$DeploymentServer = $DeployRoot.split(&amp;quot;\&amp;quot;)[2] }&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Else {&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;$DeploymentServer = (Get-ChildItem env:ComputerName).value&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;}&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;# Note that this script is called once for each platform image created (x86, x64)&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;$Platform = (Get-ChildItem env:PLATFORM).value&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;$Content = (Get-ChildItem env:CONTENT).value&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;# Determine the Name of the existing .wim file that exists in the WDS Share&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;$WDS_Share = &amp;quot;\\$DeploymentServer\&amp;quot; + (get-wmiobject win32_share -computername $DeploymentServer | where-object {$_.name -eq &amp;quot;REMINST&amp;quot;}).name&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;$ImageFileName = &amp;quot;$WDS_Share\Boot\$Platform\Images\&amp;quot; + (dir &amp;quot;$WDS_Share\Boot\$Platform\Images&amp;quot; *.wim).name&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;# Grab the 'Friendly Name' of the WDS Image File&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;$ImageName = (((wdsutil /get-imagefile /imagefile:$ImageFileName | select-string -inputobject {$_} -pattern &amp;quot;Image name:*&amp;quot;).ToString()).split(&amp;quot;:&amp;quot;)[1]).trim()&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;# Run WDSUTIL to load the image on the server being updated.&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;WDSUTIL /replace-image /image:$ImageName /ImageType:Boot /Architecture:$Platform /ReplacementImage /ImageFile:$Content\LiteTouchPE_$Platform.wim /Server:$DeploymentServer&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;}&lt;/p&gt;
&lt;p&gt;#------------------------------&lt;/p&gt;
&lt;p&gt;then adjust LiteTouchPE.xml:&lt;/p&gt;
&lt;p&gt;&amp;lt;!-- Exits --&amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;lt;Exits&amp;gt;&lt;/p&gt;
&lt;p&gt; &amp;nbsp;&amp;lt;Exit&amp;gt;Powershell.exe &amp;quot;%deployroot%\Scripts\WDSupdate.ps1&amp;quot;&amp;lt;/Exit&amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;lt;/Exits&amp;gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3303279" width="1" height="1"&gt;</description></item><item><title>re: Automatically update MDT 2010 boot images in WDS</title><link>http://blogs.technet.com/b/mniehaus/archive/2009/09/09/automatically-update-mdt-2010-boot-images-in-wds.aspx#3302436</link><pubDate>Thu, 24 Dec 2009 15:03:36 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3302436</guid><dc:creator>Denver_80203</dc:creator><description>&lt;p&gt;This script worked great until I created my first remote deployment share. &amp;nbsp;When I updated the remote share's Boot.wim, The scripts stepped up and replaced my local boot images.&lt;/p&gt;
&lt;p&gt;This resulted in local PXE boot.wim files that set the deployroot to the remote server share. &amp;nbsp;Worked great but, very slow of course :)&lt;/p&gt;
&lt;p&gt;I think I'll end up disabling the extension in the LiteTouchPE.xml file on the remote share and manually replacing files on those machines.&lt;/p&gt;
&lt;p&gt;If I knew powershell, I think the solution would revolved around remote execution of WDSutil on the server specified in the DEPLOYROOT variable.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3302436" width="1" height="1"&gt;</description></item><item><title>re: Automatically update MDT 2010 boot images in WDS</title><link>http://blogs.technet.com/b/mniehaus/archive/2009/09/09/automatically-update-mdt-2010-boot-images-in-wds.aspx#3302059</link><pubDate>Tue, 22 Dec 2009 13:42:33 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3302059</guid><dc:creator>Aurélien BONNIN</dc:creator><description>&lt;p&gt;Hi Michael,&lt;/p&gt;
&lt;p&gt;I just wanted to add some additional information about this process. In fact, because there isn't a &amp;quot;POSTWIM&amp;quot; phase it is necessary to do these automated process during &amp;quot;POSTISO&amp;quot; phase and require that &amp;quot;Generate a Lite Touch bootable ISO image&amp;quot; option have been enabled (for LiteTouch Image) &lt;/p&gt;
&lt;p&gt;In addition it is required to have already added these boot images in WDS manually at least one time.&lt;/p&gt;
&lt;p&gt;is it true ?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3302059" width="1" height="1"&gt;</description></item></channel></rss>