We upgraded to K2v4.

I followed the instructions in this video: K2000 Native UEFI PXE Network Booting (https://support.quest.com/k2000-systems-deployment-appliance/videos)

Which made me change our old PXE boot filename from "k2000.0" to "undionly.kpxe", since this change only UEFI PXE boot works, our old PXE systems get an error during DHCP saying the "no boot file name received".

So now I ask, does that PXE boot file need to be changed? If not, then the video needs to be corrected. The video says it is for v4.

Edit: since I posted this I did change the boot file back to K2000.0 and it still fails
Answer Summary:
Cancel
1 Comment   [ + ] Show Comment

Comments

  • Can you tell me how I determine what our current PXE boot file name is? We're currently running K2000 version 4.1.182.
Please log in to comment

Answer Chosen by the Author

1
For version 4.0, undionly.kpxe is correct for the bootfile name to pxe boot bios systems using iPXE.  However, using k2000.0 will also work, but it uses pxelinux and is slower.

What server are you using?

Because it isn't working, this leads me to believe that the policy is incorrect (or misspelled), it must match identically to
PXEClient:Arch:00000

Screenshots of your config would be helpful too.
Answered 01/05/2017 by: cserrins
Red Belt

  • Ok, after watching that video for the 4th time, I paid attention to the little orange balloons stating "not all environments support all CAPS". So you were correct....I had ARCH all caps in my config. After corrected that (I had to recreate the vendor class as it wouldn't let me edit). My PXE boot is alive once again!!!
    • is it 4 or 5 zeros. The video Balloon when it comes up only has 4.
      • For undionly it is PXEClient:Arch:00000 (5 zeroes).
      • Thanks!
Please log in to comment

Answers

Answer this question or Comment on this question for clarity