Can a Windows 2016 server provide two PXE boot sources?
|
2018-03-21, 00:54
Post: #3
|
|||
|
|||
RE: Can a Windows 2016 server provide two PXE boot sources?
(2018-03-19 17:32)NiKiZe Wrote: First of, no EFI implementation should support booting from NTFS it is FAT32 only.Hm, it seems you're at odds with Mr. Batard: https://github.com/pbatard/uefi-ntfs But like I said, I'm new to this. I'll prefer to sit back and watch you two duke it out; all I ask is that you let me know where I can find a front seat to the contest ;-) (2018-03-19 17:32)NiKiZe Wrote: But before that, build the ipxe.efi, or snp.efi which you can copy to a USB drive as bootx64.efi and then use that to test things out before modifying the dhcp server to send these out. (see http://ipxe.org/appnote/buildtargets for how this is done, and there is also some prebuilt ones at boot.ipxe.org)I'm not sure I'm following along on how to create this iPXE/UEFI/ISO. You mention creating and using a file [bootx64.efi], but that carries a different extension than *.ISO. I'm going to want to end up with an *.ISO file for building the stick. Does this new [bootx64.efi] replace the one that's currently in \boot\efi? Could you go into a little more detail? Slowly, please :-) |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Can a Windows 2016 server provide two PXE boot sources? - InteXX - 2018-03-19, 08:12
RE: Can a Windows 2016 server provide two PXE boot sources? - NiKiZe - 2018-03-19, 17:32
RE: Can a Windows 2016 server provide two PXE boot sources? - InteXX - 2018-03-21 00:54
|
User(s) browsing this thread: 1 Guest(s)