I had a working solution, but that comment I ran across on the Tech Net site about DHCP options not being recommended was bothering me.
According to this Tech Net article: Managing Network Boot Programs, the answer is no.“Redirection by the Boot Service to a TFTP service on a remote server should not be done as it is not reasonably possible for the redirecting server to know for certain that the TFTP server being redirected to is truly available.”List of NBPs " data-medium-file=" data-large-file=" class="size-medium wp-image-911" src=" alt="List of NBPs for WDS" width="300" height="130" srcset=" sizes="(max-width: 300px) 100vw, 300px" /Rather than allowing the WDS server to make a decision about which one is best for your client, you are statically setting this option via DHCP option.
This configuration is particularly useful in a lab environment where you want to immediately image new computers, but you want to ensure that existing computers are not sent through the imaging process by accidentally booting from the network.
Causes computers that do not support firmware console redirection to display "Press space or F12 for network boot," using console redirection to serial port 1 or 2.
I disabled DHCP options 43, 60, 66, and 67 and then had the network team add IP Helpers that pointed to the IP address of my WDS server. I could once again PXE boot from any device in my organization.
I was curious to see if there was any type of performance difference, so I flip-flopped back and forth a few times between DHCP Options and IP Helpers and pushed out several images to test clients. During each test PXE booting operated exactly the same, and took the same amount of time to reach a fully deployed and useable desktop on the test client.
Any devices with a modern EFI will be unable to take advantage of PXE booting if you set option 67 in this manner.