I thought that I would start a new thread since I couldn't find a clear answer on the forum. I am trying to find the steps to verify that my Server 2012 R2 WDS server is capable of PXE booting both Legacy and UEFI computers. When I try to PXE boot a Dell E5440 in UEFI mode it will say "Start PXE over IPv4." Something about the NBP file quickly pops up and disappears then the screen flashes and moves onto IPv6 despite that boot option being disabled in the BIOS. The UEFI network stack is enabled. I have both 32 and 64 bit LiteTouch WinPE images available through PXE.

Any idea?

Ideas? I m must not be the only one trying to PXE boot Legacy and UEFI computers.

Any help would be appreciated.

Windows Server 2012 R2 should support PXE booting for uEFI and BIOS clients.

I have seen some problems for WDS Server boxes that were "upgraded" from previous versions of Windows Server and/or boot files were xcopy'ed to the WDS Server, rather than allowing the WDS tools to "import" the boot wim files.

Try fully updating the x86 and x64 boot files on the server, that should force an update of all the boot files.

The only things I have done with WDS is turn on the role add my LiteTouch WinPE images. How/Why would I go about updating the boot files?

To be clear, this is a fresh install of Server 2012 R2. Not an "upgrade."

When you "import" a boot wim into WDS the WDS Service does more than just copy the wim file locally, it also extracts and prepares several other supporting files. That bin file that prompts for F12, and the file that bypasses the F12 prompt? yea both of those. Since your questions were directly related to the boot operation just *before* the WinPE Boot wim file is loaded, it would be a good to verify those files, hense my suggestion.

The fact that this is a clean installation is good news, although I'm still not clear as to how you added the WinPE images. WPEUtil.exe? Through the WDS console, or did you just copy the files locally via the windows explorer.

If you still have problems, I would suggest asking in the Windows Deployment forums, perhaps someone there can escalate to MSFT. Be prepared to provide WDS Logs.

I added the LT boot images through the normal console/GUI. I re-created them and added them again to WDS. Same thing. When I select the Onboard NIC (IPv4) it appears like it starts to download the NBP but then stops and skips to try IPv6. 

As far as I know our networking team have DHCP IP helpers on the switches. Could they need a config change for UEFI? 

You are missing one little "unofficial" step.

If you have a Windows 2008R2 WDS server and selected the following DHCP option on the Windows Server 2008R2 DHCP server:

Option 067   smsboot\x64\wdsmgfw.efi (=UEFI x64 Boot)

Then it would boot into pxe but then it will fail en you will see that it will try IPv6.

To fix this you only need to copy a file from an Windows WDS Server 2012(R2)

WDS 2012 R2 (Boot folder)

WDS 2008 R2 (Boot Folder)

Now copy folder "x64uefi" to your Windows 2008R2 WDS server.

And you will see that is works now.

• Edited by Makaveli1976 15 hours 15 minutes ago typo

Having DHCP Options for PXE is just bad practice overall and you should consider this a workaround instead a solution. You broke the non UEFI support if I am not mistaken by doing that.

I am having no issues with the new Dell models.
Just get rid of all your strange DHCP Options and configure IP Helpers instead as recommended.

Maybe disable NetBios on the WDS server too, depending on the PXE firmware this can cause timeouts in certain environments.

Are your clients and server in the same subnet?
If yes a misconfiguration of the IP helpers is not the issue.

• Proposed as answer by oriooff 7 hours 25 minutes ago
• Edited by oriooff 7 hours 19 minutes ago

In my own setup i use a W2012R2 DHCP server. (and W2012 R2 WDS)

And with help of vendor classes and DHCP Policy's I can redirect my clients to the appropiate WDS boot file.

Vendorclass: PXEClient:Arch:00007 =UEFi PXE x64

Vendorclass: PXEClient:Arch:00006 =UEFI PXE x86

Venderclass: PXEClient:Arch:00000= BIOS Legacy

The next step is to cofigure Policy's to recognize certain PXE request en redirect them to the correct files and then it works like a charm.

• Edited by Makaveli1976 11 minutes ago