[SOLVED] DHCP configuration for ISO deployment

[admgautier]

Hello,

I would like some clarification on the DHCP server configuration required to deploy an ISO via WAPT.

I have configured my TFTP server as described in your documentation.

Regarding the DHCP settings, is it simply a matter of executing the indicated PowerShell commands? (Replacing the variables `$waptserver_ipaddress_tftp = "192.168.154.13"` and `$url_waptserver = "http://srvwapt.mydomain.lan"`, of course?

When I enter the following URL, nothing is displayed:
`$url_waptserver/api/v3/baseipxe`.

Is this normal? Will the baseipxe be created after the script is executed?

Thank you in advance for your further information.

[dcardon]

Hello admgautier,

in your screenshot, the string returned by the WAPT server is correct. The variable will be replaced by the iPXE bootloader.

Is the client machine able to retrieve the iPXE bootloader? The most common problem is the secureboot configuration on the UEFI BIOS, which requires a signed bootloader.

Regards,

Denis

[admgautier]

Hello everyone,

thank you for your feedback.

I did disable secure boot on the client machine, however I used the powershell commands to configure the DHCP server:
$waptserver_ipaddress_tftp = "192.168.154.13"
$url_waptserver = "http://srvwapt.mydomain.lan"

Add-DhcpServerv4Class -Name "legacy_bios" -Type Vendor -Data "PXEClient:Arch:00000"
Add-DhcpServerv4Class -Name "iPXE" -Type User -Data "iPXE"

Set-DhcpServerv4OptionValue -OptionId 66 -Value "$waptserver_ipaddress_tftp"

Add-DhcpServerv4Policy -Name "wapt-ipxe-url-legacy" -AND Condition -UserClass EQ,iPXE -VendorClass EQ,legacy_bios*
Set-DhcpServerv4OptionValue -PolicyName "wapt-ipxe-url-legacy" -OptionID 67 -Value "$url_waptserver/api/v3/baseipxe?uefi=false"

Add-DhcpServerv4Policy -Name "wapt-ipxe-url-uefi" -Condition AND -UserClass EQ,iPXE -VendorClass NE,legacy_bios*
Set-DhcpServerv4OptionValue -PolicyName "wapt-ipxe-url-uefi" -OptionID 67 -Value "$url_waptserver/api/v3/baseipxe"

Add-DhcpServerv4Policy -Name "ipxe.efi" -Condition AND -UserClass NE,iPXE -VendorClass NE,legacy_bios*
Set-DhcpServerv4OptionValue"undionly.kpxe"

Add-DhcpServerv4Policy -Name
Set-DhcpServerv4OptionValue -PolicyName "undionly.kpxe" -OptionID 67 -Value "undionly.kpxe"

I'm careful to modify the $waptserver_ipaddress_tftp and $url_waptserver variables.

However, nothing is being reported on the client machine.

I don't really understand where the problem is coming from.

[sfonteneau]

Can you describe the machine's behavior in more detail? Could you provide

a photo of the machine booting up so we can see where it's failing?

[admgautier]

Hello,

First, here is my DHCP configuration.

Then, when I start my machine, here is the result.

TFTP has been correctly configured on the WAPT server and has started correctly.

[admgautier]

If needed, here is the version of my WAPT server:

[sfonteneau]

It seems there's a double slash in the policies "wapt-ipxe-url-legacy" and "wapt-ipxe-url-legacy" "//api".

Then you have a policy "iPXE" (the first line in the screenshot). You should delete it; it's a history entry that I think could cause a conflict.

You also have a wdsnbp.com entry that could conflict with the other rules. Is it still in use?

[admgautier]

Indeed, there was an unnecessary double slash. My apologies.

Regarding the other options, they were already present on the server, and removing them improves my machine's performance.

I tried configuring the iPXE strategy following this thread: viewtopic.php?p=9879#p9879.

The machine is searching for the configuration via PXE. I'll continue your webinar to complete the configuration with a generalized image: https://www.youtube.com/watch?v=zREmQ_0sM88.

I then tried to reinstall via iPXE but got the same result. Before deleting /boot wdsnbp.com, the machine would load a page and try to load that Boot\x86\wdsnbp.com... without success, of course.

I've attached my new DHCP configuration. Do you see any errors?

Thanks again for your support.

[admgautier]

I also noticed that the first two lines of PowerShell failed to execute correctly.

Could that be the source of the problem?

[sfonteneau]

Regarding the other options, this was already present on the server, and by removing them my machine is already responding better.

That's to say ?

That's better, so we have a different error? I didn't quite understand

For PowerShell errors, it indicates "ResourceExists", so we'll assume that's okay