@Wayne-Workman Awesome! Tested on a test VM with Ubuntu as well. Works like a charm.

If version information is added to future ARM kernels, the script should pick it up. I did add three hosts to my test fog system. Two of them I assigned valid kernel files to, and the third one I assigned a bogus file name. The script checks to make sure all the kernels actually exist, and are actually linux kernels before adding them to the payload.

Would you mind opening pull requests for dev-branch and working-1.6 again?

@fry_p said in Windows 11/Future for Us:

I still want to help where I can in the Forums though I have been inactive recently, I plan to change that.

Sounds great! You are more than welcome to engage.

Just out of curiosity, how much would it cost to have Microsoft to sign the certs?

I have no idea.

@brakcounty said in Idea: Two "next-servers" coexisting on the same vlan:

Would it be easier to re-run the FOG setup script and just change the FOG IP and disable DHCP? I could also define our existng DHCP server during the setup.

Probably good idea to check out the docs on changing a FOG server’s IP: https://docs.fogproject.org/en/latest/reference/change_fog_server_ip_address.html

@koni said in Can't pxe boot UEFI:

My boot file are download in /root/fogproject/package/tftp

Why do you use those files? The FOG installer will copy those to /tftpboot for you. Then no path needs to be specified. Simply the boot filename, e.g. ipxe.efi

@Florent Good point. I am not sure that notifications currently work. And if not - for how long this is broken.

Have you checked your profile settings yet? https://forums.fogproject.org/user/florent/settings (is it set to notification or email or both?)

@dashwell said in Fog server reporting image error on restoring to larger drive:

I have backups of the FOG and FOS, is there an easy way to check the version of the INIT files, because that was the most recent change?

Beside booting the FOS init (as George mentioned) you can also manually extract the init and check the version on any Linux system:

sudo -i
mkdir /root/tmp
cd /root/tmp
cp /path/to/init.xz .
xz -d init.xz
mkdir loop
mount -o loop init loop/
head -n 2 loop/usr/share/fog/lib/funcs.sh
umount loop/
rm init
cd ..
rmdir tmp/loop/ tmp/

The error message in the picture tells us that either a rather old init was used to caputure that image or the destination disk is just way to small anyway.

@wayne-workman said in [Feedback Requested] Adding kernel info to FOG Reporting:

A single fog server can have many kernels.

On the one hand side it would be great to see more than just the active kernel binary (global settings) but on the other hand we can’t tell if people really use all those kernels or just have those sitting there unused. From my point of view it would get us the most clear picture about kernels in use if we check the database for global kernel filename (64 & 32 bit) and possibly also kernels assigned in host settings (just another simple query to the hosts table. Open for discussion. What do you all think?

I decided to purposely not include the kernel file name, as this may contain some sort of identifiable information. Also I purposely chopped some of the file command output, to get only version information and nothing else.

While I can see that filenames might be a particular name chosen by the admin I don’t think this would reveal too much valuable information. I just say this because I was looking for a way to distinguish between bzImage (64 bit) and bzImage32 (32 bit) using Linux commands but have not been able to yet. Using filenames would help. On the other hand the script could just check the filename and add 32, 64 bit or ARM64 information according to the filename.

If we really use the information from the database we don’t need to think about this part too much.

grub & memdisk kernels are really old. 2005 and 2010. What’s involved with updating these?

I don’t really know where those binaries came from in the first place. Those were added before I joined. Keeping things up tp date is usually a good thing but it can break stuff as well. Some people have complained about us updating rEFInd a couple of times and I am not sure if we should touch these (grub & memdisk). As well I am not sure if newer versions exist. As far as I know this is a grub4dos binary - no update since 2009. Probably similar with memdisk?!?

@TaTa The default NFS in FOG is still version 3 which has no concept of user authentication/authorization. Sure you can try to lock things down a bit by setting access rights on the FOG server filesystem.

But if you want to go beyond that you will need to look into NFSv4 which is not implemented yet: https://forums.fogproject.org/topic/14791/feature-request-for-fog-1-6-x-configure-image-capture-to-use-nfsv4-instead-of-nfsv3

@wilfried7 said in Is it possible to exclude a folder from capturing ?:

Is it possible to exclude /export/ESX-backup from capture ?

No it’s not supported to exclude a particular partition. You can tell FOG to capture only a single partition. But that does not help in your case because it’s setup with LVM.

@dashwell Which version of FOG (and the FOS init) did you use before the update?