My FOG server has two nics. eno1 and eno2. eno1 is bound to my standard workplace LAN and eno2 is set for DHCP and tftp for imaging and that network is physically isolated. The WebUI is accessible via both interfaces. I found a bug where if i log into the UI from the eno1 network, the storage node says its offline node unavailable, and if i click on it, it takes me to another page that says “Invalid Server Information!” The storage node is configured with the ip that is bound to eno2. i have a workstation set up for management on the same network that when accessing the web ui, the storage node shows up properly with space used/available. Now this bug isnt exactly persistent because sometimes it shows up properly when accessing via the eno1 network, and sometimes it doesn’t so its hard to reproduce and troubleshoot. hope this makes sense.

So i ran into an issue recently where i had to reformat my server, reinstall FOG, and import the following from backups that i had:
Users, Hosts, Groups, Images, and FOG Settings. I manually backed up /images to a different workstation with plenty of space. I used the export function to create these backups. My coworker had registered a new host and captured an image after i had created those backups. So he had to re-do that work. So is there a way to automatically backup those items on schedule? Not sure if using mysql will export all of those items. If it does then i can just create a cronjob to complete that task. I will run it every weekend when no one will be capturing or deploying images.

Right my freenas server is hosting on http not https via webdav. it is being hosted on an isolated network so i dont see the need to secure it, plus the webdav is set to read only. so FOG is set to ipxe over https by default? how can trust be established at the BIOS or UEFI level?

the only time ive seen permission issues with ipxe is when the tftproot folder isnt public with read and execute, but that was on my freenas server using dnsmasq for dhcp and tftp. maybe check the permissions on /tftproot and /var/www/fog/service/ipxe.

how is FOG able to set the hostname in Windows immediately after imaging though? I’ve noticed that after imaging, the computer name in Windows is set to whatever i set the hostname to during the Full Registration process.

Great thanks! should i use 1.5.7 or the latest git version 1.5.7.2?

i did read your warning loud and clear, but like i said the Web UI was down and i didnt want to leave the server down all day through the weekend and into this morning, so i rolled the dice. The process of reinstalling everything wasn’t too bad. hey now i have backups of everything and i learned a lesson.
Ok so if i just say “No” to the first part of the installation where it asks if i want to reinstall apache and php, everything else should go through without issue?

I am running Ubuntu Server
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

So I do have an existing “/images” folder that is not empty, and would follow your instructions to back that up as “/images_old” and create a new one called “/images”. Theoretically if all goes well with the above steps and I successfully mount my RAID array to the newly created “/images” folder, what permissions do i need to set or will the data in the RAID array already have the correct permissions and it is just a matter of mounting?

UPDATE
Since i canceled the installation/upgrade process, the web UI is not working. I haven’t tried running any tasks yet but hopefully that part is still working.
UPDATE 8/16/19 3:56pm
so i went ahead and ran the update and broke mysql and mariadb beyond repair. apt update --fix-broken wasnt working. so i backed up my images, and reinstalled ubuntu server and fog 1.5.5 fresh. i luckily had a .sql backup file i exported two days ago and was able to import it via web ui successfully. i also mounted my RAID array to “/images” and its working fine. i will hold off on updating FOG to 1.5.7. Thanks for the input!

downloaded the latest tarball 1.5.7, extracted, ran installfog.sh, detected fog settings, all was fine until the last part “Here are the settings FOG will use:” the line that says “Image Storage Location: /images” is incorrect, i have my images going to “/Images” (capital I) because i have a RAID array mounted to /Images. I was unable to mount my array on /images so that is why i created a new image storage folder. I canceled the installation. What should i do?

oh ok good. thanks for the prompt reply. so i dont think i used the git method initally. im looking at my home directory and see a folder called “fogproject-1.5.5” and an file called “fogproject-1.5.5.tar.gz”. inside the fogproject folder, i dont see any script files except “uninstallfog.sh”. so should i follow the installation instructions on the fog wiki? i believe i saw something about using git. i assume that the installer will detect fog and try to update it?

new forum user here. we’ve been using FOG at my workplace to replace ghost and has been working well. question is, since my FOG version is 1.5.5, id like to update to 1.5.7 but have read on a different forum months ago that updating fog will reset/clear all the customization, almost like it is being installed/set up for the first time. is this true? what is the best way to update FOG without having to backup/restore settings especially the dhcp/pxe/ipxe stack?