@wayne-workman i managed to go from 16 to 18 (server) fine… but when i tried to go 18 to 20 it all went wrong so just rolled the VM back. i will when 18 falls out of support do what Seb suggests and move the images over and the DB to a fresh install… after all my VM started life as v 14 of ubuntu so probably due a fresh install.

@ITCC Someone much more cleverer than me (from ANME) has worked out how to fix it and it is due to sysprep sealed images rather than Fog persay as Tom suggested. the Fix is to add the following to your sysprep SetupComplete.cmd file

for /f "tokens=2 delims={}" %%a in ('bcdedit /enum {bootmgr} /v ^| find "identifier"') do set prep-bcdid={%%a}
bcdedit -set {current} device partition=c:
bcdedit -set {current} osdevice partition=c:
bcdedit -set {memdiag} device partition=\Device\HarddiskVolume1
bcdedit -set %prep-bcdid% device partition=c:

@Tom-Elliott Thanks Tom, yes that looks to have sorted it out thankyou…

@Tom-Elliott Thanks for coming back to me

last two erros from apache2 - the last from 12:14 one is the only one at the timei last tried to pull image from the menu.

[Mon Jan 26 12:13:25.935606 2026] [proxy_fcgi:error] [pid 3067025] [client 192.168.4.119:56722] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Error: Call to a member function isValid() on null in /var/www/html/fog/lib/fog/host.class.php:775\nStack trace:\n#0 /var/www/html/fog/lib/fog/host.class.php(789): Host->_setAlo()\n#1 /var/www/html/fog/lib/client/autologout.class.php(43): Host->getAlo()\n#2 /var/www/html/fog/lib/fog/fogpage.class.php(3290): Autologout->json()\n#3 /var/www/html/fog/lib/fog/fogpage.class.php(255): FOGPage->requestClientInfo()\n#4 /var/www/html/fog/lib/pages/dashboardpage.class.php(76): FOGPage->__construct()\n#5 /var/www/html/fog/lib/fog/loadglobals.class.php(65): DashboardPage->__construct()\n#6 /var/www/html/fog/lib/fog/loadglobals.class.php(79): LoadGlobals::_init()\n#7 /var/www/html/fog/commons/base.inc.php(38): LoadGlobals->__construct()\n#8 /var/www/html/fog/management/index.php(22): require('...')\n#9 {main}\n  thrown in /var/www/html/fog/lib/fog/host.class.php on line 775'
[Mon Jan 26 12:14:51.730575 2026] [proxy_fcgi:error] [pid 3066513] [client 10.7.56.194:46160] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/html/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/html/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/html/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/html/fog/lib/fog/host.class.php(1133): Image->getStorageGroup()\n#3 /var/www/html/fog/lib/fog/host.class.php(1398): Host->_createTasking()\n#4 /var/www/html/fog/lib/fog/bootmenu.class.php(1390): Host->createImagePackage()\n#5 /var/www/html/fog/lib/fog/bootmenu.class.php(1332): BootMenu->setTasking()\n#6 /var/www/html/fog/lib/fog/bootmenu.class.php(493): BootMenu->verifyCreds()\n#7 /var/www/html/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#8 {main}\n  thrown in /var/www/html/fog/lib/fog/image.class.php on line 496'

This is the sql i couldn’t get the sudo commands to run but was able to execute the sql via webmin (everything at the end of the file from this year)

sudo errors (
gordon@fog:~$ sudo mysql -u root fog
[sudo] password for gordon:
ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO)
gordon@fog:~$ sudo -s
root@fog:/home/gordon# mysql -u root fog
ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO)
root@fog:/home/gordon# select * from history
)

5964 	[2026-01-06 15:47:57] Inventory ID: 598 has been successfully updated. 	jash-young 	2026-01-06 15:47:57 	192.168.12.26
5965 	[2026-01-06 15:47:57] Host ID: 750 NAME: HP445RG6T05 has been successfully updated. 	jash-young 	2026-01-06 15:47:57 	192.168.12.26
5966 	[2026-01-16 12:41:48] Image ID: 14 NAME: ZabbixServer-Backup has been successfully updated. 	gordon 	2026-01-16 12:41:48 	10.7.56.207
5967 	[2026-01-16 12:46:40] Host ID: 1217 NAME: zabbixserver has been successfully updated. 	gordon 	2026-01-16 12:46:40 	10.7.56.207
5968 	[2026-01-16 12:46:52] Task ID: 47506 NAME: Capture Task - zabbixserver has been successfully updated. 	gordon 	2026-01-16 12:46:52 	10.7.56.207
5969 	[2026-01-16 13:33:12] Inventory ID: 502 has been successfully updated. 	jash-young 	2026-01-16 13:33:12 	192.168.12.19
5970 	[2026-01-16 13:33:12] Host ID: 656 NAME: HP440G6T10 has been successfully updated. 	jash-young 	2026-01-16 13:33:12 	192.168.12.19
5971 	[2026-01-16 13:34:42] Host ID: 661 NAME: HP440G6T15 has been successfully updated. 	jash-young 	2026-01-16 13:34:42 	192.168.12.19
5972 	[2026-01-16 13:34:51] Inventory ID: 507 has been successfully updated. 	jash-young 	2026-01-16 13:34:51 	192.168.12.19
5973 	[2026-01-16 13:34:51] Host ID: 661 NAME: HP440G6T15 has been successfully updated. 	jash-young 	2026-01-16 13:34:51 	192.168.12.19
5974 	[2026-01-21 13:52:29] Inventory ID: 667 has been successfully updated. 	jash-young 	2026-01-21 13:52:29 	192.168.12.16
5975 	[2026-01-21 13:52:29] Host ID: 819 NAME: HP440G8T11 has been successfully updated. 	jash-young 	2026-01-21 13:52:29 	192.168.12.16
5976 	[2026-01-23 11:56:00] Host ID: 1218 NAME: HP4G1iT01 has been successfully updated. 	jash-young 	2026-01-23 11:56:00 	192.168.12.16
5977 	[2026-01-23 12:18:38] Host ID: 1218 NAME: HP4G1iT01 has been successfully updated. 	jash-young 	2026-01-23 12:18:38 	192.168.12.16
5978 	[2026-01-23 12:19:14] Host ID: 1218 NAME: HP4G1iT01 has been successfully updated. 	jash-young 	2026-01-23 12:19:14 	192.168.12.16
5979 	[2026-01-23 14:48:37] Host ID: 1219 NAME: HP4G1iT02 has been successfully updated. 	gordon 	2026-01-23 14:48:37 	10.7.56.55
5980 	[2026-01-23 14:48:44] Task ID: 47513 NAME: Capture Task - HP4G1iT02 has been successfully updated. 	gordon 	2026-01-23 14:48:44 	10.7.56.55
5981 	[2026-01-26 10:37:59] Host ID: 560 NAME: HP430G5T08 has been successfully updated. 	gordon 	2026-01-26 10:37:59 	10.7.56.57
5982 	[2026-01-26 10:38:06] Task ID: 47515 NAME: Deploy Task - HP430G5T08 has been successfully updated. 	gordon 	2026-01-26 10:38:06 	10.7.56.57
5983 	[2026-01-26 10:38:06] SnapinJob ID: 3313 has been successfully updated. 	gordon 	2026-01-26 10:38:06 	10.7.56.57

Screen shots of trying to deploy from menu

I upgraded fog server the other day it was only a minor version out of date (i just cant remember exactly what it was on but fairly certian it was 1.5.10.17xx)

as explained in the title from the fog PXE boot menu on the client computer if you choose deploy image and pick the image it then displays this error message.

http://myfogserver/fog/service/ipxe/boot.php...  HTTP 5xx Server Error (https://ipxe.org/1d0c6598)
Could not boot: HTTP 5xx Server Error (https://ipxe.org/1d0c6598)
Could not boot: HTTP 5xx Server Error (https://ipxe.org/1d0c6598)
Chainloading failed, hit 's' for the iPXE shell; reboot in 10 seconds

if i go and find the host in the web console and choose deploy image it works fine and will deploy the image - so workaround fine… but i would like to fix it as we mostly reinstall from the client…

From the client PXE menu we are fine registering new hosts (including choosing to image them as part of that process)

your right they do support PXE boot i found the option right at the bottom in the bios you can choose between PXE HTTP and iSCSI
i didn’t do enough scrolling down last time i looked.

@ITCC Someone much more cleverer than me (from ANME) has worked out how to fix it and it is due to sysprep sealed images rather than Fog persay as Tom suggested. the Fix is to add the following to your sysprep SetupComplete.cmd file

for /f "tokens=2 delims={}" %%a in ('bcdedit /enum {bootmgr} /v ^| find "identifier"') do set prep-bcdid={%%a}
bcdedit -set {current} device partition=c:
bcdedit -set {current} osdevice partition=c:
bcdedit -set {memdiag} device partition=\Device\HarddiskVolume1
bcdedit -set %prep-bcdid% device partition=c:

we have just taken delivery of 50 of these units for our school and i can’t get them to Network boot. they have Intel i226-v Nics in them & Intel Core Ultra 5 125H (all very nice)

if i use a USB Stick with D:\EFI\BOOT\bootx64.efi (ipxe.efi from tftp folder) then i can get them to register and image

I am now on Fog version 1.5.10.1650 thinking i might have just needed a newer set of boot files but what i did notice was that on pressing F12 the boot menu says UEFI: HTTP IPv4 Intel Ethernet Controller I226-V
and when you boot it says: >>Start HTTP Boot over IPv4 on MAC: MACADDRESS and it just hangs here and doesn’t start iPXE

is PXE booting and HTTP Boot over IP two different things? and is this somehting i can get working

just to update I downloaded windows 11 23H2 from MS admin console and then made a new image with fog and deployed it and whilst for some reason the GPO that should auto encrypt the c drive doesn’t appear to be working, if I right click it and choose encrypt with BitLocker and chose allow windows to unlock the drive automatically (which is what the GPO should do) it encrypts just fine. So its definitely something new with Windows 11 24H2 I suspect its to do with secure boot being disabled.

Edit ignore the bit about the gpo not working I moved the pc to a diferent OU for testing and it simply wasn’t applied. I have since now forced windows update to install Win11 24H2 and the drive remains encrypted. so this for a while will be a workaround for our staff laptops that need to be encrypted.

I too am trying to get this working its new problem for us on Windows 11 24H2 our older win 11 images were fine so is our win 10 22H2 images.
other than trying the bcd edits in the post i have also tried below but still no joy

Tried separately and together these changes which are suggestions I came across on the net.
group policy editor -> computer config -> admin templates -> windows components -> bitlocker drive encryption -> os drives -> config TPM for UEFI.
PCR 0,2,11 Ticked (i.e. remove 4)
AND OR
group policy editor -> computer config -> admin templates -> windows components -> bitlocker drive encryption -> os drives -> Allow Secure Boot for integrity validation
Disable

Enabling some combinations in the Event log looks like the c drive is encrypting but on restart it then just goes into automatic recovery mode.
If we leave neither of these options set it doesn’t encrypt with the error message reported in this thread about the BCD Settings

These are the sort of Event logs we get (in this is with PCR 4 Removed)
Application and Service Logs > Microsoft > Windows > BitLocker-API

Before the GPO is applied lots of these

BitLocker cannot use Secure Boot for integrity because it is disabled.

After the GPO is applied . with lots of this inbetween the ones below

BitLocker cannot use Secure Boot for integrity because it is disabled in Group Policy.

BitLocker cannot use Secure Boot for integrity because it is disabled in Group Policy.
BitLocker Drive Encryption is using software-based encryption to protect volume C:.

The identification field was changed.
Identification GUID: {ID}

A BitLocker key protector was created.
Protector GUID: {ID}
Identification GUID: {ID}


BitLocker encryption was started for volume C: using XTS-AES 128 algorithm.

Device Encryption initialized automatically for volume C:.

BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.
Protector GUID: {ID}
Identification GUID: {ID}

A BitLocker key protector was created.
Protector GUID: {ID}
Identification GUID: {ID}

BitLocker was resumed for volume C:.

BitLocker successfully sealed a key to the TPM.
PCRs measured include [0,2,11].
The source for these PCRs was: Group Policy.

BitLocker was resumed for volume C:.

And in windows no padlock on the c drive… restart (even after being idle for 30 mins) no adds to the event log either… Windows Automatic repair.

Just to add I have tried it with and without the recovery partition on the end.

@sebastian-roth this has worked for me with a brand new HP 440 G8

@wayne-workman i managed to go from 16 to 18 (server) fine… but when i tried to go 18 to 20 it all went wrong so just rolled the VM back. i will when 18 falls out of support do what Seb suggests and move the images over and the DB to a fresh install… after all my VM started life as v 14 of ubuntu so probably due a fresh install.