[SOLVED] : iPXE and WDS Config

[sebus]

I see you mean option 252 as here: http://ipxe.org/appnote/chainload_wds

But what would one expect in that option for the above to work?

With UEFI PXE IPv4->iPXE->menu->.ipxe script

Code:

#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
set proxydhcp/next-server AAA.BBB.CCC.DDD # IP of WDS server
set proxydhcp/filename SMSBoot\x64\wdsmgfw.efi
set proxydhcp/dhcp-server AAA.BBB.CCC.DDD # IP of WDS server ?
set wdsserver:ipv4 192.168.XX.XX
set netX/next-server ${wdsserver}
chain tftp://${wdsserver}/SMSBoot\x64\wdsmgfw.efi

I get WDS to respond but gets "stuck" on only Contacting Server



In the smspxe.log I can see a successful PXE boot (as per https://blogs.technet.microsoft.com/ping...-20072012/ )

Code:

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778293" ServerName=""><Machine><ClientID>GUID:841AA243-DB51-4562-AF0D-EB9E4EE64F75</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SP1201F9" OfferIDTime="02/02/2017 14:40:00" PkgID="SP100115" PackageVersion="" PackagePath="http://sccmserver.domain.local/SMS_DP_SMSPKG$/SP10017B" BootImageID="SP10017B" Mandatory="1"/></ClientIDReply>
    SMSPXE    12/02/2017 19:06:23    7716 (0x1E24)
00:15:5D:A4:A7:99, DEF39572-90C2-F142-B361-C21B8675A333: using advertisement SP1201F9    SMSPXE    12/02/2017 19:06:23    7716 (0x1E24)

but nothing more happens

sebus