Hi, we have a small WDS setup using Microsoft Deployment Toolkit (no SCCM/MEM involved), and I'm able to successfully re-image machines usually. I've come across one machine that seems to be unable to proceed beyond downloading the NBP file. The machines are all using UEFI to boot including this one.
The machine boots and I press F12 to network boot, and I see the below
>Checking Media Presence.......
>Media Present........
>Downloading NBP file...
>NBP file downloaded successfully.
This screen remains for approx 5 seconds, then it proceeds to instead try and do PXE over IPv6 instead. This fails (this is expected) and the machine instead boots up to the installed OS.
Looking at the Deployment-Services-Diagnostics logs in Event Viewer I can see the machine appears to be successfully PXE booting and downloading at least one files form TFTP with no signs of errors or failures.
The following client booted from PXE:
Hardware Address: <MAC address of the machine>
IP: 172.16.32.90
Device ID: {1F261432-E23E-6911-841C-1C697A664DC4}
ClientArchitecture: 4
Prestaged: false
A Non-Shared buffer was created for reading file E:\RemoteInstall\boot\x64\wdsmgfw.efi.
The Following Client completed TFTP Download:
Client IP: 172.16.32.90
Filename: boot\x64\wdsmgfw.efi
File Size: 1322528
Client Port: 1393
Server Port: 57112
Variable Window: false
Other machines proceed after this to also download files such as bootmgrfw.efi, boot.sdi, WIM and BCD files, but this one doesn't seem to proceed beyond the initial wdsmgfw.efi download.
I've checked the BIOS settings and UEFI booting is enabled on this machine. I've compared the settings with a working machine and everything appears to be the same. I've also tried imaging this PC using the same cable that worked on another machine in case of a cable fault, with no success.
All the threads I'm finding online about this are referencing situations where all machines are having this problem, rather than just individual machines. I've also checked with my colleagues who are more familiar with it and they're unsure as to what the issue could be either.
Any suggestions on where to look next would be appreciated.