@Tom-Elliott I was able to post it just now, so whatever you did seems to have worked!

Thanks!

@theyikes Why do you need to reset it to the original installation state repeatedly?
How to do that is in the wiki here https://wiki.fogproject.org/wiki/index.php/Uninstall_FOG (that doc isn’t yet migrated to the new docs site)

I’m not sure why you’re wanting to start the server side fresh though.

The general idea is

Create Fog Server on a linux vm/machine that has enough storage for the OS images (not isos, captures of install states) Setup a different VM with the OS as ‘golden image’ (With windows you need to utilize sysprep) Register that VM as a host in FOG and capture the image. Deploy the image to as many other hosts as you desire

See also :

https://docs.fogproject.org/en/latest/capture-an-image
https://docs.fogproject.org/en/latest/deploy-an-image
https://docs.fogproject.org/en/latest/intro

@Tom-Elliott Thank you for the response. That answers the question. I’ll consider the proposed workaround. I’m going to look into other options, such as keeping FOG on an isolated network, and the practicality of those options.

@yannickF I’m working on using SSH vs FTP for file transfers and deletions as it’s more “natual” in today’s security conscious world.

If you’re able to allow SSH to the remote ends, this may help out with things.

I’ll have to change the text on these fields to remove “FTP” as the main parameter.

As, and this is very much just a guess, the Error is showing specifically teh SFTP subsystem is failing, I am guessing the remote side is not setup (properly) for SFTP, and is instead using the default sshd_config file.

I say this because there’s checks letting you know if you can connect, and if the sftp fails. Since connect has to happen first, that message tells me the configuration on the remote machine needs a minor update.

If you have admin access to that remote node (as well any node you need this to connect to)

Please open the relative machine’s /etc/ssh/sshd_config

Look for the line:
Subsystem sftp /usr/libexec/openssh/sftp-server

Replace it with:
Subsystem sftp internal-sftp

Restart sshd service:
sudo systemctl restart sshd.service

This should fix that particular error message.

@jenesis I’m going to say that since this is a hardware security device its not possible to pxe boot it. I can see the device manufacturer using the hardware security key as part of its integrity control to ensure its OS hasn’t been tampered with.

But I would not rely on my guess alone. I would contact the company’s support team and ask if the software can be pxe booted. If yes, then we can probably get it to boot via iPXE. You also want to ensure you are not in violation of the manufacturers EULA by pxe booting something you shouldn’t.

@pilipp_edv said in general questions about storage / master storage nodes:

After that, I configured the windows DHCP servers in the other locations to point to the main FOG server.

FWIW: You can (should) point the remote dhcp server to the remote storage node so the clients doesn’t need to transfer the ipxe boot image across your wan. The storage node will instruct the clients to “check in” with the fog master node.

The part you are missing is the FOG server plugin “Location”. With the location plugin you first identify your different locations. Then assign storage nodes to the “location” then assign existing client computers to the location. As you full register new clients there will be an added prompt for location during registration. This plugin pulls all of the bits together to make the clients find the proper storage node.

@george1421

The problem was the IGMP Snooping as you suspected. Thank you for your help.

@aviel1540 Not sure I understand the question entirely.

You deploy image to machine After machine deploys, create a capture task for the machine When machine boots, it does an upload of it’s image. Once uploaded, then it boots to the OS?

You can just tell the machine to shutdown after the tasks are complete, so that you don’t have to wait 5 seconds. Sure you would have to physically generate the capture task, but this way would prevent the system from booting to the Newly deployed image.

@cornycopia After thinking about it, there’s a “general” port that’s used.

FOG Settings -> FOG_FTP_PORT

Granted this isn’t per server, but it is a choosable thing.

@youzersef I was remote to the physical host, but it seemed more like a blue screen in comparison to just “hanging”.

Anyways, I reinstalled FOG and cloned “stable” instead of “master” and got around that issue.

I’m going to make another post for another issue I’m facing with UEFI (would have updated sooner, but forms have been down).

@zeltron80 So what would this look like ? I just simply want another server option in the menu. Is it using your ‘exit’ => ‘exit’ to ‘exit’ => ‘chain tftp://xxx.xxx.xxx.xxx/menu.ipxe’ ?

@youzersef finally solved was a very simple think in the end of the installation I was pressing enter and after that I was opening the link that was a reason why was not working omg 😅
Now to work it’s work but it’s going slow to capture the image how I can get more faster ?

Re: AlmaLinux 8.9 NetInstall or ISO

I ended up piggy backing the ipxe setup from fogproject and loading netboot.xyz which is doing the trick.

Thank you.

@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