@wayne-workman yes but I would set a windows task to manage the updates. I found fog daily work fails once the client fails. Then I don’t have daily info that I was aiming to collect.

@tom-elliott said in Updating DataBase Failed:

@zago123 FTP is port 21.

To add to what Tom posted, FTP actually uses 2 communications ports. From the fog server to the target (command channel) and then from the target back to the fog server (data channel). So ports 20 and 21 are used for a fully ftp connection.

@tom-elliott

Thanks for the reply. Everytime I reinstall the fog server am I going to lose all my settings and hosts and images?

@hanz Thank you very much for your feedback.

I switched over to chat because the Q&A turn around was faster.

The first issue was the OP had dhcp option 60 defined. This caused the pxe booting client to think the fog server was a proxydhcp server. When the fog server failed to respond the client just gave up. It ignored the dhcp option 66 and 67 settings that were defined.

When the OP removed dhcp option 60 then a new issue popped up with some incorrect policy settings in his windows 2012 dhcp server. After that was fixed and he rebooted the fog server everything started working!!

I’m solving this thread since its now working.

@entr0py said in Error Restoring Images - Clients having identity crisis:

MSI

Can I ask you to post to this thread: https://forums.fogproject.org/topic/10987/what-can-we-do-when-we-don-t-trust-uuid With the inventory data from one of those MSI boards? We only need one entry unless you have different computer models than mainstream Dell,HP,Lenovo. We are looking for a good example of different mobo manufacturers and how they populate smbios (what FOG queries to identify the target machines).

@jhalbert You need to setup the location plugin: https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

Assign your nodes locations, and assign those hosts at that remote site to the same location. After this, those hosts will only image using that location’s server.

@quazz I currently have a colon : isolating the host name and the path in my configuration. I can boot into the Win10 recovery properly. I’m suspecting the files are not in that directory or the permissions are set such as to not allow access via NFS. Either way this process will not give the OP what he wants. Will it boot the recovery program, Yes. Will it allow a complete restore, No. The swim files are still on the FOG server with no way for the recovery program to access them. I’m not done with the document yet, but it looks like Win10 will have to follow the same process as Win7 with a WinPE environment connecting to a network share to run the setup.exe program to install Win7/Win10.

ref: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/10

@Sebastian-Roth and @Tom-Elliott Thank you so much for your help. Backed-up my current images and cleanly installed from the latest GIT-repo 1.5. Coping back the same hooks worked again. Not sure what happened during the upgrade but fog is back in production now.

Thank you
Chakri

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