FOG Hangouts group

JJ Fullmer

@bond007fink @jayrehme
By “Latest Update” do you mean the December updates for Win 11 or do you mean the latest release version of 25H2 ? I haven’t tested 25H2 yet.

JJ Fullmer

@pbriec Sorry that your post got lost in the shuffle, I saw it pop up with @raul’s response.
I imagine/hope you got past this in the last year but just in case, the fix would most likely be resetting the host encryption from the web ui (removes some token related database entries on the host record) then restarting the fog service on the client.

If that didn’t do the trick, then restarting the fog service along with resetting the hots encryption should fix it.

JJ Fullmer

@CoNickt @avh2025
Not all usb ethernet adapters are created equal. I would usually say to just bite the bullet and get the vendor specific adapter but it looks like you already did that. I have usb and usb-c adapters that work fine but different uefi firmwares behave differently. i.e. Microsoft surface just has to have its surface branded adapter for native boot to work. HP will work sometimes with the dell or lenovo pxe capable usb-c adapters. We also recently got 2 different hp laptop models where one had to use snponly.efi and the other was fine with ipxe.efi. I maintain a table of models and which adapters work with what we have. Lots of things do just work once you have a collection of usb adapters. Unfortunately, it’s an issue of hardware vendors adding proprietary limitations, but luckily between fog and ipxe you can typically get it working pretty smooth.

Generally if you’re able to pxe boot though, it should find the adapter within pxe. It could be a case of it being too “new” an adapter that requires a different driver not in ipxe. In that case though, I would try using snponly.efi as it may have different behavior with less things loaded in the pxe side. It may also be a driver or setting needed in ipxe that could be handled in a custom compile of ipxe, there’s some info on that here https://docs.fogproject.org/en/latest/compile_ipxe_binaries

It’s also possible to use a tool such as rEFInd to get to a uefi cli console. If you load the ipxe.efi and or snponly.efi and then if you can obtain them the efi driver for the adapter you can do a fs0: to enter the usb disk (it may be fs1: or fs2: you gotta ls on each disk to find the right one) then load usb-network-driver.efi then ipxe.efi to ensure the usb network driver is loaded in the efi for that session and then boot direct to the pxe file which will start the fog network boot. It’s a bit of a hassle but it usually works for me when all else fails. I have an old startech usb 2 ethernet adapter I do this with. This has worked universally but it’s not an ideal solution, but can be poc that it can be done on any device.

I hope my rant was helpful.

JJ Fullmer

@bond007fink @jayrehme
I do a monthly update to my image (single disk resizable) with the latest updated added to the iso I use to install. So I’m using the November iso with the December updates embedded for win 11 24H2 x64 and I had no issues with resizing.

So it may be a config issue on your end or it could be a more specific use case due to a windows upstream change.
Can you give a little more information on the hardware you’re capturing from and what your settings are on the image definition in fog?
I can try to recreate to some extent.

lukebarone

@Bristow-0 You can clone the repo, and run the installer from the branch you want to work from. When you install FOG (either downloading the files or running it through git), it will create a settings file that will be read during subsequent install attempts to fill out the default answers.

rogalskij

@Tom-Elliott Thank you so much Tom, as always I appreciate your support and guidance.

rogalskij

@Tom-Elliott

So, does that mean I should install the new one at the top? Or do I have the new one already by virtue of installing back in July? Sorry versioning gets confusing for me. Also what is FOS?

rogalskij

Our Fog instance updated to Kernel version 6.12.35 sometime over the summer. Since then new Kernel versions have been showing up under the Fog Configuration > Kernel Update menu per normal. The version number on these new versions however keep showing 6.12.35, the same that we already have. The first 6.12.35 shows July 15th as the date, but the newest 6.12.35 shows October 14th as the date.

Is this a bug only affecting us? Should we just update to the new version even though it shows the same number? Anyone else experiencing this? I just want to make sure I have the latest Kernel for new devices we purchase. Thanks everyone!

JJ Fullmer

@george1421 said in Broken iPXE boot loader:

@Mightmar I wonder if the devs for iPXE has changed something in the ipxe source code to cause this error message about autoexec.ipxe not found. This should be supplied by the fog project add on files. I’ll take a look at the compiler to see if something has changed. You should not see this error.

Reinstalling 1.5.10 will fix the error of the latest build of iPXE. Also you mentioned about a later version of FOG. Yes you can install that over 1.5.10 without issue. It should also have updated (but not the newest version of iPXE).

This is the first post I found searching autoexec.ipxe so replying here for future searchers.

This was an addition in a recent ipxe version, and is meant to be a way to add ipxe based functionality without needing to recompile ipxe in order to edit an embedded script (https://github.com/ipxe/ipxe/discussions/1237#discussioncomment-9847219), I can’t find the post/doc again but I remember reading in one place that ipxe added it as part of the hopes of getting a signed ipxe shim so users could use the signed shim and then use this script to add what they can’t embed. While technically we can create a blank file in /tftpboot/ i.e. just

#!ipxe

which will remove the error during boot, this can then cause kernel panics when loading into FOS. Why it does this is a bit of a mystery at the moment, maybe it’s adding to or replacing another part of our pxe menu scripts that causes something in loading the kernels to lose access to ramdisk drivers. But adding it can break everything, so for the time being, just ignore the error.

soscrafts01

Hi,

i have in school one computer class without stored in bios windows pro key and i try to assign to host a windows 11 pro key but for the whole class when i deploy image more than half pc have some error about the isntalling windows was interrupted i think it might be problem with unattend file on image or that i wrote one windows key when i was creating the image but if it was a problem i think only one pc would imaged well but always few pc is imaged well the funniest thinks is i make image on this same device which is in class but in another class where we have another devices i did not have this problem i sometimes i had issues with to old or too new bios but this time all class have this same id of bios

Well where i need to look for problems? in unattend file or in that i put key of winmdows 11 pro to distribution image ?

J	Joe Schmitt
S	soscrafts01
O	oelked
M	Mr_____T
B	broodbaron
R	rcalayan
H	hammerc807
D	dyacishyn
L	lukebarone
M	Melisa
Y	yushin
B	brechtvervaeke
A	abasto
E	emreonder
R	rogalskij
M	mkoliva15
C	carltoncortez
A	alvin.bayani
K	kguevarra
D	David Raymond

FOG Hangouts

Posts

Member List