@Fog_Newb probaly just typoed it and i went with it too lol.

@RAThomas If the value is empty it shoudl think it’s false, and since it seemed to be random that’s where I got confused. But I’m glad this is working for you.

Thank you!

@diogo-seabra As for the picture, I think we need to clearly define your network.

dnsmasq works by using broadcast messages. So that means dnsmasq will only work on the local subnet. If your pxe booting computers are on a different subnet then you will need to add the fog server’s IP address to the list in the dhcp relay service on your router.

Also if you have dhcp snooping enabled on your network switches, that may also cause dnsmasq to not respond properly.

@Tom-Elliott Hi Tom, Thanks… I updated to 1.5.10.1692 and was able to deploy a 2 day old image to the PC. I updated some things on the PC, mostly with Steam and display settings then went to capture an image from it again and ran into the same problem mention in the OP. Only this time, I was able to take a pic.

I ran chkdsk prior to capturing and it came up clean

alt text

UPDATE: So I tried everything for the ntfsresize error … turns out, I had to shrink the partition in windows a bit then expand it. After that, I could capture.

@plegrand @plegrand I have not tested everything but it seems to be working fine with Trixie. As mentioned, there were some minor challenges but with the help of @Tom-Elliott posts and posts from others, I got it upgraded. I did a full inventory on a new computer and that worked. I deployed one image and that seemed to work.

php -v
PHP 8.4.11 (cli) (built: Aug 3 2025 07:32:21) (NTS)
Copyright © The PHP Group
Built by Debian
Zend Engine v4.4.11, Copyright © Zend Technologies
with Zend OPcache v8.4.11, Copyright ©, by Zend Technologies

cat /etc/debian_version
13.0

@george1421 No luck, could you please have a remote session at your convenient time?

@BrightPipe said in FOG not saving images in the directory:

EDIT---- Running the installer again seems to have fixed the issue. Thanks.

Good deal because that was going to me my next request. I’m glad you have it sorted out.

I have done this before on a Cisco switch but it’s been a while. Thought I share my notes on what commands are needed

# Vlan131 (fog server vlan) ip helper-address 192.168.158.255 # Vlan158 (fog client on a different vlan) ip directed-broadcast 101 # ip access-list extended 101 access-list 101 permit udp host 192.168.131.149 any eq 9 * NOTE in the ACL above 192.168.131.149 is the fog server ip address # forward udp ip forward protocol udp 9 (it might say discard) # On the switch the two vlans look something like this interface Vlan131 description fog server vlan ip address 192.168.131.1 255.255.255.0 ip helper-address 192.168.131.3 (my dhcp & dns server) ip helper-address 192.168.158.255 (fog client subnet broadcast address) end interface Vlan158 description fog client vlan ip address 192.168.158.1 255.255.255.0 ip directed-broadcast 101 (extended ACL) end

Hope it helps

@rodluz
Thanks for the feedback. I swapped the RAM module and NUC was able to re-image. Case closed.

@george1421 Thanks for your help.

I solve the problem with this AutoUnatted.xml

<?xml version=“1.0” encoding=“utf-8”?>
<unattend xmlns=“urn:schemas-microsoft-com:unattend”>
<!-- Bypass OOBE -->
<settings pass=“oobeSystem”>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
<NetworkLocation>Other</NetworkLocation>
</OOBE>
</component>
<component name=“Microsoft-Windows-International-Core” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<SystemLocale>pt-PT</SystemLocale>
<UILanguage>pt-PT</UILanguage>
<UserLocale>pt-PT</UserLocale>
<InputLocale>0816:00000816</InputLocale>
</component>
</settings>

<!-- Run SetupComplete.cmd via PostOOBE --> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>reg add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\FirstBoot\PostOobe" /v "00" /t REG_SZ /d "cmd /c C:\Windows\Setup\Scripts\SetupComplete.cmd &amp; exit /b 0" /f</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings>

</unattend>

The AutoUnatted.xml will call the the script C:\Windows\Setup\Scripts\SetupComplete.cmd

I make the sysprep with AutoUnatted.xml

@chunter2 This domain does not exist or dcouldn’t be contacted seems to be indicative of the problem. Simply put, from the message you show, it seems the DNS isnt’ able to reach the domain controller.

I highly doubt this is due to the version of FOG based on this, but my perspective is obviously very limited at this point.

@ProfessorFow There is the ability to replicate images across groups. You can set which “groups” images need to replate to by associating images to multiple storage groups. You can even define which storage group is the primary.

@george1421 So removing my key from the unattend file fixed the SetupComplete.cmd running issue. I forgot to tell it to join the domain after deploy and made a snap in for that which worked to test it out (I could tell the service was running because it rebooted to change its name as well but wanted to verify with the snap in). Windows must have activated based on something in the hardware because the machine is activated as well, so the key didn’t really need to be there I guess(?)

Also thanks for all your help, several years ago under another username you helped me a lot with random issues on another fog set up. The whole FOG project team is amazing!

@JJ-Fullmer Dear Fullmer, thanks in advance for your intervention.

Unfortunatly in the machine that run my fog container there is another mysql database listen on port 3306.
This is not a problem, i just semi-resolved creating a non-privileged/shared network host mysql container with no exposed port -> place fog container and this database container in a same network (they can ping each other with fqdn) and i’ve just modified the /opt/fog/.fogsettings with your suggestion in the past, but the solution doesnt work:
The installation goes fine, but the result is a blank http page that it say: database error. (something like that).
I think (but is only supposition, im not absolutly a developer) that there is written php scripts that must to be point to a localhost database (something in /var/www/html/fog/*).

This problem is born because the fog container must be in privileged mode, with the same network namespace as the host, and in this host there is another database already.

Thanks for confirm me the inevitable death of the container version of fog. it really hard to containerize this application without setting privileged mode and/or share the host network. and the huge problem of systemd processes make this containerizzation very difficulty to maintain.

Thanks for the patience

Thank you for your detailed reply, @george1421

I have decided to run both servers on the same network. With DHCP switched off on AikenWorkbench, I’m able to boot intoFOG menu.

Your entries aren’t quite right, or I’m doing something wrong. If I use it as is, I’m getting something like "Could not boot: Not found (https://ipxe.org2d12618e)

I have decided to exclude some of the commands and narrowed it down to:

chain -ar tftp://192.168.2.1/grub/bootx64.efi boot || goto MENU

And I’m trying to run it on EFI EFI-capable machine, but I’m only getting to the grub console and no further.

I understand my best bet is to learn how iPXE works and study its documentation.

There is more config from Aken if this helps:

cat /etc/default/tftpd-hpa TFTP_USERNAME="tftp" TFTP_DIRECTORY="/awbcboot" TFTP_ADDRESS="192.168.2.1:69" TFTP_OPTIONS="--secure" ls /awbcboot bios biso boot grub ls /awbcboot/grub biso boot bootx32.efi bootx64.efi grub.cfg grub.cfg.bak snap unicode.pf2

And grub.cfg

cat grub.cfg set default="0" set timeout=0 menuentry 'Aiken Workbench V2 UEFI ...' --class gnu-linux --class gnu --class os { linux (pxe)/boot/vmlinuz-awc root=/dev/nfs nfsroot=${pxe_default_server}:/awbclient ip=dhcp rw libata.allow_tpm=1 -- initrd (pxe)/boot/initrd.img-awc

And here is the whole dhcp.conf but we don’t use Apple class as they dropped PXE support.

ddns-update-style none; authoritative; allow booting; allow bootp; option domain-name-servers 208.67.222.222; option arch code 93 = unsigned integer 16; class "AppleNBI-i386" { 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 = 1) { option vendor-class-identifier "AAPLBSDPC/i386"; option vendor-encapsulated-options 08:04:81:00:00:67; } if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring (option vendor-encapsulated-options, 0, 6) = 01:01:01:02:02:01) { option dhcp-parameter-request-list 60, 43; option vendor-encapsulated-options 01:01:01:03:04:C0:A8:02:01:04:02:80:00:07:04:81:00:00:89:09:2A:81:00:00:89:09:44:6f:45:2d:49:6d:61:67:65; } } if (substring (option vendor-class-identifier, 15, 7) = "iMac4,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 7) = "iMac4,2") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 7) = "iMac5,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 7) = "iMac5,2") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 7) = "iMac6,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 10) = "MacBook1,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 10) = "MacBook2,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 13) = "MacBookPro1,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 13) = "MacBookPro1,2") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 13) = "MacBookPro2,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 13) = "MacBookPro2,2") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 13) = "MacBookAir1,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 10) = "Macmini1,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 9) = "MacPro1,1") { filename "grub/bootx32.efi"; }elsif (substring (option vendor-class-identifier, 15, 9) = "Xserve1,1") { filename "grub/bootx32.efi"; }else { filename "grub/bootx64.efi"; } } class "pxeclients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; next-server 192.168.2.1; if (option arch = 00:00) { filename "bios/pxelinux.0"; }elsif (option arch = 00:06) { filename "grub/bootx32.efi"; }elsif (option arch = 00:07) { filename "grub/bootx64.efi"; } } subnet 192.168.2.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.2.10 192.168.2.254; next-server 192.168.2.1; option subnet-mask 255.255.255.0; option broadcast-address 192.168.2.255; option routers 192.168.2.1; default-lease-time 600; max-lease-time 3600; }

@janez3k said in Fog iPXE Menu no input:

https://pastebin.com/xWhJkDX1

Thank you for this, I have copied and pasted what you have. The only part i noticed (though I left it for now) is the missing building of ncm--ecm-axge

I don’t know that this file is particularly in use so I think it’s safe to keep out but If I’m wrong I’m sure we’ll learn about it quickly enough.

I have pushed this version of the IPXE building script to both working-1.6 and dev-branch.

This won’t become part of the release until the 15th of September (at this point), but is available for testing on the bleeding-edge/beta channels.

Dear Tom,

Thanks, and this is what I figured. At least I can pxe boot it and capture the image now, if I switch it to “AHCI/NVMe” mode, and switch back to “RAID” mode to boot the single NVMe drive.

I made this known so we can reach out to Dell and possibly have this changed as it actually doesn’t need this “RAID” mode.

Also we still have to disable secure boot on any computer either HP or Dell to get the pxe boot to work.

We did manage to use FOG to capture a RAID from an HPE DL380 Proliant Gen10 RAID controller and use that to load Windows Server 2022 now, so it does seem the kernel is the issue here on this intel motherboard RAID.

Regards,

Matt

@george1421

thank you for your great answer. You are completely right, it is a 17-x104ng, not a fg. It was an error of me 🙂

The needed hardware id is VEN_10EC&DEV_8136

Hope that helps

Thx,
mchristo

Thanks @george1421,
I haven’t setup Fog yet so was looking for a step by step guide to getting it installed and configured.

@Tom-Elliott sounds good!