Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  12.3k
  Topics
  113.4k
  Posts

  R

  Hi all,

  Firstly, thank you all for the huge amount of work you’ve put into this project it’s seriously impressive.

  I’ve been deploying Windows using FOG Project for a few years now, but I’ve encountered an error that I haven’t seen before and it’s driving me insane.

  FOG Version: 1.5.10.1639
  Kernel Version: 6.1.22
  Init Version: 2024.02.1
  FOG Server OS: Debian 12
  Storage Node OS: Debian 12

  I use DNSMasq for the boot files, I’ve attached the config below (IP’s removed, but it’s configured to my server)

  #Don’t function as a DNS server:
  port=0

  #Log lots of extra information about DHCP transactions
  log-dhcp

  #Set the root director for files available via FTP.
  tftp-root=/tftproot

  #The boot filename, server name, server ip address
  dhcp-boot=undionly.kpxe,...**

  #Disable re-use of the DHCP servername and filename fields as extra
  #Option space. That’s to avoid confusing some old or broken DHCP clients.
  dhcp-no-override

  #inspect the vendor class string and match the text to set the tag
  dhcp-vendorclass=BIOS,PXEClient:Arch:00000
  dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
  dhcp-vendorclass=UEFI,PXEClient:Arch:00007
  dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

  #Set the boot file name based on the matching tag from the vendor class (above)
  dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,...**
  dhcp-boot=net:UEFI,ipxe.efi/ipxe.efi,...**
  dhcp-boot=net:UEFI64,ipxe.efi,...**
  dhcp-boot=net:BIOS,undionly.kpxe,...**
  #PXE Menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
  pxe-prompt=“Booting FOG Client”, 1

  #The Known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,

  Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI This option is first and will be the default if there is no input from the user.

  pxe-service=X86PC, “Boot to FOG”, undionly.kpxe
  pxe-service=X86-64_EFI, “Boot to FOG UEFI”, ipxe.efi
  pxe-service=BC_EFI, “Boot to FOG UEFI PXE-BC”, ipxe.efi

  dhcp-range=...**,proxy

  The machine that I’m deploying Windows to is a Varipos 815s - the interface is labelled as: ‘IBA GE Slot 00C8 v1395’- I’ve having mixed success with these machines on exactly the same bios version, from the exact same ports. Some of them complete normally and the others display this error:

  “No network interfaces found, your kernel is most probably missing the correct driver! Please check your network setup and try again”

  It appears that one the kernel & init are loaded the interface just completely stops, along with the negotiation lights on the port. Does anyone have any suggestions to resolve this issue or point me in the right direction? TIA.

• Announcements

  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!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2.4k
  Topics
  18.5k
  Posts

  A

  @DBCountMan said in Secure LDAP authentication:

  Do I need to have a cert that is trusted by my domain’s root CA in the FOG’s root store?

  As far as I know, no.

  @DBCountMan said in Secure LDAP authentication:

  BTW the screenshot at the bottom of that thread you linked shows “Use LDAP SSL” but I do not have that option.

  The last screenshot is from the 1.6-alpha version of FOG Server.

  The screenshot in https://forums.fogproject.org/post/155590 is from the current stable 1.5.10.xxxx version and as you can see it uses 636 port.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2.3k
  Topics
  20.9k
  Posts

  N

  Hello,

  I’m running FOG 1.5.10 and have set up a global postdownload script at /images/postdownloadscripts/fog.postdownload. The script sends a Slack notification via webhook when a deploy finishes.

  The script is configured in the database (FOG_POST_DOWNLOAD_SCRIPT), and the file has correct executable permissions.

  However, the script is not being executed automatically after deploy, even though deploys complete successfully and show in the Active Tasks list.

  I have tried:

  Adding debug logs inside the script writing to /tmp/fog-post.log (only updates when running manually).

  Watching the PXE client console during deploy but don’t see any message about using the postdownload script.

  Confirming the global postdownload path is set correctly in the database.

  Verifying that no “Post Download Script” option exists per image in the web UI.

  What I need:

  Clear steps or checklist to verify why the postdownload script is not running automatically.

  How to confirm if the postdownload script is actually called by FOG after deploy.

  If there is any additional configuration required in FOG 1.5.10 to enable postdownload scripts.

  How to properly debug this issue (logs to check, commands to run).

  Any known issues or tips specific to FOG 1.5.10 regarding postdownload scripts.

  Thank you for your he