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

pxe-bootuefiwdswindows-server-2012

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.

In order to be able to boot my UEFI-Client from LAN 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.

Best Answer

Removed dhcp options 66 and 67 and added ip helper address pointing to wds. additionally had to disable netbios over tcp/ip on the wds server.

Related Solutions

Client see Windows Deployment Services but still get “selected boot device failed” error

We have two internet connections DHCP uses router 10.0.1.2 and Servers use 10.0.1.1. When I switched the Gateway IP on the WDS server to 10.0.1.2 everything worked just fine.

PXE with WDS & Windows Server 2012 – no filename option in DHCP lease

PXE uses DHCP. You can run PXE on a network with separate PXE and DHCP servers, but PXE does need to listen on DHCP. It just can't hand out IP addresses.

It kind of goes like this:

PXE Client:  DHCPREQUEST, p.s. I'm a PXE Client.
DHCP Server:  DHCPACK, Here's your IP! p.s., PXE over there ->
PXE Server:  DHCPACK, Hello, I'll be your PXE server today...

So you're going to need to make changes to the DHCP server (to specify to PXE clients where to get PXE services) and possibly the routers as well (to specify the PXE server as a DHCP helper).

I don't have access to the environment where I had this working because I've switched jobs since then, but here are some suggested DHCP scope options:

Predefined Option 43 - 010400000000FF
Custom-made Option 60 - String - PXEClient
Predefined Option 66 - IP or Hostname of the WDS Server
Predefined Option 67 - boot\x86\wdsnbp.com

I got these here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/e84c8a4c-a6da-4c4a-8ca6-2a1007b205ae/wds-server-and-dhcp-server-on-two-different-servers

Good luck!

Best Answer

Related Solutions

Client see Windows Deployment Services but still get “selected boot device failed” error

PXE with WDS & Windows Server 2012 – no filename option in DHCP lease

Related Topic