Categories

  • 12k Topics
    114k Posts
    S

    In the start of the week same of our PCs suddenly got an error. After the FOG start menu we got this error:

    Starting bootmgfw.efi Using load options '' Secure Boot validation failure loading bootmgfw.efi!

    Our PC support told us to update our BIOS because of new signatures (Starting directly on Windows without FOG in between gave us also a Invalid signature error). After the update we can boot into Windows, but now we have problems booting into FOG.
    It’s loading the NBP file and iPXE is starting, then we getting the following error

    iPXE 1.20.1+ Configuring (net0 xx:xx........) .......... No configuration methods succeeded (http://ipxe.org/040ee186) Configuring (net0 xx:xx........) .......... No configuration methods succeeded (http://ipxe.org/040ee186)

    After that I go into the PXE shell and try typing dhcp. This gives me an “OK” always after the 2nd try. So im again in the FOG starting menu and want to boot into Windows and I’m getting the following error:

    http://......... refind.conf ......... Connection times out (http://ipxe.org/4c0a6092) Could not boot: Connection timed out (http://ipxe.org/4c0a6092) Could not boot: Connection timed out (http://ipxe.org/4c0a6092)

    Our setup is:
    Your version of FOG is up to date.
    You’re running the latest stable version: 1.5.10
    Custom signed files with this tutorial: https://forums.fogproject.org/topic/15888/imaging-with-fog-and-secure-boot-poc
    Changed from ipxe.efi to snponly.efi didn’t helped.

    Someone knows what’s the problem here and how to solve it? Do I need to update the FOG server or just update the pxe file?

    Thanks in advance

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Cire3C

    @youzersef Ok, see how long it takes me to get back on a project…lol

    I did some more looking, and found yes, the GUI will re-write the dhcp config file. However I did some more reading and I guess services.inc determines what is written by the GUI.

    Sorry, not a CLI guy, and I love the quick and easy edits, viewing issues that the GUI provides. Like Fog ! However my servers are headless…lol

    Anyway, looking that route now, and will update if I find how Negate wants services edited so when it reboots, DHCP will remain.

    Determined 🙂

    Any thank you everyone here . This place has always been great for information !

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    H

    @rodluz yes, directly from 1.5.10.1754 to 1.5.10.1763 when I saw the prompt in the FOG gui that I’m not using the latest version - it was up to date before.

    in 1.5.10.1754 recapture didn’t added up, just updated the image size to the latest one.

164

Online

12.5k

Users

17.5k

Topics

156.3k

Posts