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

    Surface Pro 6, PXE Failing

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    3
    6
    1.3k
    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.
    • T
      TBCS
      last edited by

      So when I try to PXE boot, the Surface Pro 6 tells me roughly

      Start PXE Boot from IPv4
      Correct IP
      Undionly.kpxe
      Downloading NBP File
      File Downloaded successfully

      But then it just moves on. No error message, just a restart. Does anyone have any ideas for me? I’m very new to FOG and have had no trouble with any other machines I’ve tested it on.

      x23piracyX 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

        The short answer is you are sending the wrong boot loader to that computer. I’m going to bet that surface pro is a uefi only computer. You need to send ipxe.efi to that computer instead of undionly.kpxe which is a bios pxe boot loader.

        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
        • T
          TBCS
          last edited by

          Ok that makes sense, the boot loader (DHCP 067) is the part that I was the least familiar about (basically I just knew that I needed to write undionly.kpxe in there and didn’t really know what it meant). That makes a lot of sense when you put it that way. Thanks for your help!

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @TBCS
            last edited by george1421

            @TBCS Do you plan to support both uefi and bios based systems at the same time? If so, do you have a linux or windows 2012 or newer dhcp server? There is a wiki page that shows how to configure them to dynamically provide the proper boot file based on the pxe booting client.

            https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

            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!

            T 1 Reply Last reply Reply Quote 1
            • x23piracyX
              x23piracy @TBCS
              last edited by

              @TBCS this device can afaik only boot uefi you habe to disable secure boot also.

              Like george is telling you, you need to get efi booting working.

              Regards X23

              ║▌║█║▌│║▌║▌█

              1 Reply Last reply Reply Quote 0
              • T
                TBCS @george1421
                last edited by

                @george1421 That was a really helpful guide. Easy to follow and now we’re ready for whatever type of boot we need.

                1 Reply Last reply Reply Quote 1
                • 1 / 1
                • First post
                  Last post

                210

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project