Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    12k Topics
    114k Posts
    A

    Have been using Fog for a couple of years now and it has been working flawlessly for us until a couple of days ago.

    Fog is installed on Ubuntu via the git method, Fog is running version 1.5.10.11 with kernel 6.12.35 and we use the ipxe.efi boot file

    We have secure boot enabled on all our devices and Fog has been configured to work with this using signed images and deployment files.

    We have a single image for Windows 11 and that has been deployed without issue to a load of Dell laptops and desktops. We have also managed to deploy the image to some Stone desktops.

    The Stone laptops are proving problematic. They PXE boot and join the task and the image is deployed fine but as soon as the device reboots it hangs with the manufacturers logo displayed on the screen and refuses to post.

    I can’t get in to the BIOS unless I pull the hard drive, by some fluke if I put the drive back in the machine will boot but then after a reboot it hangs again. On some rare occasion it will actually continue to work.

    I don’t think the issue is with Windows 11 as I can deploy a Windows 10 image and go through the update process and install Windows 11 and the laptop is happy but this isn’t an ideal solution.

    I am wondering if the task end sequence and clean up is causing some kind of issue but I don’t really know where to start. As I have said already these laptops worked fine with the Windows 10 image.

    Has anyone seen this issue before and able to offer some much needed advice to resolve the issue please?

    Thanks

  • Get the latest news on what's happening.
    Security Advisories
    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.
    General Tutorials
    2k Topics
    19k Posts
    A

    @george1421 I see now and you’re right as my clients are all legacy boot/BIOS boot non UEFI and would not benefit from the client-arch examination.

    I’ve already declarations set for each host in my dhcpd.conf file in terms if MAC to IP and so adding another field of filename “some boot loader file” won’t be impossible.

    Thanks you for this exercise as I’ve learned some very important things here.

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    F

    @Tom-Elliott Thanks, going to switch back to 1.6 very soon.

193

Online

12.3k

Users

17.4k

Topics

155.8k

Posts