@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

@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.

@gaptoothgonni So while this can be done, FOG is designed to capture an image from where windows is already installed and sysprep’d, not to boot to a wim. Of course it can be done, but I just wanted to make sure that’s clarified.

All that said, doing it that way may or may not get past your problem, because it may just be a client pc bios setting.
If you manually boot to that iso on a usb on that pc, does it see the disks?
That message generally means it’s missing the storage driver.
Does the host you’re trying to deploy to have VMD/RAID enabled in the bios settings?
It is possible, and not even that hard if you’re already customizing the iso, to add the storage driver to the wim. I’ve never used NTLite, but in powershell you can mount the wim of the image with Mount-WindowsImage and use Add-WindowsDriver to add the inf you need to that image. You probably need to mount the boot.wim and setup.wim images and add it there too as you’re booting to the boot.wim and using winpe. This page might also be helpful https://learn.microsoft.com/en-us/windows/deployment/update/media-dynamic-update#update-windows-installation-media

I would also say, if you’re going this route, to consider making a autounattend.xml if NTLite doesn’t do that, as it can automate the install of windows and then have it kick things off into provisioning. We customize an iso like this and use it to create and capture our base image in FOG.

I got a little off topic there, TL;DR
Make sure the disks are seen if you boot to the iso manually, if they are not, then adjust the bios/uefi settings to use AHCI mode for disks as it works universally. If the disks are seen when manually booting, then something else is causing it not to see the local hardware.

@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

@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.

@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.

You might start by verifying the actual stored image name on the storage node at 10.149.50.21:/images

Next you might use some SQL tool (I use phpMyAdmin) to check the ‘fog’ database on your FOG server, table ‘images’ and verify that the values for ‘imageName’ and ‘imagePath’ both look correct.

‘imageName’ could be different from ‘imagePath’, but only if someone has renamed the image in the FOG server web GUI. ‘imagePath’ should be the same as the desired image directory in your storage node(s) /images directory.

@Selanty
I have the same problem, fresh installed Fog on Debain 12, PHP 8.2.29, Fog 1.5.10.1667.
Fog-Server is running on the same switch as the 2 Clients in one VLAN 2765. For that VLAN ip igmp is enabled.
“sh ip igmp” on that aruba switch shows:
-IGMP version : 2
-Querier Address : 10.73.65.21 (vlan-address of a second switch witch plays as querier)
-the querier ist running igmp v2

“service FOGMulticastManager status” result is:
PHP Fatal error: Uncaught Error: Non-static method FOGService::outall() cannot be called statically in /opt/fog/service/FOGMulticastManager/FOG>

unicast to that 2 clients is running.

Hi, just wondering if you were able to find a fix for this. Right now I’m experiencing a similiar issue when in the ipxe menu for Fog. No keyboard input works.

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

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

I’ve gotten a very similar set up to what you want and have tried working.

You’ll need to either rebuild the FOG version of iPXE with the shim command enabled or use a stock version of iPXE with the default.ipxe script replaced with an autoexec.ipxe script (I haven’t tested this so you mileage may vary). Once you’ve done that you can just sign your iPXE binary with your sec boot key, and save it as grubx64.efi (or see this Shim Issue or this part of the foguefi install script if you use Dell PCs.)

Finally now when you netboot, provided you also have mokmanager (mmx64.efi) in the same folder, you’ll be prompted to install your secboot key and on next boot you’ll be able to boot. iPXE with secure boot on. You will also need to sign you bzImage etc and then modify your default.ipxe script to load the shim with the shim command, and then you’ll be able to boot into fog fully!

If anyone wants I can put together a more coherent guide and I’m happy to answer any questions you have on this.

Tom
I still get this error when I try to Create a New Image:
This page isn’t working
10.149.50.21 is currently unable to handle this request.
HTTP ERROR 500

Web searches says this is a server provider issue. Is there something in Fog Project that can be checked for me?

Hi @Tom-Elliott,

Currently both nodes are in the same storage group as I want to replicate images and snapins from the Master to the Normal storage Node. I read through some documentation and it seems this should still happen if they are in different storage groups. Is this true?

If so, I believe this second issue should be fixed.

@uzee FOG doesn’t change or really step into the target system during deployment. You CAN do this if you write a post install script that will get called once the target image is deployed to the target computer. In the case of a linux computer you could potentially set the target computer’s name here by updating the /etc/hostname file or anything else you can do with a bash script. The FOG Client can also be configured to make changes to the target computer or install applications based on instructions from the fog server. Its really identifying what you want to do and how much automation you want to script. Its all possible with FOG and a little creativity on your end. Since you already know Ubuntu (linux) bending FOG to what you want will be easier than coming strictly from a MS Windows background.