Subcategories

  • Technical help directly related to FOG.
    9k Topics
    85k Posts
    J

    Hello,
    few computers with fog client (0.13) refuse to appear in pending host from one day to the next without reason.
    Client does 3 times :

    ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 13/01/2026 16:14:33 Client-Info Version: 0.13.0 13/01/2026 16:14:33 Client-Info OS: Windows 13/01/2026 16:14:33 Middleware::Authentication Waiting for authentication timeout to pass 13/01/2026 16:16:32 Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt 13/01/2026 16:16:32 Middleware::Authentication Cert OK 13/01/2026 16:16:32 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before 13/01/2026 16:16:32 Middleware::Authentication ERROR: Could not get security token 13/01/2026 16:16:32 Middleware::Authentication ERROR: Le fichier 'C:\Program Files (x86)\FOG\token.dat' est introuvable. 13/01/2026 16:16:32 Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService 13/01/2026 16:16:32 Middleware::Response Invalid host 13/01/2026 16:16:32 Middleware::Communication URL: http://fogserver/fog/service/register.php?hostname=SALLEA08-03&mac=1C:69:7A:C2:4E:23&newService&json

    Then end with :

    13/01/2026 16:16:33 Client-Info ERROR: Failed to authenticate, will not run Module Looper.

    I was running FOG 1.6.0alpha then update to 1.6.0-beta.2262 but it was the same.
    I had to import them with csv to unlock the situation on the client.

    I don’t know what log to check to understand the problem.

    Thank you for your help.

  • Problems with specific computer models.
    710 Topics
    8k Posts
    D

    @george1421 Today’s findings:

    autoexec.ipxe is getting loaded by some default somewhere (not because of my dnsmasq entry) and it’s completely ignored. None of its contents get run. I confirmed the correct autoexec.ipxe file is actually being loaded by renaming it, attempting a boot, and observing a ‘file not found’ error message. I pulled bzImage and init.xz directly from the latest release and N-1 https://github.com/FOGProject/fos/releases to ensure compatibility. No change. This server’s NIC does not support the native iPXE drivers. Only snponly.efi works.

    No joy 😞

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    G

    Hi Again guys

    I have some news about this problem.
    I found a work around.

    I change the file d1.fixed_size_partitions deleting the recovery Windows partition. This change generated and error when I made the deploy image in Client PC.
    But if I cancel the job in the CLI fog server and reset the client machine after fog show the error
    It boot ok.

    I’ll continue reading …
    Thanks

  • Technical help related to a Linux Problem.

    726 Topics
    6k Posts
    J

    Ok so I now have a second system with the EXACT same issue. I purchased a Dell Precision 7875 which has 2 on-board nics. I updated our dhcp server to issue an IP address for one of the two NICs. With the system connected to that interface I PXE booted the system. The first stage of the fog shows as it notices the system is not registered and asking whether I would like to register the system. Yet once I say do full registration that’s it it will not proceed further.

    So similar to the issue that I’ve raised prior with multiple NICs and @george1421 suggested I PXE booted the system again but went into DEBUG mode. Well as it appears the unused MAC address is now showing up on the interface that I had configured to connect to the network. Seeing that I did not assign an IP address to the second mac address the system would not proceed any further. The odd thing is that BOTH interfaces show up having the same mac address. It seems that there’s an issue with the FOS with newer Dell systems with multiple NICs.

    If I disable one of the two NICs in the BIOS, and do the re-imaging process everything works fine…

    Really looking for a fix for this…

    Cheers

    Jason Naughton

  • Technical help related to a Mac Problem.

    80 Topics
    942 Posts
    B

    Hello everyone,

    As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
    I already use FOG to deploy Windows and Linux images on PCs.

    I would like to deploy a LinuxMint image on these iMacs.

    However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

    I modified my DHCP server as follows:

    ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

    I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

    I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

    Thanks in advance!

  • General Developer questions relating to FOG.
    682 Topics
    5k Posts
    K

    @raul I have an Ansible role which does something akin to what you’re trying to do here:
    https://forgejo.cwavs.xyz/Cwavs/ansible-role-fog it might be worth taking a look and seeing if it helps give you any ideas on how to solve your problem. Happy to answer questions about it.

174

Online

12.5k

Users

17.5k

Topics

156.1k

Posts