• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

HP Prodesk 600 PXE Boot Issue

Scheduled Pinned Locked Moved
Hardware Compatibility
2
6
4.4k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    Richard Nihells
    last edited by Jan 26, 2018, 3:15 PM

    We are trying to image a HP Prodesk 600 mini desktop. However when we do the boot into PXE, while it does find Fog, it only downloads the undionly.kpxe file and then kicks back into the BIOS menu.

    This computer is a Windows 10 but that shouldn’t matter since this is a PXE boot issue. I had only tested with a VMWare VM setup with CentOS so I also ran a test on a VMWare Windows 7 VM to just try a Windows computer. That did the PXE and showed the Fog menu correctly.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Jan 26, 2018, 3:29 PM

      Are you sure the computer is in bios (legacy mode) vs uefi mode? If its in uefi mode 1. you are sending the wrong pxe boot file 2. you need to disable secure boot for imaging

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • R
        Richard Nihells
        last edited by Jan 26, 2018, 5:17 PM

        We did go in and enable legacy boot. Secure boot is turned off.

        G 1 Reply Last reply Jan 26, 2018, 5:23 PM Reply Quote 0
        • G
          george1421 Moderator @Richard Nihells
          last edited by Jan 26, 2018, 5:23 PM

          @richard-nihells ok so its legacy mode, the undionly is probably the right boot kernel. You can try undionly.kkpxe (note the 2 Ks).

          I should also ask, what version of FOG are you using?

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          1 Reply Last reply Reply Quote 0
          • R
            Richard Nihells
            last edited by Jan 26, 2018, 5:32 PM

            How do I try undionly.kkpxe.

            Version 1.4.4

            G 1 Reply Last reply Jan 26, 2018, 5:41 PM Reply Quote 0
            • G
              george1421 Moderator @Richard Nihells
              last edited by Jan 26, 2018, 5:41 PM

              @richard-nihells You change the dhcp option 67 {boot-file} to that name.

              So you are using 1.4.4. That’s good so you have a current version.

              When its pxe booting, do you seen anything that says NBF? What your describing really sounds like a computer in uefi mode, being sent a bios kernel.

              Just so you know bios (legacy) mode requires undionly.(k)kpxe kernels, where uefi mode requires a uefi kernel ending in .efi, like ipxe.efi again that would be set in your dhcp boot options.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                4/6
                Last post

              217

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project