@bkgoodman This can be set from the fog web ui. FOG has a concept of storage nodes and master nodes. Only master nodes can collect images, you can deploy images from both master nodes and storage nodes. Where storage nodes are deploy only.

While the following deals with synology nas devices the same info can reference other NFS aware devices. Your target system needs both nfs AND ftp enabled to be able to function as a FOG storage node.

https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

@altitudehack This was a spam attempt that was missed. I’m working on clearing it out, and apologize

@Tom-Elliott
No, the node points to the master configurations.
installtype=‘S’
snmysqluser=‘fogstorage’
snmysqlpass=‘password’
snmysqlhost=‘ip_master’

using the fogproject/bin/installfog.sh

Checking if this node is registered…Done

Node being registered…Done

Ensuring node username and passwords match…Done

Setup complete

You still need to setup this node in the fog management
| portal. You will need the username and password listed
| below.

Management Server URL:
http://fog.test.test/fog/

You will need this, write this down!
IP Address: 172.17.0.2
Interface: eth0
Management Username: fogproject
Management Password: password

I redid the installation using the fogproject/bin/installfog.sh script and everything went well. I deleted the storage node from the master and ran the commands below again, it returned success but the storage node was not added to the master.

source /fogproject/lib/common/functions.sh
source /opt/fog/.fogsettings
registerStorageNode

To enter bios of the VM, use F2 key on boot, then you can disable secure boot

@george1421 Cool! After reinstalling FOG, ipxe.efi has file sizes now so the ASUS PC can PXE boot with ipxe.efi. Thank you very much!

@PCF24 Here is a quick and dirty script to reset all your hosts.
I tested it with two hosts and it is working for me. I don’t want to reset all my hosts.

You will have to paste your FOG server IP, FOG user api token, and FOG settings api token to the script.
You will also need to install jq in your FOG server.
Debian base: sudo apt install jq. RHEL based: sudo dnf install jq

#!/bin/bash server_ip="http://10.10.10.10" fog_user_token="PASTE_YOUR_USER_API_TOKEN_HERE" fog_api_token="PASTE_YOUR_FOG_SETTINGS_API_TOKEN_HERE" all_hosts=$(curl -S -s -X GET -H 'content-type: application/json' -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" $server_ip/fog/host/ | jq '.hosts[]') all_ids=$(echo "$all_hosts" | jq '.id') all_ids=${all_ids//\"/} for host_id in $all_ids do curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"pub_key":""}' $server_ip/fog/host/$host_id/edit curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_tok":""}' $server_ip/fog/host/$host_id/edit curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_time":"0000-00-00 00:00:00"}' $server_ip/fog/host/$host_id/edit done

@george1421 Thank you for your quick reply.
I am currently trying to get the multicast cloning to work over several vlans as in your instructions.
I am using OPNsense instead of Pfsense. Unicast works without problems, but we have many of the same PCs and so multicast would make sense.
Part 2.7 would be relevant to check that I have not forgotten any ports.
Part 3.1 and 3.2 as I have never worked with an IGMP proxy.
During a short test, everyone stopped before cloning and waited. Would assume it was because of my wrong IGMP configuration as I didn’t see any blocked ports on the firewall.

@Tom-Elliott
Thanks, for all the input.
I’ll see if i can find some sensible solution for my setup.

@Tom-Elliott Is there a way to check the synchronization status of the storage nodes with the master node on the webpage?

@Sebastian-Roth Thanks. Worked like a charm. Went from ~250Gb image down to ~9Gb.

@Eliza In the FOG web user interface. In the FOG menu FOG Configuration and then along the left menu Select Kernel update.

@introloud said in Configure FOG Server's DHCP service?:

I’m gonna try both unicast and multicast to a couple of machines first but I doubt that it’d be any different since it’s on a simple network right now.

This is simple and complex to explain. But a unicast image is sending an image form the fog server to a single target computer. Lets say for example that take 50MB/s of network bandwidth. If you start up a second unicast deployment to a second target computer that will take another 50MB/s of network bandwidth. Now lets add a third simultaneous unicast deployment, Now you are sitting at 150MB/s of network bandwidth usage and 1GbE only has 125MB of available bandwidth, so you will get collisions and throughput slowdowns.

Now lets say you setup a multicast session with those 3 same computers. The image is now being sent out as a multicast. You can have as many receivers as you want, because only one image is being sent out you only consume 50MB/s of network bandwidth. If a receiver is late to the stream, they simply miss the stream and will not be imaged during that streaming session. Using a multicast streaming method you can image 30 computers in about the time it take to image 2 computers using unicasting.

They will be in the same VLAN but probably may have different subnet masks

Strictly speaking you would normally have only one subnet mask per VLAN unless you are doing supernetting for some reason.

imaging task to multiple machines, and have them reboot to get into network boot

Typically you would configure the computers to boot through PXE then boot to the hard drive. That way if FOG had any actions for the computer it could do it while the fog menu is displayed. If there were no jobs then it would just boot the hard drive. You would have the FOG client installed on the target computer so when the schedule task starts the target computer would be instructed to reboot via the fog client program.

Hello,
You can also have a look at this topic :
https://forums.fogproject.org/topic/16876/dual-boot-grub-issue-after-deploying?_=1696487644593

@jptechnical If the laptop is in uefi mode there is a way to boot from a usb drive: https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way

There are other options but try the easy way first.

@george1421 @Tom-Elliott
Luckily I could schedule a meeting with my System-Admin today, and he tried turning off the serving of the WDS boot file - seems in the configuration of option 66 and 67 of our companies DHCP server was an old Windows Server that served a meaningless WDS file, we changed it to my FOG Server and the issue is now solved.

I am very thankful for your first-class support and I apologize for the inconvenience! You guys are my heroes!