@Erika I don’t want to release this in the official repo since this is just a testing kernel, so here is the link to the kernel on my forked repo. https://github.com/rluzuriaga/fos/releases/tag/EXP_20250110

You’ll have to manually install it since it isn’t on the official repo. This is how if you’ve never done it before.

1. SSH into your FOG server
2. cd /var/www/fog/service/ipxe
3. mv bzImage bzImage_original #Not necessary but recommended so you can revert if there are any issues
4. wget https://github.com/rluzuriaga/fos/releases/download/EXP_20250110/bzImage
5. chmod 644 bzImage
6. chown fogproject:www-data bzImage # For Debian based servers
   chown fogproject:apache bzImage # For RHEL based servers

@Erika I would like to try the newer 6.12 kernel to see if this issue would get resolved. I will have a kernel for you to try later today.

@jeje3346 Oh yes the other thing I forgot in my previous reply is that you need to have the FOG client installed on the computer so that the name change can happen.

If you are wanting to install the FOG client on your golden image, make sure that you disable the FOGService in the windows services. You can use this link for reference of how to do this correctly with sysprep. https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep

@jeje3346 I have seen this issue when sysprep domains the computer through the unattend file. Once the computer is domained, FOG is not able to change the computer name. If this is the case, I would recommend you domain the computer through the active directory options in FOG or through a snapin instead of the unattend file.

I would also recommend you upgrade your FOG install to the latest stable release 1.5.10.1629 since there have been a lot of improvements done since version 1.5.9.

@Erika We just released a new experimental kernel that may fix this issue. Can you try updating to version 6.6.69 and let us know if that one works please?

@westcustom I had this issue with some of my HP workstations. I had to change the DHCP bootfile setting from ipxe.efi to snp.efi and that fixed it.

@stokehall @george1421 I have the 6.11 kernel booting, however I am unable to get the keyboard and networking working. It seems like this keyboard issue is also affecting Linux distributions trying to build for the X1 SOCs like Ubuntu.
I have not been able to test anything on the init (imaging, registering, etc) because of the networking and keyboard issue. Also, Buildroot has not updated their linux headers to include 6.11 so I can build the new init needed.

@stokehall Thank you for the update. I didn’t think Ubuntu was going to start using kernel 6.11 for their 24.10 release, but it seems like they are, so I’ll take a look over the weekend.

Re: Using FOG to PXE boot into your favorite installer images

Please Add “Paragon Hard Disk Manager” to your list this should work with any WinPE

Configuration currently works for UEFI only. It appears the wim file is missing bootmgr.exe for the BIOS booting systems

It is highly recommended to use this on a machine that has 4GB+ RAM.

First we’ll create the required directories:

mkdir -p /var/www/fog/Tools/{iso folder name}
chmod -R 777 /var/www/fog/Tools/{iso folder name}

Now we’ll mount the WinPE iso over the loop directory. Then we’ll copy the contents of the DVD to the directory we built above.

mkdir -p /mnt/loop
mount -o loop /{full path where you have the iso stored}/{iso file} /mnt/loop

We are going to copy to /var/www/fog/Tools so we can use the http protocal already setup for fog management.

cp /mnt/loop/bootmgr /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/boot/bcd /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/boot/boot.sdi /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/sources/boot.wim /var/www/fog/Tools/{iso folder name}
cp /mnt/loop/efi /var/www/fog/Tools/{iso folder name}

umount /mnt/loop

Download and install the latest wimboot kernel and extract it from the zip file.

• https://github.com/ipxe/wimboot/blob/master/wimboot
  The issue was discussed in this post: https://forums.fogproject.org/post/144293
  We will use tftp protocal for this file in the fog menu.

cd /tmp
wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip
unzip wimboot-latest.zip

Copy the wimboot file from the archive directory to root of the os directory (we’ll need this for every windows boot media, so we’ll place it in a common spot).

mkdir -p /tftpboot/os
cp ./wimboot-2.6.0-signed/wimboot /tftpboot/os
chmod -R 777 tftpboot/os

The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS.
In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry
Set the following fields

Menu Item: os.{iso file name}
Description: {iso file you would like to boot from}
Parameters:
set tftp-path tftp://${fog-ip}
set http-path http://${fog-ip}/fog/Tools/HD_Manager
kernel ${tftp-path}/os/wimboot gui
imgfetch --name bootmgr ${http-path}/bootmgr bootmgr
imgfetch --name bootx64.efi ${http-path}/efi/boot/en_us/bootx64.efi bootx64.efi
imgfetch --name BCD ${http-path}/bcd BCD
imgfetch --name boot.sdi ${http-path}/boot.sdi boot.sdi
imgfetch --name boot.wim ${http-path}/boot.wim boot.wim
boot || goto MENU

That’s it, just pxe boot your target system and pick os.{iso file name} from the FOG iPXE boot menu.

@alexamore90 Is this a typo with IP, gateway and DNS all set to the same address?

You might want to run systemctl status isc-dhcp-server (Debian/Ubuntu) or systemctl status dhcpd (Redhat based distros) and post output here.