@george1421 noted. When I was initially testing, I did not know this and it took some digging in the forums to find this tidbit of knowledge. Given that having separate storage groups stops replication between the nodes in my mind it makes most sense to have a more distributed setup of normal servers at each site to handle all of my requirements. Thanks for the input!

I don’t have any recommendations for a fix but wanted to note that I have a site running: 1.5.10.1754 and quick registration is working as intended. So could be something else at play here besides the version.

Hello everyone,

In my environment we utilize the FOG service to push Snapins and perform Power Management tasks, which when manually enabled works flawlessly.

I have the following settings configured:

1. Within ‘FOG Configuration’ > ‘FOG Settings’ > ‘FOG Client -Snapins’ > CLIENT SNAPIN ENABLED is checked & Under ‘FOG Client - Power Management’ > CLIENT POWERMANAGEMENT ENABLED is checked.
2. Within ‘Service Configuration’ I have ‘Power Management’, ‘Task Reboot’, & ‘Snapins’ all set as ‘Enabled’ & ‘Enabled as Default’

However, if I go into any of my hosts it’s all disabled. I can manually change the settings for an individual host or group of hosts, and it will apply, I can then utilize them. But if I reboot the hosts all of the ‘Host Module Settings’ will return to be all unchecked.

I am currently running version: 1.5.10.1734

Anyone’s input would be greatly appreciated. At the end of the day things are all working properly, I just need to manually enable the service settings every time I want to perform an action which I don’t believe is intended (correct me if I’m wrong).

Thanks in advance!

@george1421 noted. When I was initially testing, I did not know this and it took some digging in the forums to find this tidbit of knowledge. Given that having separate storage groups stops replication between the nodes in my mind it makes most sense to have a more distributed setup of normal servers at each site to handle all of my requirements. Thanks for the input!

@george1421 thanks for the detailed response! We are frequently re-imaging lab rooms. The subnet group plugin is vital as when a device moves rooms to a separate subnet, when it ‘checks-in’ to FOG after it is powered on and PXE boots in the new location it will be re-assigned to the proper group associated with the IP range. That subnet group will be used to group all the lab computers in the desired room and thus used to multicast the room.

The issue lies when I have a storage node setup at a new location and acting as the PXE/TFTP server, the client will not ‘check-in’ with the main FOG server and run the plugin hooks until it finishes imaging and the client takes care of it which does not work in my desired process.

At this point I am leaning towards a standalone server for each site just to support the functionality required.

To follow up on this I am looking for any community input on the following:

If anyone has a multi-site setup where they are reliant on the Subnet Group plugin did you:

1. Edit the init.xz file to check in with the master server, if so, I’m curious how
2. Setup each site node as a normal server with your full configuration
3. Another option that I have not thought of

Anyone’s input would be greatly appreciated.

Hello everyone,

I have an interesting issue I am facing. I am testing having a storage node at another physical site. The connection seems fine as it can reach the FOG server but one thing I am facing is I am heavily reliant on the Subnet Groups plugin, specifically for identifying what IP a client is upon booting into FOG and assigning to the associated group.

What I am finding is that when a client boots at the sub-site it will get the boot files from the storage node and get into the ‘DEVICE IS REGISTERED’ screen but the plugin hook never fires thus thwarting my desired process.

My desired process is when computers are setup in a lab: Booted > Check-in with FOG > Subnet Group assigns computers to proper group > boot loop until all devices are in group > assign an image and task > machines are images. I have this working at the main site.

Is my best option to have a separate full FOG setup at each site?

Appreciate anyone’s input!

FOG version: 1.5.10.1733
Server OS: Ubuntu 24.04

@lmoysidis I’m not using fortigate but check out the following article: https://docs.fogproject.org/en/latest/installation/network-setup/proxy-dhcp/?h=
I needed to dynamically assign a boot file based on vendor class and dnsmasq did the trick!

I reverted back to a snapshot I had on the same version and it’s working as expected. Unsure how things got corrupted but I would say it’s safe to assume this is working unless others report the same issue.

LOG Viewer is empty in the GUI. I can however access the logs via the server.

FOG Version: 1.5.10.1733

In the web developer console, I see the following:

fog.about.logviewer.js?ver=141:42  Uncaught TypeError: Cannot read properties of null (reading 'split')
    at LogGetData (fog.about.logviewer.js?ver=141:42:25)
    at fog.about.logviewer.js?ver=141:11:5
    at fog.about.logviewer.js?ver=141:32:3

Seems similar to a previous issue.

@Tom-Elliott latest pull resolved the issue. Appreciate your help on this!