Thanks @Tom-Elliott . That actually makes a lot more sense now.

I saw the greyed-out “Mass edit” button, but hadn’t worked out that I had to select multiple items (turn them blue) from the filtered list of hosts in order to be able to use that button to set values across multiple entries. Once I did, it worked as intended.

Hi. In FOG versions up to 1.5, you could open a group and select an image (and a post-imaging action) and it would apply to all the hosts within the group. This option appears to be missing in v1.6, which is a shame because it saves a lot of time when you have to apply a new image to hundreds of hosts (I’m currently doing it one host at a time in v1.6).

Is this change intentional or is there another way to do this now that I’m just not seeing?

@Tom-Elliott

Thank you!

As you thought, it was a double DHCP server… Even though .6 was in bridge mode, the DHCP server on it was still enabled, unlike the other MikroTik switches we have. Disabling it brought the iPXE booting back. I’ve run a re-inventory task and am now running an image capture task.

I’ll have to keep a future eye open for that as we expand our classroom network.

Cheers!

Hi, Hope you can help me with this.

I was having a dreadful time upgrading from v1.5 to v1.6 (database wouldn’t upgrade and had become corrupt), so I decided to export everything I could, wipe the server, and begin from scratch (the “nuke it from orbit” approach).

I installed a fresh copy of Ubuntu Server 26.04 and then downloaded and installed FOG v1.6.0-RC-14 using the link to the .tz file on the website (not via git). After it installed and after importing all my data again (groups, images, hosts) and setting the new Bootfile Name to “secureboot/snponly-shimx64.efi” on my MikroTik router’s DHCP server, I went to try and boot one of my classroom Dell laptops. It wouldn’t boot from iPXE. I got the following on screen (from a screen cap):

>>Start PXE over IPv4.
  Station IP address is 192.168.5.119

  Server IP address is 192.168.5.25
  NBP filename is secureboot/snponly-shimx64.efi
  NBP filesize is 1048424 Bytes
Downloading NBP file...

  NPB file downloaded sucessfully.
Fetching Netboot Image secureboot/snponly.efi
iPXE initialising devices...
autoexec.ipxe... ok

iPXE 2.0.0 (g12798) -- Open Source Network Boot Firmware -- https://ipxe.org
Features: DNS HTTP HTTPS iSCSI TFTP VLAN AoE EFI Menu
Checking net0 for DHCP...
Configuring (net0 08:92:04:29:13:b6)........ ok
Received DHCP answer on interface net0
Trying proxy DHCP...
Checking for next-server...
Starting netboot to default.ipxe...
tftp://192.168.5.6/default.ipxe.................. Connection times out (https://ipxe.org/)
Chainloading failed. hit 's' for the iPXE shell; reboot in 10 seconds

My server is 192.168.5.25
My MikroTik router with DHCP is at 192.168.5.1
IP 192.168.5.6 is another MikroTik router working in bridged mode as a switch that isn’t serving DHCP at all.

I’ve checked the TFTP service is running and active on my Ubuntu server. Files in the TFTP folder are set so that everyone can read them (777). Firewall is disabled. The only thing I changed on the MiroTik was the Bootfile Name. Everything worked fine in earlier FOG version, so I’m not sure why it won’t boot now that I’m running 1.6.

Please can you make any suggestions?

PS: I know a bit about Linux, but am not an expert or a full-time sysadmin. Am happy to dig into logs if you tell me which ones.

Also occurring on Dell Latitude 5450 laptops.

This weekend I ran a re-imaging job on a room full of 60 Dell laptops. When I got back in on Monday morning, 5 of the Dell Precision 3590 laptops were displaying kernel panics in the iPXE OS sync process. Link to screen photo

I was able to force quit the stalled OS and reboot back into FOG iPXE and successfully complete the disk re-imaging. Has anyone else had this issue, and should I log it as an issue on Github for FOG-OS?

I’m running FOG 1.5.10.1734 (but not sure which FOG iPXE OS version)

@tian I’ve got exactly the same problem. The initial 10 queue items complete, but the next batch won’t start. I have to click the lightning bolt icon in the task list to force it to start. Am running up to date FOG software on a fully patched Ubuntu server.