Well you can start with the wiki page: https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

And here is an older document, but the concepts still apply. There is no need to hack the php code any more since you can edit the pxe boot menu inside the fog web gui now. https://wiki.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options

@russkil said in Is there a control list of what you can expect fog to do?:

One question that does spring to mind tho is with fog does it change the host name of a machine in fog would that take effect at the time of boot or at the time of reimaging?

The FOG Client (if installed) will also enforce hostnames. If you change the hostname in the web interface, the FOG Client will make the change on the remote system. If the hostname on the remote system gets changed, the FOG Client will re-set it to what you have defined in the web interface. If the system is also domain-joined, the FOG Client will also rename the computer’s object in Active Directory too.

@Bob-Henderson Thanks for the tip, I am sorry to have nothing to offer but we are a startup wich means that every single penny comes out of our pocket and things are going bad down here in Brazil so… I appealed to the “ecofriendly” therm because it’s the very core of our startup and how FOG is a linux-based project I thought it would be in the same ecosystem where people are used to help each other for some cause or sympathize for the idea and etcetera, explore your technichal habilities was not my intention.
I will take a look on theese other projects, thank you again.

The iPXE boot loop is kinda strange. I think I’ve never seen this! Why was default.ipxe missing in the first place. How did you get it back? Can you please post the content of that file here in the forum. You should find this text file in /tftpboot/default.ipxe on youf FOG server (192.169.250.100).

@Tom-Elliott Yes

@Jarl2.0 If you are using zStd capture speed will be much slower than deploy speed. That is the nature of the compression tool. With gzip you don’t get as good of compression ratio or deploy speeds, but capture and deploy are similar in speed. For Zstd 11-13 is probably a pretty good range to stay in.

i like the idea of using /quit instead of /shutdown and getting sure the shutdown is a real one with shutdown -s -t 0 -f 😉
I never used the chkdsk portion but it would not do any harm 😄 but wasting time :p… well i do a defrag instead.

If there is still a hdd i think it would make sense to defrag before you write cereal to it 😉

@Sebastian-Roth Thanks alot i will try that 🙂

@chris178 Look in the FOG community scripts on git-hub: https://github.com/FOGProject/fog-community-scripts

Wayne wrote an excellent script called MakeFogMobile Download and install that. His script sets up a cron job to check to see if the IP address changes if so then it updates the fog configuration.

@joseska For other fog variables you can make http call to the fog server for the other settings from inside your snapin script.

Here is some info: https://forums.fogproject.org/topic/9613/invoke-hostinfo-php-from-powershell

Hello. I know this is quite an old Post but it is quite close to my issue. I managed to deploy a dualbootloader (grub legacy) with a Ubuntu and a Windows 7 OS. Now i just wanna replace the Windows 7 with another Image but i wanna keep the existing Bootloader and all other OS in it. Is there a way to deploy a single OS into this bootloader or do i have to deploy the whole thing again (Grub+Ubuntu+ Windows 7)? Also is it possible to deploy an OS and then integrate it into the original FOG Bootmenu (Not just an iso i mean the native os)?

@Wayne-Workman Thank you too ! Will work this out 🙂

If i’ve any trouble i’ll come back here !

Nothing you should know other than you’ll be pleasantly surprised when your knowledge about Ubuntu directly applies to Debian while also having fewer problems too.

1.4.4 is the current stable release as of today.

@markus1204 said in FOG SERVER IMAGE TYPE:

.WIM is only used with Windows Image. These files cannot simply be added to the FOG Server and used as the image data on the server. Fog uses Partclone to create its images, and partclone is NOT the same as WDS/MDT/WIM files. We store the files with the .img extension so people know it’s an image file, but these are compressed (typcially). We don’t add the compression extension as users are now able to select their own method of compressing the image.

@Benjamin_D said in Adding FOG database to another FOG database.:

the centralized AWS EC2 FOG server gets up and running.

You will absolutely want to use certbot to configure https on that machine.

have you considered setting up the storage node, disabling replication, and updating the files manually?

@sjensen said in Moving FOG virtual server to a new server.:

@Wayne-Workman is there a specific process you used? Did you export the VM?

No, I migrated. This is a Hyper-V feature.

I feel I should add the only reason FOG doesn’t win on “disk to disk imaging” is because of how it’s configured to operate vs an inability to do such a thing. It can most definitely do Disk to Disk imaging, but it’s written to take advantage of mass imaging particularly over network.

@Maorui2k From your description the issue could still be caused by some of your machines instead of the switch being the bottleneck. Again, I am not saying that switch isn’t causing this. Just want to point out that testing PCs in batches doesn’t cost you money (like a new switch would) but only some time.

Multicast in FOG works pretty similar to how Ghost does it. Although back at my old working place we had strange performance issues which we never had using FOG multicasting!