Link to home
Start Free TrialLog in
Avatar of rmeany
rmeany

asked on

Need Help Configuring Syslinux EFI boot on WDS Server

From what I understand, the latest releases of PXE/Syslinux fully support EFI boot now.  I'm trying to get it up and running using similar methodology that I used to get PXELinux working for BIOS machines via WDS.  

I copied syslinux-6.03/efi64/efi/syslinux.efi and syslinux-6.03/efi64/com32/elflink/ldlinux/ldlinux.e64 into the WDS RemoteInstall share under /Boot/x64/ ...

I then ran the following commands on the WDS server to tell it to provide the path to syslinux.efi for efi clients:

wdsutil /set-server /bootprogram:boot\x64\syslinux.efi /architecture:x64uefi
wdsutil /set-server /N12bootprogram:boot\x64\syslinux.efi /architecture:x64uefi

When I attempt to PXE boot an EFI client, I am presented with the following error in WDS:

"Windows Deployment Services Encountered an Error ... Error Code 0xC0000022"

Anyone have any hints as to what I may be doing wrong here?
Avatar of vivigatt
vivigatt
Flag of France image

Just to make one thing clear:
You are not using any DHCP option 66 and 67 are you?
If son you should not.
Take a look at my article for more details about that:
https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-options-60-66-and-67-what-are-they-for-Can-I-use-PXE-without-it.html
Avatar of rmeany
rmeany

ASKER

No, I am not using any statically configured DHCP options.  I am relying on WDS to advertise.  

To update what I've discovered regarding this,

The error code 0xC0000022 was caused by having secure boot enabled in the BIOS settings of the client machine.  Disabling that caused that error to go away.

However, WDS would still not boot syslinux at that point.  The WDS screen would come up and just hang at "contacting server xxx.xxx.xxx.xxx ... Getting cached packet ... my ip is yyy.yyy.yyy.yyy" (the IPs were valid).  

I had found a post where someone else encountered the exact same problem only on certain machine types with WDS not finishing the load of syslinux.efi:  http://www.syslinux.org/archives/2013-June/020242.html

So it sounds like there is some feature of WDS that is not properly handing off to syslinux.efi on certain hardware.  From what I understand, syslinux cannot chainload further .efi files so even if I did get syslinux.efi to load from WDS, I couldn't have the option to continue to WDS in the menu.  I personally won't bother investigating further as it's just not worth the effort to me - we can boot our other options off a USB drive and just go straight into WDS for EFI deployments.  

If anyone happens to have further insight on this,  it would certainly be appreciated though!
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.