@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.

@tom-elliott Great! Thanks, will do.

thanks you guys for advice, i solve the problem by change multi partitions all disks to single disk in Image options.

@user4000 To me it sounds like you hit the nail on the head. Flacky network connection would likely cause such an issue…

See if you want to invest a little money and buy a tester device called Pockethernet. It does a great job but is way less expensive than professional networt test equipment.

Cool. Thanks Tom!

@sebastian-roth said in 1.4.4 install fails - add-apt-repository: command not found:

apt-get install software-properties-common

I may have to go with the 2nd fix and get newer packages from Yakkety to resolve the issue. This server is our office Domain controller as well as imaging server. So breaking the Samba shares and logins will have my team up in arms come Monday morning.

So sad they let this bug slip through. My plan of upgrading all my remote servers and installing Fog has hit a major road bump.

I am going to create a VM and install the latest version of Zentyal from the ISO and see if that makes any difference.

Thank you for all your patience and invaluable assistance. Above and Beyond by far!

@ntalbert Please be so kind and tell us what exactly caused the issue and how you solved it. This is an open source community and this is build on sharing pretty much everything including solutions to locally caused issues as other might have same or similar problems…

@sebastian-roth

The comment from george1421 sis solve my issue. The issue was I had created a custom menu item for dban. There must have been something wrong the way I created the menu item. I deleted the created menu item and it fixed the issue. I will revisit putting the custom menu back on my system later.

Thanks
Kyley