2 Replies Latest reply on Feb 9, 2018 1:34 AM by lballmer

    PXE boot best practices

    rlattin Rookie

      I'm wondering if there is any good documentation or other advice that can help us optimize our PXE booting.  In the past we've always used DHCP scope options 60, 66, 67, and 43 to point our clients to the PXE server.  If the PXE representative is also the DHCP server then only option 60 is needed, but if we want PXE to point to a PXE rep that is not the DHCP server we have used options 66, 67, and 43 to point it to the correct server and boot file.  This solution works great if we just stick to 32 bit PXE booting, but doesn't allow any flexibility if we want to use both 64 and 32 bit booting.


      I am aware that we can accomplish our goal by using the self-elected subnet service on clients in the same subnet, but this has proven unreliable for us.  We much prefer to use servers as our PXE representatives, which reside on a different subnet than the clients.  Are there any best practices out there to make PXE booting across subnets happen without the use of DHCP scope options?  We've tried putting the IP address of the PXE rep in the IP helper table, but it doesn't help.  We are running version 2017.3.

        • 1. Re: PXE boot best practices

          Are you trying to boot UEFI only (no BIOS emulation) or are you trying to do something like BIOS for 32 bit systems and UEFI for 64 bit systems?


          I'm interested to hear how you make use of UEFI and why you need 2 different boot files.


          In my environment, we had WDS for a long time but moved over to Landesk provisioning less than a year ago and love it. We keep WDS as a backup and also use it as the PXE boot server host (DHCP option 66)- we don't use Landesk for PXE. All clients support BIOS emulation so we just kept DHCP 67 as default boot\x86\wdsnbp.com and we added the Landesk 64bit WinPE image to the WDS boot file menu.


          FWIW I think I've rebooted the WDS server once in 8 years- it's very reliable re serving up PXE boot images.


          With this setup we do zero-touch bare-metal builds (HP workstations & Lenovo laptops / Win10 x64) now with hardly any errors and are very happy with it. But there's always more to learn, so interested in what you are doing if you care to share.

          • 2. Re: PXE boot best practices
            lballmer Rookie

            Hi rlattin

            we face the same issue, where we have problems with the PXE boot, as our DHCP Service runs on a separate appliance. So far I found these documents, but I didn't make it to solve the issue. Maybe these documents will help:


            How to configure DHCP to work with LANDESK PXE boot

            About DHCP options 66 and 67 and LANDESK PXE Booting

            About LANDESK Management Suite PXE


            I keep you posted, if we have fixed the issue.