@sebastian-roth
Updated to working this morning. I’ll post an update after we get a few machines imaging. Thanks again for your help.

@Deimos Ok, great to hear this is fixed! I am marking this solved then. Feel free to open new threads in case you run into new issues.

@degaro While this response may be a bit snarky; my response would be, what would you have learned if it worked perfectly right out of the box? What do you now know that you didn’t just a few hours ago? You DO learn more and remember it longer when you have failures than success.
The FOG developers can only protect the IT admin so much. I agree that the question needs to be worded better. Maybe something like:

Would you like to have the FOG server act as the DHCP server for your network? [y/N] Y

The default is no, but the IT admin can still pick yes. The developers really can’t stop that.

@Avaryan Well it looks like this got us past the DHCP issue of the inital posting. So adding that ID to the kernel source code does seem to help.

Please check your apache error log right after you see this error on screen. See my signature on where to find the log on your FOG server.

Just dug around, and it would appear that you are right about being able to use GPO. Is there a way to automate this? If not I’m probably just going to go back to sneakernetting this from a flash drive. We haven’t joined our computer to a domain yet so I can’t really push it that way.

@Taspharel This hopefully helps:

chmod 777 /var/www/fog/service/ipxe chmod 666 /var/www/fog/service/ipxe/bzImage*

Then try kernel update again.

@Deimos Sure, all fine. Take your time and thanks in advance!

We should be able to collaboratively work on this here: https://demo.firepad.io/#6XlP080kbJ

Would be great if you open a new “German Translation” thread anyway. I am sure it’s good to post it there and discuss things.

@jgallo Oh I see now. I needed to modify the fog.postinit file to call patch.fullreg. So now the last line in fog.postinit reads
. ${postinitpath}patch.fullreg With that final modification, my custom registration menu now works! Thank you for all the help, this community has been great and I am really liking FOG.

@jbranka4 Sounds kind of strange that machines with Win 10 did still work but Win 7 ones didn’t. From what I know about this it shouldn’t really matter if it’s Win7 or 10 in that case IF

exit style is configured the same way for all of those machines all are either legacy BIOS or UEFI

I kind of expect to see a difference between those machines beside Win7/10, most probably BIOS vs. UEFI.

@FallingWax Ok, now I see what’s wrong here. Thanks for reporting this issue. Moved your post to bug reports.

When changing the way FOG exports the DB we obviously missed out on fixing the backup script as well. No one reported yet so we didn’t notice until now.

You can edit that script and exchange line 74 which starts like wget ... with the following call:

wget --no-check-certificate -O O $backupDir/mysql/fog.sql "http://$ipaddress/$webroot/maintenance/backup_db.php" --post-data="type=sql&fogajaxonly=1" 2>>$backupDir/logs/error.log 1>>$backupDir/logs/progress.log 2>&1

This is until we fixed this in the official code… @Tom-Elliott Mind having a look if this call is about right?

@wayne-workman Thank and it is working!

Well I can see from the message, you are trying to boot a uefi system. What exactly do you have configured for dhcp option 67? If its undionly.kpxe then that is your issue. You need to send a uefi boot loader like ipxe.efi.

@sebastian-roth Just tested RC 9. The host doesn’t show up in the pending MACs report, but does show up in the ‘list all’ in Host Management, but is unapproved at that point. Clicking a little link towards the top of it’s general page will approve it.

So, from what I’m seeing, the pending MACs list has something wrong with it, but the auto-registration is working.

@ally_uk Can we mark this solved?

@abra4242 Can you please take a short video of the reboot cycle and post a link here so we can have a look as well?

@datastream Ok, thanks for the update. Unfortunately this sounds like there is nothing we can do for you. Marking this solved for now as the root cause is identified and it’s not FOG.

@Derek-Newbold I am marking this solved as we haven’t heard back from you in a while an I expect you’ve figured things out by now. Feel free to post again if you still need help on this.

@jflanagin Any news on this?

I got it working. Not sure how but we are up and running on latest. Thanks guys

@zingaro Can we mark this solved? I guess sudburr’s hint is spot on.