@DBCountMan Yes if you are using the location plugin. Using the location plugin you assign the storage node to a location and then when you register the target computer with FOG you assign the target computer to a location. Then when the computer pxe boots it learns who it needs to communicate with. So a storage node would work in this case to spread the load.
One caveat with storage nodes is that they can’t capture images. Only the master node can capture images. Then all storage nodes (including the master node) in the same storage group can deploy the image.
The answer is difficult to explain in just a few words.
The fog.download file is actually in the FOS Linux image that gets transferred to the target computer before imaging begins.
The fog developers provided two call out functions where the fog admin can do things before imaging starts and just after imaging stops but before the target computer reboots. You will use the first call out that the developers give you called a post init script. This call out script is called just after FOS Linux (the OS that runs on the target computer boots). My idea is to use this first call out to copy the patched fog.download script from the fog server to FOS linux, then when imaging starts it will use your patched file with the data you need to see. I would place the file to copy in the same directory as where the post init scripts are called from.
NOW Sebastian mentioned an easier way to go about this without patching the fog.download file. In that you will again use the post init script call out script to simply print the info you need then pause waiting for a key press before continuing. There is nothing to patch, you will simply create a bash script in the post init directory and then call it from the post init callout script.
Thinking outside the box, actually you have the power of php engine on the fog server. If one stretches their imagination a bit, this same script that displays your information on the screen, you should use php mail and send the contents of the fields in an email to you. This is a little harder to setup, but its not that hard to do.
@alexamore90 Updating FOG is a normal process of fog administration. I agree its been quite a while since the last update but the process is the same. FOG 1.5.10 should be released soon, but until then the FOG developers are suggesting that people upgrade to a pre release but stable version of the development release.
When you installed fog if you use the git method to download the installer files then upgrading is easy and you will not lose any configuration settings. To do the upgrade its pretty easy, to perform a dev-branch upgrade there is one more step.
In your case if you are on FOG version 1.5.9 and you use the git method you would simply change to the base of the install directory (typically in /root/fogproject) and issue these commands on the fog server.
git checkout dev-branch
The git checkout dev-branch command is what changes the installer to use the 184.108.40.206 (or later code base). When 1.5.10 is released you would simply replace that line with to go to the master code base with git checkout master and issue the same commands.
The installer installfog.sh will look at all of the answers you provided when fog was installed and use them during the reinstall.
After you update to the 220.127.116.11 dev release you will need to once again update the FOS Linux kernel to 5.15.x series (FOG WebUI->FOG Configuraiton->Kernel update, as well as recompile the latest version of iPXE using this tutorial https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe when you complete these after steps you will be at a level that FOG 1.5.10 will be when its released. The above install process will make sure your FOG install will support the newest hardware released by the hardware manufacturers.
You say that you have 3 FOG servers you really should update them all to be on the same release or you won’t have the fix for the non-movable recovery partition that Microsoft created.
@alexamore90 Sorry I don’t use that application. If you are more comfortable to post in your native language you may do that. We try to keep the posts in english, but find sometimes we get better detail when the poster uses their native language and we translate. I will only post in english through.
If you have a basic drawing of your setup that might help too, Remember we have to imagine your configuration based on the words you use.
One additional question I should have asked, is your current configuration for a home lab or a business?
@george1421 The exsi is installed on a host server directly on the HDD, inside there are 3 fog virtual machines that I need to deploy windows on various clients.
since I have another host (server) I would like to use it as a backup, but how can I make a backup on the host I have now and restore it on the new one without reconfiguring all over again?