are they all in a clean shutdown state before starting?
do they already have an OS?

Not sure why I did not just start with trying a pre 6.xx.xx kernel…

Downloaded the the last 5.15.xx Linux kernel slapped it in /var/www/fog/service/ipxe/bzimage-5.15.98 updated the host kernel to bzimage-5.15.98 and BOOM 20GB/min.

Still willing to do some testing if there is anything you need from me to see if this can be fixed in 6.xx.xx.

@Mr_____T Well, I have discovered a work around. According to our consultant, the legacy wrapper message in the 1st or 2nd image was kinda the key. the X360 has no wired nic port and the usb nic adabter is recognized as a legacy booting device. But the unit only boots efi. I followed this link for starters:

Kernel runtime parameter:

Next I added the MAC addresses from each usb dongle I have available. Then, from the fog web interface:

list all hosts
Select the host
Basic Tasks tab
Deploy tab
Task (I first checked debug and followed the bread crumbs no issues)
Imaging commenced.

This is quite a bit more work than I was hoping to do just to image one machine. I was hoping someone out there could come out of the fog (pun intended) and provide some feedback.

So this is not solved. But a work around that does. If you got this far Tx

fixed it by installing gcc-aarch64-linux-gnu on ubuntu and running the script again. compilation errors are not logged to the script shown on screen, but to the bin/error_logs/ directory in the extracted archive.
Update now ran without issues.

@argylega have you restarted the Mariadb and apache services, or the whole server?
I also assume you mean you can’t login to the website. Is there anything in the apache error log?

@JJ-Fullmer We are using FOG 1.5.9 I have tried turning on the Mac passthough. I have tried all of the .efi bootfiles i have. We did get a machine back from Lenovo where they rolled back the biois and that one machine is working fine

@tian I’ve got exactly the same problem. The initial 10 queue items complete, but the next batch won’t start. I have to click the lightning bolt icon in the task list to force it to start. Am running up to date FOG software on a fully patched Ubuntu server.

@eliaspereira I’m not fully sure what is wrong or where it’s wrong at and I don’t really have a means to test.

I’m presuming you posted the issue on github which is a good place to start.

If that is the case it sounds like something missed a step during updating the database potentially?

seems to have sorted my issue, there is an update to the fog client, I had previously version 0.12, installed 0.13 and seems to be working ok now.

@miyaqub I’m going to go on a limb and suspect you have 2 recovery partitions potentially?

it seems that’s what was wrong in the case of this thread you’ve posted.

I found a partial solution. If in the file /var/www/fog/lib/reg-task/registration-class.php on the line where $userTest is, I change the values ​​of $username and $password to the real values ​​through which I log in to the FOG server, I get quickreg including deploy image… This is not a system solution and should be fixed by the developer. (Again, this is for version 1.6, on 1.5.10 this works correctly).

@joshua_mchugh George’s mention of using a post install script to do it is more advanced but very worth the effort. Having it domain joined via sysprep specialize simplifies things in the long run.
That being said, you’re probably misunderstooding groups, because they’re a little confusing. Groups in Fog do not dynamically update the OU of the host members, but it can be used to set the OU in bulk on members. There is a plugin to change the behavior of groups if you want, but I’d try it the normal way first.
But if you set the OU on the host, then when it joins the domain via the fog client, it will be in that OU. It will not move a host to a different OU, unless you do something like manually leave the domain and change the computer name and then the fog service will rename the computer back to what it is in fog and then join the domain in the set OU.

I personally use a post install script now that grabs the OU from to host and Injects that into my unattend file. I believe I’ve posted some examples in the past. If I remember tomorrow when I’m at a computer and not a phone, I’ll link them.