SOLVED

I was on 18.04 and ran “sudo do-release-upgrade -d”, It finished, I rebooted and was able to access the FOG web interface and deploy an image. I am running the latest stable version: 1.5.8

UPDATE: I had some issues when I upgraded to 20.04 on a different FOG box. It has been resolved.

Thanks

@sebastian-roth The error during the FOG install on 21.10 is related to installing php 8.0 mysql

If I try to manually install php8.0-mysql it appears to be installed already

The GUI works fine and capturing an image goes smoothly until the end where the database needs to be updated

Wow, so I ran the FOG installer again, this time there wasn’t an error when it came to the mysql install.

Going to try capturing an image now.

Hmm. It still fails to update the database.

@Sebastian-Roth

Yes.

I just want to add real quick, the DC 7800’s can boot to the menu with any kernel and without and kernel parameters. They fail when deploying.

I installed the leaked dev version 21996/21996.1 on bare metal and in a VM. Secure Boot didn’t have to be enabled . UEFI and TPM (which requires CSM to be disabled) had to be. Secure Boot - the option only had to be present.

After more testing. I found I could install it in a VM as Legacy. I guess MS laxed on the VM requirements?

I also found on metal, I could disable TPM and enable CSM which should make secure boot completely unavailable. Then I deploy a sysprep-ed Win 11OOBE UEFI image on it without any problems.

I will try pure legacy on metal next…

This was with that leaked dev build so who knows if it was modified or what not and how close it is to the actual dev build release or the final release.

3.13 that comes on the latest dev-branch as of today has issues with APFS on my laptop.

3.20 x64 does not

@Sebastian-Roth

Hell yeah dude, that cleared it right up.

@Sebastian-Roth

Not sure if this has been resolved or if this helps -

I’ve created a Win 10 UEFI VM using the 2004 ISO. VMware Workstation 15 Pro 15.5.6 build-16341506. All the settings were default except I went up tp 8GB of RAM. I installed it, ran all the updates, activated it while waiting for updates, rebooted twice then captured the image with FOG dev-branch version: 1.5.9-RC2.11 running on Ubuntu 20.04 LTS

It deployed fine to a similar VM.

@sebastian-roth Thanks. I just updated to the latest. So far it is capturing an APFS drive on a hackintosh no problem.

@Sebastian-Roth

So yes, this is a perfect solution since Primary host disk can now be set by size. I have one image for the OS disk, and one for the “D” drive. I just switch the Primary Host disk setting depending on which image I want to capture or deploy.

@george1421 I boot from a FOS usb stick that pxe boots to the FOG server. So I am thinking put the T2 Kernel on the server and specify that kernel under the “host kernel” setting for the macs, then on the the FOS stick put the t2 kernel as well?

@Tom-Elliott Maybe I should mention I am using basic DHCP from pihole and dnsmasq on the FOG server is handling the ipxe stuff. Which has been working well up until now? I read something else about the tfpboot directory being redirected to https using the newer versions?

Don’t function as a DNS server:

port=0

Log lots of extra information about DHCP transactions.

log-dhcp

Set the root directory for files available via FTP.

tftp-root=/tftpboot

The boot filename, Server name, Server Ip Address

dhcp-boot=undionly.kpxe,10.1.1.100

Disable re-use of the DHCP servername and filename fields as extra

option space. That’s to avoid confusing some old or broken DHCP clients.

dhcp-no-override

inspect the vendor class string and match the text to set the tag

dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

Set the boot file name based on the matching tag from the vendor class (above)

dhcp-boot=net:UEFI32,i386-efi/snponly.efi,10.1.1.100
dhcp-boot=net:UEFI,snponly.efi,10.1.1.100
dhcp-boot=net:UEFI64,snponly.efi,10.1.1.100

PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.

pxe-prompt=“Booting FOG Client”, 1

The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,

Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI

This option is first and will be the default if there is no input from the user.

pxe-service=X86PC, “Boot to FOG”, undionly.kpxe
pxe-service=X86-64_EFI, “Boot to FOG UEFI”, snponly.efi
pxe-service=BC_EFI, “Boot to FOG UEFI PXE-BC”, snponly.efi

dhcp-range=10.1.1.100,proxy

@Tom-Elliott I’m sorry. I restored a previous version of the FOG server and no longer have any error logs from when all this happened. I can go to 1.6… IIRC there is a change that needs to be made to SSHD conf or something. The last time I went to 1.6 FOG was unable to see the default storage node.

Everything working fine until this latest FOG update. Using a Strix Point laptop with a USB Ethernet adaptor. Also trying to install different kernels through the web UI no longer works. HTTP ERROR 500

I tried installing master branch. Failed, couldn’t even boot to memtest. I restored the FOG VM from a back up made a few days ago. 1.5.10.2144 - everything is working as normal now. Afraid to update

Just thinking, sometime between the 1.5.10.2144 backup, there were tons of dev updates, and one time when I did a git pull on FOG, it deleted a bunch of things. But since the gui worked, I assumed it was okay

FOG 1.5.10.1734

Ubuntu 24.04.3

Booting from the default FOG menu to a Windows host isn’t a problem but Linux… I get errors.

Fresh install of Ubuntu Desktop (EFI). It was installed on a host that was running Win 10 and was able to get from the Fog menu to booti Windows

With Ubuntu and Pop OS I can not boot PXE to the Fog menu to the OS using the stock refind.conf and even this custom one

This error with stock refind.conf and a custom one

Tried making a custom refind.conf

I’m editing the refind.conf on the FOG server /var/www/html/fog/service/ipxe/

Any ideas?

If I wipe linux and install Win 10/11 it has no problem PXE boot to FOG menu to OS

@mmoore5553
Assuming you’ve tried setting the VM to BIOS and UEFI and still no go… Do you have the VM set to use a bridged network connection? Also you have to make sure the boot order on the VM is set for network boot first.

@Sebastian-Roth Can I bother you with this quick question ^^^

All my hosts are registered in DNS accordingly, Usually after doing this FOG is able to see which OS the host is running. Almost in real time. Like when FOG is capturing an image from the host, the hosts section of the UI will show a Linux icon, then after it completes and boots back into Windows, it will show a windows icon. But this new laptop running Win 11 with a USB to Ethernet PXE adapter ,the OS Icon is just an exclamation point that says unknown. I disabled the firewall and refreshed the FOG UI but it still shows unknown. When an image is being captured from it, it shows Linux as the OS What do?

Thanks

I have a Win 11 install that isn’t using bitlocker and the TPM and secure boot requirements bypassed but it is using Windows Hello biometrics to log in (fingerprint). Are there any caveats when it comes to basic capture and deploy?

Thanks

@Tom-Elliott Thank you. Logging out with 1.5.10.1730 works properly.

When Logging out of the Web UI I get a “This page isn’t working
10.1.1.100 is currently unable to handle this request.
HTTP ERROR 500”

To duplicate
Click Log Out Of Fog, which directs to this URL http://[ipaddressoffogserver/fog/management/index.php?node=logout

Gives HTTP ERROR 500

Tried on Brave and Firefox