#1. Does LANDESK have an official solution for setting up a single PXE Server in a mixed BIOS/UEFI environment? Is the info in this article the correct approach? If so.....
The LDMS PXE rep is designed to be used one rep per subnet, without configuring DHCP options for the reason you have outlined above.
You may be able to configure something to workaround the issue at hand, but from an 'official' position, it's recommended to do a rep per subnet, and not configure DHCP to hand out bootfile info.
1 of 1 people found this helpful
if you use IP helpers (1 to your DHCP server and 1 to the PXE representative) on your Vlans you don't need (and really should not) configure these DHCP options. The PXE supports both UEFI and Legacy Bios. It will switch between x64 and x86 automatically depending on the kind of boot.
Thank you, Frank. That's what I wanted to hear. I'm going to put that into test this week.
It has long been said that we recommend 1 PXE rep per subnet, however this is not the case.
We recommend having at least 2 per subnet for redundancy in case the first representative goes down.
Could you elaborate on what you mean by the PXE rep can support both UEFI and legacy boot mode? We've run into our first new PC that does not have a 32bit WinPE 5.0 driver and thus we cannot use the legacy boot mode for it (although as a workaround, we used a USB Ethernet adapter and was able to use legacy boot). Or, could you or someone/anyone, point me to a doc that tells us how to reconfigure our PXE reps to support dual legacy and UEFI boot?
Thanks in advance!
Have been working with Windows 7 image (BIOS, MBR and PXE) and it have worked perfectly.
But now im starting to build a new Windows 10 image in vmware workstation (UEFI and GPT) and when i want to capture that image and want to PXE boot and dont get any resposne at all from the PXE server.
What do i have to configure in my PXE environment to get PXE to work with UEFI?
Running 9.60 SP1
Sorry for the delayed response guys, but it turned out that there was indeed a 32bit driver for the NIC we were dealing with. So for now, we are dodging the 64bit winpe until we have to move to it. Still not sure what all is required for that yet so will continue to watch this thread.