14 Replies Latest reply on Aug 22, 2016 11:31 AM by Kenyon

    Forcing 64 bit winpe?

    Dubois-King Apprentice

      We are on Landesk 2016 and no matter what we do when we PXE boot, it always loads the 32 bit winpe environment.  I figure if all out PCs are 64 bit now, we might do better using the 64 bit winpe.  However I can't find anywhere in Landesk to tell it to use the 64 bit winpe.  I see the options for editing the 64 bit wim, but that's all.  Anyone have any ideas?


        • 1. Re: Forcing 64 bit winpe?



          If you're utilizing the Legacy boot (non-UEFI) LANDesk will detect and utilize the 32bit WinPE. If/when using UEFI Boot, it will utilize the 64bit WinPE. The WinPE environment is not dependent upon the OS of the device.

          • 2. Re: Forcing 64 bit winpe?
            Dubois-King Apprentice

            Thanks for the reply.  Unfortunately when I try to pxe boot using uefi it won't even get the initial connection to the pxe server.

            • 3. Re: Forcing 64 bit winpe?
              Kenyon Expert

              On my PXE server I made a copy of the "boot_x64.wim" file and renamed the copy to "boot.wim" replacing the original "boot.wim" file. I made a backup of the original to have on hand just in case I need to switch back. Now all of my machines boot to 64bit.


              UEFI machines will only boot on the 64bit and need to be pre-targeted to PXE boot. This article describes this scenario; How to PXE Boot devices with UEFI

              • 4. Re: Forcing 64 bit winpe?
                1EarEngineer Specialist

                Just for clarification, when you say you don't even get the initial connection, are you ensuring you've created the bare metal, assigned and started it to a task before attempting to IPv4 boot? UEFI will not display a menu like legacy booting will.

                • 5. Re: Forcing 64 bit winpe?
                  Dubois-King Apprentice

                  I'm not sure what that means, but we managed to get the pxe boot to work in 32 bit mode, so we've given up on 64 bit for the time being.

                  • 6. Re: Forcing 64 bit winpe?
                    dwagner1 Apprentice

                    I took the boot_x64.wim and renamed it to boot.wim and this has been working fine for us.


                    We are a Lenovo shop with Surfaces scattered around and we've been able to boot just fine.  :-)



                    • 7. Re: Forcing 64 bit winpe?
                      jaysmith SupportEmployee

                      Anyone reading this thread should be aware that forcing your devices to load the 64-bit boot.wim by renaming it is not a supported process.  If you choose to do this and if you need support for your boot.wims from LANDesk in the future, you will need to revert the configuration back to the default before LANDesk Support will be able to work with you.  While this may seem like a quick and easy "workaround" please be aware that it may cause you significant issues in the future especially when it comes time to apply a Service Pack or upgrade your LDMS version and our software attempts to upgrade your boot.wim images.



                      We are aware of some situations where using the 64-bit boot.wim may seem necessary.  For example if the vendor and manufacturer of your hardware does not make available any 32-bit drivers.  In order to use the 64-bit environment your device must be using UEFI instead of BIOS.  It's automatically detected.  In order to successfully PXE boot a UEFI device, you can follow the steps listed in this document:

                      How to PXE Boot devices with UEFI


                      You can also contact support and open a case and we will walk you through the process and troubleshoot any issues you may encounter.  

                      • 8. Re: Forcing 64 bit winpe?
                        Kenyon Expert

                        Thank you for posting this disclaimer / warning. This is a very important point for this work around.


                        In our environment, our desktop techs in the field need to be able to utilize the PXE menu to image a machine. IE: They can't rely on an LDMS administrator to schedule the task at 2:am if needed.  This along with several other factors have led to utilizing a custom configuration. We also have our PXE server configured to list several choices of boot.wim files via the BCD configuration. One boot.wim for the LDMS 9.5 server, one for the 9.6 server and another for the decryption WinPE. The original boot.wim files are left intact on the core server and can be updated by any patch or update and then the boot.wim(s) can be replaced on the PXE server.


                        So to your point this would technically not be a directly supported environment and the original boot files might be needed for troubleshooting.

                        • 9. Re: Forcing 64 bit winpe?
                          1EarEngineer Specialist

                          Instead of doing all that, why not just make a bootable USB drive?

                          • 10. Re: Forcing 64 bit winpe?
                            Kenyon Expert

                            One reason would be that we could not centrally manage the boot.wim file. With something like a USB drive if a new model of machine comes out and we have to ask 15 or so techs to bring their drives to me to update them. Or any update for that matter. 


                            It really isn't that complex to configure.  Just edit the BCD on the PXE server to point to the appropriate boot files. That's it.  It takes less than a half hour.

                            • 11. Re: Forcing 64 bit winpe?
                              1EarEngineer Specialist

                              Was thinking you could just centrally host the ISO's and they just burn the new version. It's how we get around techs not having console access.

                              • 12. Re: Forcing 64 bit winpe?
                                jaysmith SupportEmployee

                                Hey Kenyon,


                                One feature of LDMS 2016 with the latest update is the ability to manually PXE boot UEFI devices and select your template much as you would a BIOS device.  From the Provisioning pane, select Preboot -> PXE Boot Options.  Select the checkbox for "Always PXE Boot UEFI Devices":


                                Then redeploy PXE reps.  Of course this requires upgrading to LDMS 2016.  Also be aware that this does not display the "Select F8" prompt as a BIOS device would.  It just goes straight into WinPE when you select Network Boot as your boot option.  If devices are setup with Network Boot as their first boot option they will always boot into WinPE when starting up. 

                                • 13. Re: Forcing 64 bit winpe?
                                  Kenyon Expert

                                  I could see how this solution could work as well. I am guessing you would have to email the techs or contact them periodically and let them know that there is an update? Then you would need to rely on them to do the update? This is not a bad idea as we may need to do something similar for the UEFI only machines that are starting to come into the environment.


                                  I do generally try to idiot proof things as much as possible and have as much in place that would not require additional steps for the techs.

                                  • 14. Re: Forcing 64 bit winpe?
                                    Kenyon Expert

                                    This will be great when we can upgrade to 2016. I am hoping that I can introduce the idea to upgrade early next year. Large environments are not easy to change over quickly.