Hit an interesting issue, I’ve worked round it - but want a better understanding of it.
CM box running 1610 Had an issue with drivers in the boot image, so updated idk and imported NIC drivers back into it. Assigned the new boot image to a few Task Sequences - got wind of an pxe issue when techs wanted a F12 build. So, pxe traffic was reaching the server, everything was in place, but (no advert found) message was in the logs. Checked and re-checked everything, nothing stupid was found; boot image was on three DP’s. At this point I switched the TS back to the older Boot image and everything worked. Below is a screen shot of the Boot Images available and their versions. I’ve no idea if you can have more than two? Or even how I ended up with 3 - but there we go. What I have noticed is that resorting the WDS service only sees two images referenced, CMP00003 / CMP00004, no mention of the new x86 file (the one that didn’t work); on that note I assigned the x64 image to the Task Sequence and got the same issue. I’m migrating to a new 1706 server next week (can’t test pxe on it yet) - so its not a biggy, but I’d like to try and understand what is happening. Thanks Stuart [cid:8778B4C5-6798-43FB-9F04-4DB5D825F6A6@fritz.box]