Topics created by brakcounty

you da man!

i restored the background file, clicked “Update” on the menu settings page of the WebUI and all is fine now. Weird. One question though, from the main FOG ipxe menu, when i hit Deploy Image, and get the prompt to authenticate with fog/pass, that text is blue, i want it to be white. Where can i change that setting?

ill take a look next time i capture. i make sure the actual image size is the compressed, used data from the drives i capture, in the terminal using dh -u. we use a custom sccm image that is based on the stock windows install, which has bitlocker disabled.

@brakcounty Using FOG with more than one NIC is not officially supported. While it can be setup this way and mostly works it can still cause trouble as we see. I probably won’t find the time to set this up myself and test but you are more than welcome to investigate in which case it works or fails. If you need assistence on debugging this feel free to ask here.

@brakcounty It contains all of the exportable items and more (like deployment history, inventory, snapin groups, and other things I can’t remember without looking). The fog database is everything except the raw image data stored in /images. With the metadata (mysql database) and the raw image files in /images you can rebuild your fog server from a fresh install.

i successfully ran the update to 1.5.7. Now i think there is an issue with the network interfaces. I set eno1 for management, and eno2 for imaging/dhcp. I was told on here that it should have been the opposite, but it has been working fine. now this morning i wasnt able to get to the webui from the eno1 network, but was able to on eno2. the port on the switch is set to the correct vlan. i unplugged the cable from eno2, then i was able to get online with eno1. could this have happened during the update? UPDATE so i had to re-apply the netplan file after rebooting the server. everything seems fine now. i can access the webui from both connected interfaces.