5 Replies Latest reply on Feb 4, 2009 2:36 AM by Sicky

    OSD Deployment with more representatives separated with Vlan


      On our environment we got several VLan's. When using another Vlan it is not possible to boot from the representative in any way. The CoreServer is in a Vlan everyone (with permissions) can access from any location. We got one Vlan to reinstall machines using PXE and OSD scripts.


      New situation:

      We want to expand to use more Vlans to reinstall machines using OSD, so that means more represenatives, but we don't want to make more OSD scripts to deploy images. The problem lies here:


      We got 1 pxe representative server on this moment, its a 2003 Server with a share that also contains the images to be deployed. It is providing WinPe with the OSD menu that is provided by the coreserver to deploy the images. We want 2 more pxe representative servers in separate Vlan's that are also sharing the images, so they will be installed from the representative server locally. On this moment in the OSD scripts, the path and name of the images (XP) are hardcoded in the scripts, like <servername>\<sharename>\<imagename>.


      What we want is:

      Replace the hardcoded name of the <servername> be replaced somehow for a variable or vbscript, so it is getting the name of that representative dynamically. The variable or script should be the servername of the representative.



      What we don't want is making al OSD scripts double or tripple for each pxe representative, one script



      Does anyone have a clue what to do.


      Thanks in advance.

        • 1. Re: OSD Deployment with more representatives separated with Vlan
          ahe Expert



          we've done this. We've a lot of sites which are connected to different core's. All the sites use the same PE image.


          In your PE image you've to change the entry in your all.reg file (or create your own). In this file the core servername is stored.


          What we do:

          add a line "call GetOurCoreServerName.cmd" in startnet.cmd

            factory -winpe 
             call GetOurCoreServerName.cmd 
            reg import all.reg 
            \ldclient\wait4ip /t 180


          In the batch GetOurCoreServerName.cmd you must check in which VLAN (on which site) your client resides.(ping -n 1 YourPXEServer.yoursite.com) (hopefully you've a explicit attribute in your VLAN)

          Extract the name of this PXE server, and check the name against a (manually created) list of dependencies...


          List of dependencies:

          pxe server name1; core server name1

          pxe server name2; core server name1

          pxe server name3; core server name1

          pxe server name4; core server name2

          pxe server name5; core server name3

          pxe server name6; core server name3

          . . .


          The prerequisite is a common share on every site (I don't know how it is possible in VLAN's).


          We've many VLAN's on every site, but we use one PXE server per site! It is a setting on the DHCP server (don't ask me which.. :-) )




          • 2. Re: OSD Deployment with more representatives separated with Vlan

            This doesn't answer your question as well, but we use one PXE Rep for multiple vlan's by taking advantage of the DHCP options in Microsoft Windows Server 2003/2008:



            • 3. Re: OSD Deployment with more representatives separated with Vlan
              ahe Expert

              Thank you for the link Dan.


              In our environment it was done by our DNS/DHCP/Network guys centrally...




              • 4. Re: OSD Deployment with more representatives separated with Vlan
                Frank Wils ITSMMVPGroup

                Hi Sicky,


                You can use this as replacement for your hardcoded server:

                REMEXEC22=drvmap.exe user 1084E90896AB83A0CA51C202F67 I: \\%Computer - LANDesk Management - PXE Holding Queue - Proxy Host Name%\image


                When PXE booting the LANDesk Inventory contains a field representing the PXE Rep it is booting from. You can use that to point to the shares on that same PXE Rep.


                Be aware though, that you can use this script only for PXE boot. If you want to push an OSD script to a PC that is on, it won't PXE boot but store the bootfiles on c: so it won't have a record indicating PXE Representative. If you want to deploy OSD also in this way, you need 2 scripts: 1 for PXE boot and 1 for Vboot.


                Good luck!


                • 5. Re: OSD Deployment with more representatives separated with Vlan

                  Hi Frank,


                  Thanks for your answer, this seems a suitable solution. In the meantime we found another solution. I wrote an vbscript that that determines the location of the PXE representative server based on the 3th octet of the ip address. There is just one PXE representative \ Software Distribution server per VLAN so it will map the drive to that (local) server. The rest of the OSD script will continue based on the drive letters.


                  We will test this your solution later on and communicate the results.


                  Thanks all guys for the input, this is much appreciated