@jas777 It looks like you are running an old version of iPXE. The newest version, as of 10 minutes ago when I built it, is 1.21.1+ (g21b5b).
I may be wrong, since I don’t use my own custom certificate, but you probably need to rebuild your iPXE with the new certificate.
Developers
Private
Posts
-
RE: FOG hangs on "... free base memory after PXE unload"posted in FOG Problems
-
RE: Version 1.5.10.1763 incorrect Image Size ON CLIENTposted in Bug Reports
@heix75 Did you update from 1.5.10.1754 to 1.5.10.1763 or from an older version?
-
RE: FOG boot issue after BIOS update on HP ZBook Fury 16 G11 – iPXE autoexec.ipxe not foundposted in FOG Problems
@gchartrandCRL I’m glad that worked! You should be able to keep using snp.efi with your previous machines.
-
RE: HD info not populating in logposted in FOG Problems
@meie1kyl The fix for this issue was done in August 2023 and released in init version 20231208. My guess is that you haven’t updated your FOG install since 2023, or else the init should have “auto” updated.
I recommend that you update your FOG server to the latest stable version since there have been many fixes and security updates since 2023. -
RE: HD info not populating in logposted in FOG Problems
@meie1kyl I may be wrong but I have a feeling you are running an old version of the inits. Can you run these commands:
source /usr/share/fog/lib/funcs.sh echo $initversion -
RE: FOG boot issue after BIOS update on HP ZBook Fury 16 G11 – iPXE autoexec.ipxe not foundposted in FOG Problems
@CanadienITGuy @gchartrandCRL I had to switch from using ipxe.efi to snp.efi for all my newer HP machines. Please try changing that in your DHCP scope options.
-
RE: Dell 3120 Imaging Failureposted in FOG Problems
@Kureebow I’ve had this happen to me before. These are the two cases that I’ve seen:
1 - I captured an image in UEFI and the computer that I was deploying it to was in Legacy mode. I also had the inverse of this, where I captured in Legacy and was trying to deploy to UEFI.
2 (the most common for me) - Some sort of RAID or volume management device is enabled in the UEFI. I only use HP so I don’t know what it would be called on Dell, but on HP there is an option that I have to disable “Configure Storage Controller for VMD”. -
RE: Error while restoring win11 image on hp decoding error (36) : Data corruption Detectedposted in FOG Problems
@jacaman Does this happen with every HP computer or just one in specific? Does this happen with any other brand/model of computer? Have you tried deploying that same image to another computer? Have you tried replacing any component of the HP computer: HDD/SSD/NVMe, RAM, network adapter (dongle instead of embedded port)?
-
RE: QuickReg - Apply AD Settingsposted in Feature Request
@Tom-Elliott Just thinking out loud here… Like you said, the UI interaction would probably be best as a plugin. For the FOS side, I would think that this could be done as a post init script modifying the fog.auto.reg, right?
-
RE: Igel M350C - unable to use integrated mmc after recent FOG Updateposted in Hardware Compatibility
@sloeckle You can use an older kernel for now, but I’ll work on a fix for this issue. I don’t have access to the hardware needed to reproduce this issue. Are you willing to help us test some kernels?
