@george1421 Hey George, sorry I didn’t reply yesterday. I did get everything running successfully. Captured an image and deploying image right now! Appreciate all your help! Not sure how to mark this is as solved but its working!
@george1421 If I may ask you using the git method can I replace the mariadb references to mysql and mysql-server in another file other than .fogsettings . It seems changing it in .fogsettings has no effect it still tries to install mariadb
I have no idea what that boot loader does. Its a component of iPXE.
So tell me about your dhcp server. What is the manufacturer and model.
The idea is that if we can uniquely identify that usb drive, maybe we can send the proper boot file name. If you are using a windows dhcp server and setup efi policies, that is getting us in the direction. That policy looks to see if the arch value is 0 (bios) or 7 or 9 then its uefi. If we can combine the uefi test with the manufacturer id of the mac address then we could send that alternate boot file name when the target computer is uefi and the mac manufacturer matches. Its easier to do with a linux dhcp server or using dnsmasq as a proxydhcp server.
Yes or debian 11 if you want to switch to FOG’s dev branch a.k.a.18.104.22.168 or later. When its released it will become FOG 1.5.10. The newest version of PHP in 22.04 needs a little clean up on the FOG side before its ready for release with FOG 1.5.11.
Do you have any ability to know how many fog users are out there?
I don’t know how many users there are, but I do know there’s 776 FOG servers operating on the dev-branch. There’s an unknown number of FOG servers out in the wild running on a version older than October, 2020.
@rude26 if you have the FOG client installed on the image, then I think by default there should be a “FOG.log” on the C drive of the computer. That log should hopefully have a section in it about computer name and domain joining which generally has info in it about what is going on. Just bare in mind that it appends to the log, so it could have that section of info in the log multiple times, so make sure you are checking the latest info in the log. Sometimes I clear the log and then reboot and check the log again to make sure I’m looking at the latest info.
Did you set it as a “Single Disk - Resizable” image type? If so, were you creating a Windows 10/11 image?
We’ve had trouble with that lately and it turns out that Windows was putting a little partition after the main C partition on the disk. I think FOG tries to resize the last partition by default, so it ends up only resizing that small partition, thus it won’t end up fitting on any smaller disks.
To fix it we just removed that last little partition before capturing the image. I think it was just a recovery partition or something that we didn’t really care about.