WDS Setup not working

Question

Hi,

I'm trying to get the WDS setup to work with BIOS and UEFI x64 computers.
When a x64 BIOS machine contacts the WDS server, it results in a blue screen with errorcode 0x00000F or something like that (BCD error).
If I boot a x64 UEFI machine it contacts the WDS server and results in a 0x102 error.
OR:
Whe I set the Admin approval on the WDS it just waits for approval but is doesn't show up in de 'pending devices' section of the WDS.

My Setup:

Domaincontroller and DHCP (with WDS) are 2 different servers. They both reside in a different subnet/vlan than the client.
If I put the client and WDS in the same network, all works fine... speedy and correct.
So the different vlans are giving me trouble

1. IP Helper (DHCP Relay) on the switch where my AD, WDS ... servers are connected to.
2. a DHCP policy to set the PXEClient option (60) for the UEFI clients and the correct bootfile (boot\x64\wdsmgfw.efi)
3. a DHCP policy to set the correct bootfile for the BIOS clients (boot\x64\wdsnbp.com)
4. Didn't check the 2 options on the DHCP-tab of the WDS server
5. unchecked the variable Windows shizzle on the TFTP tab
6. Added a boot- and an install file from a windows 10 iso to the WDS server.
7. Firewall rules created on both network to PASS all traffic to each other. (i need to adapt, but first want to see this work.)

Does anybody have an idea?

Kindest regards,

Stijn

Answer 1

@Ratteplan
Hi,
If you have a mix of UEFI and Legacy BIOS machines, you cannot use DHCP Scope Options to direct PXE clients to the Boot Program on the WDS server. You must use IP Helper Table Entries. For more information on configuring IP helper table entries, contact your router/switch manufacturer.

In addition, here are some posts with the similar issue with yours, just for your reference, you can try the method mentioned in them:
https://gal.vin/posts/pxe-booting-for-uefi-bios/
Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Hope above information can help you.

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi,

I did what your post suggested. This all works fine in the same vlan/subnet
Still having issues with the BIOS and EFI boots cross vlan

I'm starting over.
Clean slate and see what this will bring for insights.

Stijn