Search English (United States)  Svenska (Sverige)
den 17 maj 2012 ..:: Blog ::.. Register  Login
 Text/HTML Minimize

On March 21, the first day of MMS 2011, I announced the immediate availability of the Deployment Research blog and Deployment Research Facebook page. Sites filled with video-tutorials on how to deploy operating systems. Information about this new site, as well a bunch of other deployment related community sites was by the way also printed (thank you FedEx) and put in the attendee-bag (Thank you Microsoft) for every MMS 2011 attendee, about 4000 people.

This also means that the deployvista.com blog will not be much active anymore. It will still exist, but the content will gradually be migrated over to the new site, cleaned-up and converted into the new format…

Happy deployment, and I hope to see you online in the forums…

Regards / Johan Arwidmark
Microsoft MVP – Setup & Deployment


 Print   
 Blog_List Minimize

 Print   
 Blog_Archive Minimize

 Print   
 New_Blog Minimize
You must be logged in and have permission to create or edit a blog.

 Print   
 Setting DeployRoot value from WDS Server Minimize
Location: BlogsJohan Arwidmark    
Posted by: johan 5/5/2007

Note: This issue/configuration has been fixed in BDD 2007 Update 1  and MDT 2008.... still here for those of you still running BDD 2007 RTM. 

When using WDS Server to PXE boot the Lite Touch WinPE 2.0 image, you can use a function to to set the DeployRoot value to the WDS Server you booted from. This could be very useful for Branch Office Scenarios.

BDD 2007 Lite Touch has a variable for this called WDSServer, however it is only set if you run "wpeutil updatebootinfo" first

Method 1: Via Unattend.xml

Update unattend.xml on the Lite Touch WinPE image to start wpeutil and then set Deployroot=\\%WDSServer%\Distribution$ in bootstrap.ini.

Bootstrap.ini
[Default]
DeployRoot=\\%WDSServer%\Distribution$

Unattend.xml

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
            <Display>
                <ColorDepth>16</ColorDepth>
                <HorizontalResolution>1024</HorizontalResolution>
                <RefreshRate>60</RefreshRate>
                <VerticalResolution>768</VerticalResolution>
            </Display>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>WPEUtil</Description>
                    <Order>1</Order>
                    <Path>wpeutil updatebootinfo</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Lite Touch PE</Description>
                    <Order>2</Order>
                    <Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
            <Restart>Restart</Restart>
        </component>
    </settings>
</unattend>


    
          
   
Method 2: Via UserExit (thanks to Volker Neumann for provding the code)

Using a userexit to call wpeutil

Bootstrap.ini
[Default]
UserExit=UserExit.vbs
DeployRoot=\\#GetWDSServerName#\Distribution$

UserExit.vbs
Function UserExit(sType, sWhen, sDetail, bSkip)
                oLogging.CreateEntry "entered UserExit ", LogTypeInfo
                UserExit = Success
End Function


Function GetWDSServerName
                oLogging.CreateEntry "Entered UserExit Function 'GetWDSServerName'", LogTypeInfo
               
                on error resume next
                oShell.run "wpeutil updatebootinfo", 1, true

                sWDSServerName = oShell.RegRead("HKLM\System\CurrentControlSet\Control\PEBootServerName")
                sWDSServerName = Left(sWDSServerName, InStr(sWDSServerName ,".")-1)

                oLogging.CreateEntry "WDSServerName = " & sWDSServerName, LogTypeInfo
                oLogging.CreateEntry "Exiting UserExit Function 'GetWDSServerName'", LogTypeInfo

                GetWDSServerName = sWDSServerName
End Function

Permalink |  Trackback

Comments (1)  
Re: Setting DeployRoot value from WDS Server    By Poulin on 3/30/2009
Hi Johan.
I have a funny thing regarding the distribution share. First I had a Win 2003 server with WDS and MDT called lets say SERVER1 with distribution share \\SERVER1\Distribution$. I then installed af Server 2008 with WDS and MDT to replace SERVER1. Distribution share on the new server is \\SERVER2\Distribution$. When SERVER1 is turned off the clients cannot get the images. When WPEINIT starts it says that it cannot find \\SERVER1\Distribution$.

Do you know what to do?

Regards
Niels


  
 Search_Blog Minimize

 Print   
Copyright Deployvista.com 2006-2010 (c)   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2012 by DotNetNuke Corporation