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

    Imaging a computer in UEFI mode doesn't add it in the boot order in the BIOS

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    4
    9
    1.9k
    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.
    • THEMCVT
      THEMCV
      last edited by

      Server
      • FOG Version: 1.3.0 RC-36
      • OS: Debian 8.6
      Description

      Imaging a computer in UEFI mode doesn’t add it in the boot order. So if I’m running the ipxe.efi boot file it will image completely fine, but when the computer reboots it doesn’t know how to get to Windows. If I check the BIOS, only the Network boot options and the CD Drive are listed for booting.

      Is there something I’m doing incorrectly or is there something that needs to be set in FOG or is this even possible to do? People seem to not be having and issue imaging UEFI systems on here.

      Thanks,

      THEMCV

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • Q
        Quazz Moderator
        last edited by

        You’ll need to set its boot mode to UEFI.

        THEMCVT 1 Reply Last reply Reply Quote 0
        • THEMCVT
          THEMCV @Quazz
          last edited by THEMCV

          @Quazz It is in UEFI mode, but it doesn’t see the drive after FOG has imaged it. doesn’t put it in the boot order and go to Windows after imaging.

          Q Tom ElliottT 2 Replies Last reply Reply Quote 0
          • Q
            Quazz Moderator @THEMCV
            last edited by

            @THEMCV Sounds like a problem with the BIOS 😕

            THEMCVT 1 Reply Last reply Reply Quote 0
            • THEMCVT
              THEMCV @Quazz
              last edited by

              @Quazz We only have Dells. Bleh. Been a bad week for this stuff. OptiPlex 7040’s so far have been awful.

              1 Reply Last reply Reply Quote 0
              • Tom ElliottT
                Tom Elliott @THEMCV
                last edited by

                @THEMCV it would only remove the entry if told to do so. Normally it would try to auto detect based on values stored in the ‘nvram’

                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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                THEMCVT 1 Reply Last reply Reply Quote 0
                • THEMCVT
                  THEMCV @Tom Elliott
                  last edited by

                  @Tom-Elliott Okay, so maybe it’s a matter of adding the entries. The one I did testing with was on Legacy mode, then switched to UEFI and imaged.

                  So this value needs to be added in regardless to the BIOS and is separate from FOG?

                  To be honest, this is my first time working with UEFI on an enterprise level.

                  Q 1 Reply Last reply Reply Quote 0
                  • Q
                    Quazz Moderator @THEMCV
                    last edited by

                    @THEMCV It should happen automatically, though I’ve seen a few Dells that don’t do it 😕

                    1 Reply Last reply Reply Quote 0
                    • Wayne WorkmanW
                      Wayne Workman @THEMCV
                      last edited by Wayne Workman

                      @THEMCV said in Imaging a computer in UEFI mode doesn't add it in the boot order in the BIOS:

                      but when the computer reboots it doesn’t know how to get to Windows.

                      That sounds like an exit type problem to me.

                      At my old job, we had Optiplex 7040s, they imaged fine. If memory serves, set the UEFI and BIOS exit types to grub. Do this on the host’s general page via the web interface. If you have a bunch of them, this can also be done via groups.

                      It could also be that you took the image from a BIOS type machine, and are deploying to UEFI type machines. In this case, you need to make sure the reference machine is setup exactly like the target machines are firmware settings wise.

                      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!
                      Daily Clean Installation Results:
                      https://fogtesting.fogproject.us/
                      FOG Reporting:
                      https://fog-external-reporting-results.fogproject.us/

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

                      142

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.3k

                      Posts
                      Copyright © 2012-2024 FOG Project