WDS 2012: UEFI Client Network Boot results in error 0x102

I've got a WDS 2012 and a DHCP Server 2012 running on the same subnet, but on different boxes. I have been deploying Windows 8.1 x64 without any issues to BIOS clients, using DHCP Options 66 and 67.

Now I am trying to deploy Windows 8.1 x64 to HP Computers with UEFI.

I changed DHCP Option 67 bootfile name to boot\x64\wdsmgfw.efi.

When the UEFI Client tries to boot from LAN, it successfully loads wdsmgfw.efi, but then it keeps on "Contacting Server (IP-Address of WDS)" for some minutes and then stops with this message:

Windows Deployment Services encountered an error: Error Code: 0x102

I guess I am missing something here, but I don't know what it is. DHCP Option 60 does not seem to be an option, because dhcp and wds are on dedicated servers.

As soon as I switch back to BIOS and wdsnbp.com everything works again.

May 27th, 2015 4:02am

I don't think you need to change your boot file for UEFI clients, just specify the boot image for UEFI x64 in WDS.

Here is an example picture:

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 10:37am

I don't think you need to change your boot file for UEFI clients, just specify the boot image for UEFI x64 in WDS.

Here is an example picture:

May 27th, 2015 2:36pm

I don't think you need to change your boot file for UEFI clients, just specify the boot image for UEFI x64 in WDS.

Here is an example picture:

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 2:36pm

Without changing the bootfile, this setting leads to boot error.
May 29th, 2015 8:14am

What happens if you do not specify Option 67?

Or you can try changing the Option 67 to \boot\x64\pxeboot.com

I can't test your specific setup as my Server 2008 R2 has DHCP and WDS on it. I have 3 WDS Servers on the network and when I added the 2012 WDS, I didn't have to configure anything... it just worked... Of course, I do not have Option 67 set on my DHCP server, so when a PXE request is sent to either of the 3 servers, the server itself determines which boot rom to use.

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2015 10:50am

What happens if you do not specify Option 67?
BIOS:  PXE-E53 No bootfile name received
UEFI: PXE-E18 Server response timeout
boot\x64\pxeboot.com: An error occurred with the boot selection

June 1st, 2015 8:23am

Got DHCP options 66 and 67 removed and ip helper address pointing to wds installed  - boot.wim can now be downloaded. Thank you guys!
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 9:52am

Got DHCP options 66 and 67 removed and ip helper address pointing to wds installed  - boot.wim can now be downloaded. Thank you guys!
June 1st, 2015 1:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics