Summary: I have a SonicWall. How do I configure it to allow PXE boot for my K2000 appliance?
Solution:
To configure SonicWALL for PXE clients:
- Open Network | DHCP Server
- Edit DHCP Lease Scope range
- Check box Allow BOOTP Clients to use Range
- Click Advanced tab and enter:
Next Server: IP Address of the TFTP server
Boot File: name of the boot file
Server Name: name of the server (not required)
- Click OK
https://support.quest.com/kace-systems-deployment-appliance/kb/217556/dhcp-configuration-for-bios-and-uefi-pxe - AKaceUser 6 years ago
https://en.wikipedia.org/wiki/IPXE
All the settings are the same regardless of the Imaging solution being used, the only that will change is the IP address to reflect yours.
Also there are some DHCPs like Windows Server 2008 and older, that are UNABLE to handle UEFI and Legacy boot files at the same time, hence you need to manually change the value of your bootfile to either
undionly.kpxe for Legacy
OR
ipxe.efi for UEFI
You may want to share that Wiki link with them, as this is not a software developed by Quest, and UNIX based open-source.
There are guides for others DHCPs on Quest's site, but not for Sonicwall.
InfoBlox DHCP:
https://support.quest.com/kace-systems-deployment-appliance/kb/155657/how-to-setup-infoblox-pxe-to-work-with-the-kace-systems-deployment-appliance
BlueCat DHCP:
https://support.quest.com/kace-systems-deployment-appliance/kb/234459/bluecat-dhcp-configuration-for-bios-and-uefi-pxe
Cisco Solaris and Other Linux based:
https://support.quest.com/kace-systems-deployment-appliance/kb/112037/setting-up-non-microsoft-dhcp-server-cisco-solaris-and-others-
PFSense DHCP:
https://support.quest.com/kace-systems-deployment-appliance/kb/218032/pfsense-dhcpd-configuration-for-uefi-and-bios-pxe-boot
So SONIC Wall guys need to determine if that DHCP is capable of handling Legacy or UEFI at the same time, if not, they just change the bootfile name value to one of TWO values above, and try again. - Channeler 6 years ago