Topics created by alexamore90

@alexamore90 said in Snapin question:

@Tom-Elliott
yes sure, I would be interested in running a batch file after the fog has restarted because the deployment on the client has finished. I think I can’t use the snapin because of the host registration that we don’t do. but is the postinit done with fog?

You still haven’t answered the question.

I already stated that postinit scripts run in FOS (fog adjacent if you will) but you haven’t answered the question of “where or when” you’re expecting the script to run.

Please provide details of what you’re doing, when you’re expecting things to happen (explicitly as possible) and we can try to give guidance and direction.

Otherwise we’re talking in circles.

@alexamore90 There is a test function in fog, yes.

But it’s not a “passthrough test” that I think you’re imagining.

It’s literally there as a task to test the disk, as some times a disk can show no issues, but have a bad sector or the head cannot move to that position. With some things testdisk is extremely helpful, but there’s not a “combined effort” of testdisk, currently, that would provide that functionality and I would not suggest it being used unless you know the drives are spinners.

In the case of SSD disks, there’s no real moving parts, and while it might have a test mechanism on its own, this task type should not be used for them.

@AlleneBrick @alexamore90
Lets clarify further first.

What DHCP server are you using and what is its ip?
What do you want the fog server ip to be?

@Tom-Elliott ok how do I set it to 192.168.11.1?

@alexamore90 Did the installer finish all the way to the end? When running it there is a point where you need to open the browser and let it populate the database. If you skip this the installer will fail and needs to be run again.

The node offline sounds like the installer didn’t finish properly.

@george1421 If I give you access to any desk on a PC that reaches the 2 servers, would you be able to understand if there is something wrong?

@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.

@alexamore90 Definitely look into using multicast if you want to image many in little time!!

@alexamore90 said in Post download install script:

it start ms-settings:activation

I don’t know that command. I have not used it before.

I;ve used the command line scripts

cscript //nologo c:\windows\system32\slmgr.vbs /ipk <activation_key> cscript //nologo c:\windows\system32\slmgr.vbs /ato

The setupcomplete.cmd will only run if you use sysprep. Do you sysprep your images before you capture with FOG?

@alexamore90 said in Specification pc before deploy:

in which folder should it be replaced

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.

cd /root/fogproject git pull git checkout dev-branch git pull cd bin ./installfog.sh

The git checkout dev-branch command is what changes the installer to use the 1.5.9.115 (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 1.5.9.115 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?

@alexamore90 Douple posting in different languages is not going to help. Please stick to one topic: https://forums.fogproject.org/topic/16140/slow-server-fog

@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?