We've just received a new model of Lenovo laptop, the x240 20AM. It won't PXE boot from WDS.
Previously, we had a similar test model, the x240 20AL, and I imported the new drivers into Out-of-box drivers. PXE boot worked, with the odd caveat of having to pressFn+F12 on the "F12 to continue" prompt from WDS.
However, that was with the test model and now we've received our first shipment of actual x240s, and they are a slightly different subtype; they are the 20AMs. Our supplier said that the drivers imported for the 20AL would all work for the 20AMs, no more would be needed.
This is what happens after a PXE boot from LAN:
which flashes up for about a tenth of a second (it was hard to get that image!), and then we immediately see...
and then we're back to the boot menu.
I don't know if it's a (1) driver issue (possibly a different NIC in the 20AM subtype) or if it's (2) something to do with DHCP or (3) something else completely.
Deployments to our existing hardware are all working fine currently.
For option (1), I added in the Intel NIC driver for the x240 20AM, and it's still giving the same problem.
For option (2) A consultant configured WDS/MDT for us initially, so I'm not fully sure how it was set up. I've read a bit today about the available options. In our WDS, WDS is authorised to be a DHCP server. On our DHCP server, options 67 & 68 are not filled in, and there is no option 60. The documentation I have about our WDS setup makes no mention of iphelper setup, but it does say
DHCP Helpers were required for the PC network to forward BOOTP (DHCP) packets to the IP address of DEPLOYSERVER. DEPLOYSERVER was authorized in Active Directory to be a DHCP server; it is not a DHCP server but WDS is similar to DHCP because it responds to the BOOTP packets of a PXE client.
I'd rather understand the problem better before making any other changes. From what I've posted, is there enough information to find the root cause?