Can the K2000 PXE boot using IP Helper statements only (no DHCP scope options)?
A Dell engineer stated in this post 4 years ago that the only way to PXE boot with Kace is by setting the DHCP 66 & 67 scope options. Is this still true? If so, why is that? We've used Altiris and SCCM and neither of those required scope options to be set for PXE booting, they worked fine with only IP Helper statements.
Has anyone gotten PXE to work with the K2000 without the DHCP options?
Thanks!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
bobot4258
7 years ago
When we originally setup the K2000 we used DHCP options 66 and 67 to point to the K2000.
Since the K2000 does not support UEFI PXE booting and I got tired of needing to use the USB stick method I setup a WDS server with the K2000 boot.wim file and then PXE boot to the WDS server which then transfers you over to the K2000.
When setting up the WDS server I removed the DHCP options 66 and 67 and I am only using IP helper addresses that point to WDS. Doesn't entirely answer your question although I would think you could PXE boot to the K2000 with only IP helper addresses. I would seriously consider setting up an environment like I mentioned as a lot of newer computers support UEFI now.
Comments:
-
Thank you for confirming what we've seen and for the suggestion bobot. We haven't made the transition to UEFI yet, we've been setting everything to legacy boot up to this point. This does seem like something that could work. It just seems odd that we were able to PXE with Altiris/Ghost and SCCM without the DHCP options, but Kace requires them, even without UEFI. - awenwonder 7 years ago
Posted by:
TheAustinDave
7 years ago
On UEFI PXE boot, the release of version 4.0 will allow PXE boot for either UEFI or Legacy mode and should be released soon.
Comments:
-
I can confirm that 4.0 will support either format - SMal.tmcc 7 years ago
-
Our K2000 has been upgraded to version 4.0. We removed the DHCP scope options and with PC's still set to Legacy mode we are still unable to PXE boot using only the IP Helper statements. Am I misunderstanding what you guys are saying, or should this not work? - awenwonder 7 years ago
-
Most likely there will need to be some type of policy statements created, while the 4.0 version does support UEFI or Legacy it needs to have the arch info to be able to determine which method to use and which file set to deliver to the target system.
(example policy from code of non-Microsoft DHCP, but you can see how its making the choices)
next-server 172.16.2.174;
if option arch = 00:06 { # This entry is for PXE booting systems with
filename "ipxe.efi"; # 32-bit UEFI firmware, which isn't supported
} else if option arch = 00:07 {
filename "ipxe.efi";
} else if option arch = 00:09 {
filename "ipxe.efi";
} else {
filename "undionly.kpxe";
} - TheAustinDave 7 years ago