@george1421 @Sebastian-Roth Thanks for the replies. I decided to take another route using the iPXE command chain.

Currently I am using chain to point menu items to the pxe boot files residing on another server. I know that this isn’t what FOG is made for, but it’s working for me and that’s all I can ask for.

I have been following this thread from a while back (https://forums.fogproject.org/topic/14521/ipxe-menu-and-image-storage) in junction with post about using FOG to pxe boot into installer images. (https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images)

Hello,

Does anyone know if it is possible to create a iPXE Menu Option on the FOG Server to service all network booted machines to another PXE server on the same subnet?

I have an old PXE server that is already configured and that has it’s own images / kickstart files. I don’t really want to give up on this server after moving into the FOG environment. This old PXE server is still in the same subnet, I have just changed the “next-server” address to point to our FOG server in DHCP.

Ultimately I want to have a menu option in the iPXE Menu that “forwards” the client of an unregistered FOG host to this server and have them boot from there. I was interested if anyone has done something like this before.

Maybe all the work is just on the DHCP server by forwarding specific MAC addresses to my old PXE server.

Let me know if you have anything in mind or any questions.

@sebastian-roth

Thanks again. To answer your question, I am using:

Fog Server

• v1.5.9

• CentOS_8

Fog-Client

• 0.12.0

• CentOS_7

The Snapin seems to be working after I reinstalled the fog-client service. I uninstalled SmartInstaller.exe with mono and deleted the profile of the host on the WEB GUI then followed the same installation process on the Wiki.

Using the bash example you gave I can create files into the /tmp/ directory on the client so that proves to me that the Snapin is working. Feeling extra dumb right now. Thanks again for your time.

@sebastian-roth Thanks for the reply. And yeah my bad, I realized this after posting.
Do you know of a way that I get a more detailed log of what is happening? I’m just trying to see where the execution is getting hung up.

Looking at /opt/fog-service/fog.log,

Found that the client started and finished the snapin then gave back return code =1. Which seems like it should have worked.

Tried running another task to create a file. ( touch test.txt ) Log gave the same result but I see no file.

First time running FOG and everything has been working really well, but I am having some trouble getting my Snapins to work on a CentOS 7 client.

I have registered this machine with the FOG server during boot and installed FogClient with the SmartInstaller using mono.

Every guide that I can find on the wiki / the forums is for how to run your Snapins on Windows. Since I see bash scripts are an option on the Web GUI I assume it is currently supported?

Using “Create New Snapin” from the Web and adding a file to just ping the host server for 30 seconds I have successfully made a Snapin. ( As a sanity check, yes I already tested that they are networked and can ping eachother ). I saved this file, and created a task to run this on the client machine immediately. However I am not seeing any incoming packets after I run the task and there is no new process on the client computer. I also tried to install an offline package and had no luck.

I can do everything else that uses the FogClient on this machine, just not use Snapins.

Does anyone know what could be going on or have any working example? Not really sure how this process is supposed to work.