Intel Customer Support will need to follow-up on this, but my understanding is that the BN NUC's have PXE support for only Legacy boot. Why UEFI boot was supported in previous generations but dropped in this latest (BN) generation is a mystery to me.
Ah, I misunderstood the last thread. So sometime between UEFI Network Driver: 9.0.1045 (the latest network driver on the 6th gen NUCs) and 9.0.1056 (the oldest network driver I could roll back to on the 7th gen NUCs) for the I219-V network adapter, PXE boot stopped working. However this isn't a supported feature, so chances aren't good it will be addressed?... that would be a bummer
Ah correction, the above are the UEFI Video ROM drivers....
Last network ROM drivers on 6th gen were : LAN Option ROM: 0.1.04
The 7th gen lists 2 separate items : "Option ROM: v0.1.10 PXE-2.1 (build 092) and UEFI Driver: 0.0.15"
This message was posted on behalf of Intel Corporation
Thank you to N. Scott Pearson for the comments posted above.
Tyson.Korhonen: Thank you very much for joining the Intel® NUC communities. We will try our best in order to provide the answer you are looking for.
In order to confirm the information posted previously, I will do further research on this matter. As soon as I gather all the details I will post the resolution on this thread.
Any further questions, please let me know.
We have validated the PXE boot functionality successfully connected to the PXE server to load the Operating System
The only thing that is really different between Legacy and UEFI, is that Legacy will prompt you to press F12 to accept the network boot, but UEFI will not. You just have to “mash it” to accept the request. Similar to how you would get into the boot menu with F10.
See below some images we captured during testing:
I hope this helps,
Thank you for running that test! Can you confirm the BIOS version you are on? Is that configuration with DHCP on the same PXE server? If DHCP isn't on the PXE server, are you using a Helper IP for PXE or DHCP Option settings?
I've see the invisible 'press F12 to accept network boot' after the 'Succeed to download NBP File' on some of our older NUCs as well. Stumbled onto that solution fairly randomly actually hehe. On the 7i5BNK's though I can't get even get to the download NBP file screen.
This does make me want to fire up wireshark and investigate the network traffic. We run DHCP and PXE/WDS on separate servers using Microsoft's supported helper IP configuration on the subnets (2 helpers 1 for DHCP 1 for PXE). I have another PXE/WDS server that also does DHCP for a little sandbox subnet. I'll give one of the 7th gens a run on that one and see if the problem maybe falls onto the NUC not correctly interpreting the router's helper IP responses in our production environment.
We are experiencing the same issue. We can do legacy pxe boot with NUC 7i3BNH, but uefi pxe boot is not working. We installed the latest bios update, but that doesn't help. Other devices can do uefi pxe boot. There is definitely something wrong with the uefi pxe boot function of this type of NUC's...
Did anyone solve this?
We have the exact same problem. Latest BIOS, latest version of WDS running on W 2012 R2 and also 2016...Same problem.
Booting Legacy we can see the "Press Enter", Booting UEFI we cannot.
This still doesn’t work on my NUC7i5BNK, BIOS version BNKBL357.86A.0057.2017.1122.1550
I’ve just wasted an hour or so ’mashing’ the F12 key etc
Is there a proper solution for this yet?
We have open a case with Microsoft, analyzed the network traces and the problem seems to be a bad interpretation of the NUC's BIOS.
Could it be fixed by Intel with a firmware upgrade?
Oh it‘s definitely something Intel need to fix, I have other UEFI PXE devices that boot fine. Interestingly if I boot into the UEFI shell on the NUC I can ping (with responses) the distribution point and the DHCP server.
We contacted Intel Support months ago, but the support is hopeless. They keep saying they can't replicate the issue, but it seems they just lack the knowledge required for this. They keep asking for information, and when we send them the required information, they ask for other irrelevant information, such as 'are you using VOIP?' 'Do you still get the same issue after updating the LAN driver?'. We gave up on this and now use legacy pxe boot.