Hi Tony,
You must configure the option 67 to the desired URL, like
http://yourserverIP/ipxe.efi and also create an option 60 with value set to
HTTPClient
To create a vendor class, I used the following value without quotation marks
"HTTPClient:Arch:00016" with Wildcard option checked. This indicates that a
UEFI x64 HTTP device is booting.
Regards,
LEANDRO GUSTAVO BISS BECKER
Development Engineer
Engenharia Industrial - Manaus
lbec...@positivo.com.br
Positivo Tecnologia
Tel.: +55 92 3183-7988
-----Mensagem original-----
De: ipxe-devel-boun...@lists.ipxe.org <ipxe-devel-boun...@lists.ipxe.org> Em
nome de Tuzhenhua
Enviada em: sábado, 22 de dezembro de 2018 01:45
Para: ipxe-devel@lists.ipxe.org
Assunto: [ipxe-devel] How to UEFI HTTP chainload using MS DHCP
Hi iPXE,
I'm trying UEFI HTTP chainload with a MS DHCP server and IIS.
I checked online document http://ipxe.org/appnote/uefihttp. It's for ISC.
Since I had a existing MS DHCP which successfully boot with TFTP chainload
with iPXE, I still want to use it for UEFI HTTP chainload.
I tried to create a vendor class. Use 67 to lunch ipxe.efi and policy to
lunch true boot.ipxe script. But nothing happened on the client when boot into
DHCP query.
Would you please guide me to setup MS DHCP server for UEFI http Chainload?
It's much much appreciated for any help.
Regards,
Tony
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
