7 Replies Latest reply on Feb 2, 2016 5:26 AM by technobabble

    PXE Deployment


      Trying to roll PXE Representative Deployment to Image machine.  But the schedule task is sitting at Active.

        • 1. Re: PXE Deployment
          JoeDrwiega SupportEmployee

          Are you trying to push the script to make a PXE Rep or are you trying to Image a machine?

          • 2. Re: PXE Deployment

            Trying to push the script.  So we can start the imaging process.

            • 3. Re: PXE Deployment
              JoeDrwiega SupportEmployee

              The script usually takes a little time because it copies files (some can be large) and then installs the PXE service:


              REMEXEC0=MsiExec.exe /q /X{F238CE99-6614-4072-9D20-1D2FA7ED951A}

              ;{These files installed by OSDRep.msi in the older version
              REMCOPY1=%DTMDIR%\landesk\files\bootmenu.1, %LDMS_CLIENT_DIR%\bootmenu.1, TOREMOTE
              REMCOPY2=%DTMDIR%\landesk\files\bstrap.0, %LDMS_CLIENT_DIR%\bstrap.0, TOREMOTE
              REMCOPY3=%DTMDIR%\landesk\files\dosundi.1, %LDMS_CLIENT_DIR%\dosundi.1, TOREMOTE
              REMCOPY4=%DTMDIR%\landesk\vboot\bootmenu.0, %LDMS_CLIENT_DIR%\bootmenu.0, TOREMOTE
              REMCOPY5=%DTMDIR%\landesk\vboot\dosundi.0, %LDMS_CLIENT_DIR%\dosundi.0, TOREMOTE

              ;{These files are needed by winpe2.0 and later
              REMCOPY6=%DTMDIR%\landesk\vboot\bcd.dat, %LDMS_CLIENT_DIR%\bcd, TOREMOTE
              REMCOPY7=%DTMDIR%\landesk\vboot\bcd_x64.dat, %LDMS_CLIENT_DIR%\bcd_x64, TOREMOTE
              REMCOPY8=%DTMDIR%\landesk\vboot\bcd_ia32.dat, %LDMS_CLIENT_DIR%\bcd_ia32, TOREMOTE
              REMCOPY9=%DTMDIR%\landesk\vboot\boot.sdi, %LDMS_CLIENT_DIR%\boot.sdi, TOREMOTE
              REMCOPY10=%DTMDIR%\landesk\vboot\boot.wim, %LDMS_CLIENT_DIR%\boot.wim, TOREMOTE
              REMCOPY11=%DTMDIR%\landesk\vboot\boot_x64.wim, %LDMS_CLIENT_DIR%\boot_x64.wim, TOREMOTE
              REMCOPY12=%DTMDIR%\landesk\vboot\bootx64.efi, %LDMS_CLIENT_DIR%\bootx64.0, TOREMOTE
              REMCOPY13=%DTMDIR%\landesk\vboot\bootia32.efi, %LDMS_CLIENT_DIR%\bootia32.0, TOREMOTE
              REMCOPY14=%DTMDIR%\landesk\vboot\bootmgr.exe, %LDMS_CLIENT_DIR%\bootmgr.exe, TOREMOTE
              REMCOPY15=%DTMDIR%\landesk\vboot\pxeboot.0, %LDMS_CLIENT_DIR%\startrom.0, TOREMOTE

              REMEXEC16=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /p="http://%CUSTJOBHOSTIP%/landesk/files/osdrep.msi" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}" /disableclientqueue


              So you can find out where it is stuck at an run it manually if needed.


              Here is a couple docs for reference:

              How To: Redeploy PXE Representatives

              Updating the WinPE image on PXE representatives

              • 4. Re: PXE Deployment

                Just curious but assuming the agent is already installed first, can you try pushing a different (smaller) package to see if that works? As Joe said, it takes a while for the software to deploy. Maybe up to 20 minutes if I recall.

                • 5. Re: PXE Deployment
                  Frank Wils ITSMMVPGroup

                  What LANDESK Version are you using? LD9.6 doesn't use the script anymore, but has a Distribution Package to deploy PXE Reps. Make sure your agent on the target is also 9.6 and that both the Scheduled Task settings and the Agent Settings used are set to Download and Execute.



                  • 6. Re: PXE Deployment

                    Yes, LD 9.6 is what currently in our environment. We moved the workstation to PXE Representative Deployment under the Schedule Task and the machine just sits in Active.

                    • 7. Re: PXE Deployment
                      technobabble Apprentice

                      LDMS 9.6 SP2 uses a LANDesk package called "PXE Representative Deployment (type is Windows Script Host) for deploying the PXE Rep. This package has a VB script named "osdrep.vbs" that is the main file that does all of the work for you. The package should include the .wim, BCD and setup_pxeproxy.exe file.


                      Basically, the "osdrep.vbs" script replaces the functionality of the old managed script.


                      There is also a know bug in LANDesk where a package that uses a script as the main installation file will leave a machine in an Active state even the  package was delivered and installed correctly. If the PXE Rep package does not complete installing, check to see if wscript.exe (running as SYSTEM account) is hung using Task Manager.