Finally, I did my update.

The problem was that I was running Debian Buster, so I first had to upgrade to Debian Bullseye so that the installer could install the new packages.

Then, I made a copy of the fogproject/ folder, deleted the folder to initiate a git clone
Next, I followed the tutorial and restarted the installer, which restored my old settings. The web interface is working, so I assume my clones will work as well.
Thank you.

@Hojjati I’ve found a solution for this issue that worked for me.
You need to manually edit the Windows hosts file at C:\Windows\System32\drivers\etc\hosts and add an entry with your FOG server’s IP address followed by the name “fogserver”.

This is necessary because SmartInstaller.exe performs a pinning process during installation, if you notice the installer hangs or fails exactly at that pinning stage, it is definitely due to this resolution issue.

Adding the entry ensures the installer recognizes the server and can download the certificate properly.

I’m going around replying to all these old Docker request threads so people can try out my work. Check out my thread here:

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

and provide feedback in the comments.

the actual github repo is here:

https://github.com/88fingerslukee/fog-docker

Finally found out why I couldn’t auth over 636, I needed to add my domain’s CA cert to the FOG server’s root cert store. Once I did that I can now use my AD creds over 636 on the web UI and iPXE menu items.

@george1421 Thanks, George.

@george1421 I see now and you’re right as my clients are all legacy boot/BIOS boot non UEFI and would not benefit from the client-arch examination.

I’ve already declarations set for each host in my dhcpd.conf file in terms if MAC to IP and so adding another field of filename “some boot loader file” won’t be impossible.

Thanks you for this exercise as I’ve learned some very important things here.

@george1421 Just seeing if anyone else has had issues.

Haven’t purchased the new models yet.

Was hoping to confirm they’re compatible with FOG first, so thought I’d reach out and ask around.

Thank you!

@alterak If you know how to program linux bash scripts this is possible. You will need to edit a script called fog.man.reg that is in FOS Linux (the OS that runs on the target computer to capture/deploy images). I have a tutorial on modifying that program to set a default hostname. But the concepts you need to do what you ware are listed here: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

@alterak said in FOG operation in different network segments:

is there a possibility of automatic separation of locations,

I’m not sure I fully understand the question, but if you are asking can it automatically pick which location to select based on the IP address of the computer being registered. The quick answer is no, FOG doesn’t currently have that capabilities.

The bit longer answer is it could if you can be a little creative and can do a little linux bash script programming. In a nutshell, you can customize the bash script that is setup for full registration of computers. The basics of what needs to be done is covered in this tutorial: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

The IP address bit can come from this script: https://forums.fogproject.org/post/69725 This post is for getting the IP address to be used in a FOG postdownload script. But the concept will be the same for the fog.man.reg script.

@ingemedia We just released new experimental kernel/initrd. I included the r8126 drivers. I don’t have any devices to test with so would you be willing to test it and let me know?

@george1421 thanks for continuing to provide such detailed information.

I believe the best way to learn is to do, so i am going to go shopping for an SSD (and perhaps some RAM to be safe). Once I have everything in place, I am going to do a test run on our machines as well as those of an associate just to see what happens when the network changes. Following this, I will check back with you if you don’t mind to go through the results.

Hi mwestaph,

I am also new here but I believe I can take a crack at your image.
Snapins I feel are great, they automatically install after your machine is imaged. The other tool you would want to consider here are the “Groups” feature. While this isn’t a traditional group where new hosts inherit group settings, its a good way to apply settings on mass.

Here is my basic setup:
I have 2 images and 6 groups. I then onboard all of the client machines / hosts and assign them to the appropriate group. In the group setup, I then choose the correct image and snapins for that group. This applies these settings to all associated hosts (ie. All current hosts that are associated with this groups now have the same settings.)
The only downside currently is if you need to assign a new host machine to this group, you need to re-apply the image and snapin settings for the group to apply it appropriately to this machine.

Let me know if this helps and if there is anyone more experienced out there feel free to tell me if I am wrong.

Do you think writing this in fog.man.reg after line

[[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n Args Passed: $*"

could do it :

host="" imageid="999" blDoAD="Y" realdoimage=$(echo -n 1 | base64) res="" user64=$(echo "fog" | tr -d '\012' | base64) pass64=$(echo "password" | tr -d '\012' | base64) while [[ $res != "#!ok" ]]; do echo -n " * Enter hostname for this computer: " read host if [[ ${#host} -gt 15 ]]; then host=${host:0:15} echo " | Truncated to 15 characters: $host" usleep 2000000 fi host=$(echo $host | base64) res=$(curl -Lks --data "host=$host" ${web}service/hostnameloop.php 2>/dev/null) [[ $res != "#!ok" ]] && echo "$res" done dots "Attempting to register host" res="" while [[ -z $res ]]; do res=$(curl -Lks --data "sysuuid=${sysuuid}&mac=$mac&advanced=$(echo -n 1 | base64)&host=$host&imageid=$imageid&doimage=$realdoimage&doad=$blDoAD&username=$user64&password=$pass64" ${web}service/auto.register.php 2>/dev/null) echo "$res" usleep 2000000 done . /bin/fog.inventory usleep 2000000