Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
iPXE Windows Environment
2014-06-29, 20:02
Post: #2
RE: iPXE Windows Environment
First off: If you want to boot a machine in UEFI environment, you need to use iPXE UEFI binaries, not the ones for lecay BIOS systems. undionly.kpxe, ipxe.pxe, 80861503.rom are all examples of files that work in the legacy BIOS environment. If you want to build files that work in a UEFI environment you need to build ipxe.efi, snponly.efi, 80861503.efidrv, 80861503.efirom etc.

The second thing is that UEFI support in iPXE is still not considered stable for production use, so don't blame us if it goes down in flames. There are some simple tutorials you can follow from on the getting started page (for windows), there is also If you already have pxelinux.0 working, then ipxe.pxe (or undionly.kpxe) should be place alongside pxelinux.0 in whichever folder is your TFTP root folder. If you install the TFTP client on your windows workstation it should be easy to check if you can fetch the file from the TFTP server before you actually try to boot it.

PXELinux and iPXE both have a similar feature set, just like you can use syslinux, grub or lilo to boot from local media. It's really your choice. PXELinux uses a more declarative approach, while iPXE has a procedural approach with scripts, which gives you a benefit that you can react better to errors and make more runtime choices. For PXELinux this kind of logic must usually be handled by some sort of server-side service. It's really up to you what you feel is more appropriate.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
iPXE Windows Environment - zophar - 2014-06-23, 07:52
RE: iPXE Windows Environment - robinsmidsrod - 2014-06-29 20:02

User(s) browsing this thread: 1 Guest(s)