@george1421 WE GOT IT! Thanks for your help!

@juelson The output of the commands I asked you to run look normal except the directory listing of /images. There is a missing hidden file that FOG uses to know its connected to the correct image store.

There should be a file called .mntcheck in both /images and /images/dev This file is created by the fog installer so it should be there unless someone adjusted the contents of the /images directory.

So we can fix it with the following command. We will fix /images/dev so uploads work correctly while we are at it.

Key in these commands at the FOG Server’s linux console. You may need to use sudo if you are using a debian variant or do this as the root user.

This is a non destructive command so its OK to run them even if the file exists. Once the .mntcheck file is created you download should work better.

@juelson Yes and what didn’t work? From your other thread you are using fog 1.4.4. That should support uefi systems, but it probably won’t see your nvme drives. For UEFI systems you need to send a different boot loader than for bios. For bios, dhcp option 67 should be undionly.kpxe that will pxe boot a bios based computer. For uefi based systems you need to have dhcp option 67 set to ipxe.efi. or snp.efi. Since you are using a really old version of FOG with new hardware you might be out of luck until you upgrade to FOG 1.5.x branch.

Points of interesting.

@juelson I’m not exactly sure what you are saying here, so let me reword what I think I understand your issue is using my words.

I’ve pxe booted and selected full registration to register my computer with FOG. Registration works just find but when I go to deploy an image and create the deploy task, when I pxe boot into the fog the iPXE menu it shows the computer is not registered with FOG. I know it completed registration OK because I can see it in the web ui.

I know I used more words than you did, but I applied what I think I understood with your issue to ones I’ve seen before. Did I explain the situation you see now?

@mgoh You could probably update the size with a sql command if you wanted. Not really a need to do it though.

@george1421 Got it. I set up the rules using ufw with the ports from that list. I only tested a Full Reg and Inv so far. It hangs on Running Init Scripts for while then skips it, I think that is the script that pulls the serial number from the bios and auto-populates it as the hostname. I confirmed this when I disabled ufw and that step went right through without delay.

@begelmir So I have to ask a few questions.

What is your current pxe boot server? Is it using syslinux or ipxe or gpxe as the boot loader? If you don’t know look at dhcp option 67 and tell me the file name that you are sending.

Why do you want to keep your existing pxe boot environment and then add in FOG?

When you install FOG just install it with the defaults answer no to install dhcp server and or dns server. You want the fog server to be totally dependent on your existing environment.

@george1421 So the second part of this is; I would create a custom FOG iPXE menu item to test this next bit. Since refind exists in the http path we can use the http protocol to grab the files you need.

I would start out by cloning the FOG provided refind.conf file to… for this example refind2.conf. Place any files you want to load in the http path on the fog server but not in the fog file path because an upgrade will delete your custom files. For this example lets create a new directory with
mkdir /var/www/html/crefind place your cloned refind2.conf file in there plus any other files you want to load onto the refind vhd.

Understand I did not debug this menu at all, I just glued the bits together. So it might work or might now. But the idea is correct. Remember in your refind2.conf file the ipxe vhd has no paths so everything is stored in the root of the vhd. So this config file stanza
icon /EFI/refind/themes/rEFInd-minimal-drunkcj/icons/os_linux.png
Needs to be rewritten as
icon os_linux.png

@gjo on the host itself, you can look in the fog client log. You can also look at the “PC properties” and see it’s domain status. in Active Directory Users and Computers, you should see the new computer object. A note on this you might not be aware of, FOG will rename the system to whatever name you have set in the FOG Server for that host, it does this just before domain joining.

When I was doing a lot of imaging, we would set the hostname during Host Registration.

@sebastian-roth
good point…
I realized that i put the compression in the image section to the highest level (22 :))…
i will decrease it and i will try to capture again…

@londonfog Not sure but I don’t think there are API calls for the iPXE menu stuff. I suggest you look into using a SQL query/insert or you might be able to code your own plugin to get what you want.

@jmccannon The current version of FOG only has admins and that is it. There is an admin plugin module, but I have never personally used it. I do agree that FOG needs to have and admin user and a capture/deploy/imaging user class.

@george1421 You were right, it was a problem with DHCP, our System team solved it by comparing it with another site, I don’t know the details, but it’s working now, Thank you for your help!

the below entry, opening max connections for sql - was indeed a fix.
default is 151, and i now have been a solid 200 connections for a week with no issues.

in debian 11, i did the following :

sudo su -
mysql -D fog
SET GLOBAL max_connections = 512;

To make this a permanent solution, refer to the link in the previous post.

The count on working branch and dev-branch as of today is 718 fog servers.

@george1421 I made update of IPXE to the latest version and then I tried ipxe.efi and sucess! Thank you!