Categories

  • 12k Topics
    114k Posts
    B

    I think I have the same problem and I want to be sure of exactly what I need to do (I don’t know if there is a step-by-step tutorial…).

    I boot with a USB-C network adapter on an HP Elitebook. It finds FOG, I have the menu, I choose to deploy an image, and then I get this error message:

    IMG_20251106_162705.jpg

    Is this the problem in question?
    If so, what exactly should I do? I see (link @FlorianLenz ) that I need to replace two files with the new ones, then run the .sh. But isn’t that dangerous for other network boots?

    Thank you in advance for your help.

  • 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
    D

    Finally found out why I couldn’t auth over 636, I needed to add my domain’s CA cert to the FOG server’s root cert store. Once I did that I can now use my AD creds over 636 on the web UI and iPXE menu items.

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

    @Tom-Elliott Just wondering if I could have your input here.

213

Online

12.4k

Users

17.4k

Topics

155.9k

Posts