Judging from the screenshot, you have a VirtualBox legacy BIOS, not a UEFI one
However, the machine is trying to boot in UEFI mode according to the screenshots
In this type of case, the address should be
http://srvwapt.mydomain.lan/api/v3/baseipxe?uefi=false
The DHCP configuration that automatically redirects based on the BIOS type must be incorrect.
To understand how this works in DHCP:
Code: Select all
# Si la machine est une machine avec un bios legacy (client-architecture = 00:00) alors:
filename "undionly.kpxe" (on indique ici de démarer ipxe)
# Si la machine est une machine avec un bios legacy (client-architecture = 00:00) ET que c'est ipxe qui demande alors :
filename "http://srvwapt.mydomain.lan/api/v3/baseipxe?uefi=false"
# Si la machine est une machine avec un bios uefi (client-architecture != 00:00) alors:
filename "ipxe.efi";
# Si la machine est une machine avec un bios uefi (client-architecture != 00:00) ET que c'est ipxe qui demande alors :
filename "http://srvwapt.mydomain.lan/api/v3/baseipxe
The machine therefore makes two DHCP requests: one to retrieve the IPXE file, and once IPXE has started, IPXE itself makes another DHCP request to retrieve its configuration URL
Note that our documentation does not mention legacy for Windows DHCP servers:
https://www.wapt.fr/fr/doc/wapt-wads-tf ... hcp-server
Regarding OUs, wapt only displays OUs that are known through the already installed wapt agent. If you want to mention an OU that does not appear, directly modify the field in the top right of the "OU" window
In your example, you selected the domain root, which isn't possible; you need to use an OU. We just haven't implemented security at that level yet
