Jul 26 2017 02:24 AM - edited Jul 26 2017 07:15 AM
Hi community,
we have the following infrastructure. WDS Server for UEFI and one for BIOS Images. Both have MDT 6.3.8443.1000 and ADK 10.1.15063.0 installed.
The BIOS WDS Server works just fine. The UEFI one however does not seems to respond correctly, but I do not really understand what is happening here.
This is what I see after the TFTP Download succeeded. This much I was able to check in the wireshark dump. But after that there seems to be no further communication between the host that I want to deploy and the WDS server. The WDS Event Viewer logs show that the appropriate TFTP File was successfully downloaded and then everything stops and the above screen is shown.
This is the last log:
The Following Client completed TFTP Download:
Client IP: xxx.xxx.xxx.xxx
Filename: Boot\\x64\\wdsmgfw.efi
File Size: 1029536
Client Port: 1191
Server Port: 61459
Variable Window: false
I am lost atm as to where even look for the error. Do you have any ideas how to proceed?
Thank you.
Christian
Update:
While trying to further debug the issue I hit another problem that the event viewer config does not work as expected, as it only shows the log messages from 3 hours before, but not the current ones:
<maybe there is also someone with enough wisdom here to enlighten me>
Jul 31 2017 01:04 PM
Aug 01 2017 01:08 AM - edited Aug 01 2017 01:27 AM
> First of all you don't need 2 wds servers. I expect you are configuring DHCP options to point to each.
Which we do and it used to work.
> Remove DHCP options and add an IP helper on the switch to look t to one server and bios or uefi will be selected on capabilities of system being booted.
This I can not do in our infrastructure. Network is not under my control and network will not allow changes to the network if we can not show that it is absolutely necessary. In this case it is not, because this used to work and it stopped working a couple of days ago, I am still hunting for the reason.
> Additionally if you're really must use 2 wds servers make sure you have both x86 and x64 boot images on wds server otherwise even x64 won't work with x86 components there.
This part sounds interesting, but I do not understand it. Could you please amplify.
Thank you Chris.
Kind regards.
Christian
Feb 07 2020 12:44 PM
Did you ever find a solution to this? I know it's been years....but I am just now running into this problem myself. Here is the situation.
I use WDS to deploy Windows 10 images over 3 different subnets. All 3 used to work just fine regardless of BIOS or UEFI. Now, 2 out of 3 subnets work with both normally, but one of the subnets only works using BIOS, UEFI booting gives the same error that you were experiencing. I asked our Network Admins if any changes had been made and they claim nothing changed. I didn't touch the WDS server during the time it worked and stopped working, so I'm at a point where I just can't get by this error when trying to PxE boot using UEFI. I can't even find 1 solution online for this either...
If you figured out the problem, I'd appreciate it if you could share what you did to resolve it. Thanks.
Dec 02 2020 07:54 AM
@Zephyrius Your problem is solved? I have the same....
Dec 02 2020 12:21 PM