FOG version 1.6.0-beta.5136, https enabled
PXE works great with Wyse 5070 thin clients and Dell Optiplex 3000 thin clients.

Tried my first 5060 today.

Wyse 5060, BIOS 1.0J (2018-11-06), UEFI boot, Secure Boot disabled. PXE acquires DHCP, downloads EFI binary and autoexec.ipxe. Even an autoexec.ipxe containing only:

#!ipxe
echo HELLO
sleep 30

causes an immediate reboot. No requests for default.ipxe, boot.php, bzImage, or init.xz ever reach the FOG server. Same FOG server works perfectly with Wyse 5070 and Dell OptiPlex systems.

I’ve tried handing out all the different *.efi devices in my /tftpboot dir, all do the same thing. I know this is a really old system, it’s just weird that it’s just rebooting so early in the ipxe process.

Has anyone seen this before? THanks

FYI for anyone else running into this issue - I believe the problem was that I didn’t erase the /tftpboot images when I switched from http to https. I’m not really sure why that would matter, but when I did that, then re-ran the server reinstall and selected https, the images got but back in /tftpboot and my hosts didn’t see the mac error anymore.

My title is wrong, should have been “no viable macs to use after switching to https”

Running Version 1.6.0-beta.5136 on ubuntu 26.04.1 LTS (apache 2.4.66-2 and php8.5-fpm).

I had everything working fine in http. I then reran the server installer to switch to https. As soon as I did that, when I would try to register (either quick or full) a new host from the pxe menu, I’d get the error “no viable macs to use”. This happened on 2 different architectures, each system only having a single ethernet port on the motherboard.

PXE boot was still happening over http, but I had (successfully) switched the server over to https. I nuked the .fogsettings file, re-ran the install script, selected http only and now everything works again.

I’m running FOG 1.6.0-beta.5115 on Ubuntu 26.04.1 with apache2.4.66-2 and php8.5.4-0 (mod_php, not php-fpm).

I’m just getting this setup in my environment, and I’ve successfully imaged and deployed a few thin clients (Dell Optiplex 3000 and Wyze 5070) with Windows 10 IoT images. I have a powershell script that runs after imaging that completed the setup in my environment. Specifically, this script changes the hostname and joins my AD. All of this works fine.

The problem I have is that the hostname in FOG doesn’t update when I update the hostname on windows. The Windows hostname baked into the Wyze 5070 image is ‘wyze1-5070’. That hostname gets registered with Fog after the initial imaging, because the image has fogclient on it. I then run the powershell script which changes the name and reboots, but fog still refers to it as wyze1-5070.

Is there any automatic way to have the fog hostname updated to match the windows hostname? I have the ‘Hostname Changer’ service setting enabled by default, but I think that’s for fog pushing hostname changes to the client, not the other way around.

Thank you