WDS and tftp conflict when working with terminals?

Question

Microsoft

There was a question concerning simultaneous operation of WDS and terminalok.
The network has WDS and tftp32 from which the terminals pull the zxpe image for download. In the DHCP area parameters, 066 specifies the server where tftp32 is located, and 067 specifies the thinstation.nbi.zpxe value so that the terminals pull the desired image.
So if I'm on WDS (located on another server, separate from DHCP and tftp) I set it to respond to all computers, then if I reboot the terminal, it will automatically try to pull the win image from the WDS server and of course it won't boot, because. the image is not hers.
How can you restrict access to it so that when it is active, the terminals do not try to boot from it, but continue to pull the image they need from tftp?
Now, in fact, we simply disable the PXE response to WDS so that it does not interfere, and when necessary we turn it on during the installation.

Answer 1

And DHCP screw?
If on lalix, then you can try to enter next-server in the description of the DHCP network.
Another option is to make a menu on the WDS server that will load both deployment services and an image for terminals. Make the image for terminals the first in the list and boot there by default.