I think it’s a good idea for the FOG Trunk installer to automatically backup the DB before it touches anything else. And I would like the backup to be labeled with the previous installed revision number and the date of the backup.
I’d like for these to be stored inside of /opt/fog/
I’m happy to code this myself - but I just need help with getting the revision number from the previous version.
perhaps… just perhaps…
Run the download in “debug” mode,
mount the SMB share manually at the CLI, and start the imaging process? (do not use the “fog” command, it tries to mount via NFS).
You’d have to dive into what the “Fog” command actually does… find it’s file and examine what is in it…
And just do everything in there except the NFS stuff (because you already mounted via SMB, right?) and cross your fingers and see if it works?
The "Troubleshoot NFS " article MIGHT assist you with some of this…
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS
And the ill-completed Fedora 21 Server article has examples of SMB mounting…
https://wiki.fogproject.org/wiki/index.php/Fedora_21_Server
and, if you can figure out the commands to issue… and it works… then modify the “fog” command so that it does those things every time, then it should work for normal image downloads?
You’d have to modify the upload processes too.
I’d totally absolutely try this like right now but my servers are down due to a dead AC adapter for my router 
Would you be willing to upgrade to Trunk to see if this resolves your problem?
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
Bumping this thread for @Jbob
@RileyG said:
@Wayne-Workman Hard to tell. This lab was imaged last year from a single and then all set individually touched to update and change names etc. Did you catch the update? The machine is reporting BOOTMGR is missing. I may pull the drive and check it as a USB attached to see what is has on it.
@TheKoR uses FOG Trunk, and so do I at both my work and home. I think there would be a good chance that your issue would be resolved if you moved to FOG Trunk.
My reasoning for this is the extra 100MB partition you’re seeing. There was a bug in 1.2.0 that didn’t work well with manufacturer’s custom MBRs (specifically Lenovo and Dell). You’re affected by this issue, and it’s mostly resolved in the current FOG Trunk, so I think you’d have good odds with upgrading.
As before any update, save your DB and your hosts prior to this. FOG Configuration -> Configuration Save -> Export. Host Management -> Export -> Export.
Here is the article about upgrading to trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
@techpromise said:
@Trevelyan Awesome, Thanks!!
Just curious however, we have many images, is there an automated way to do this via some kind of SQL dump and import into the new server?
There is.
FOG Configuration -> Configuration Save -> Export/Import.
That’ll dump / load your ENTIRE database.
I export mine EVERY Friday, along with all my images too. AND I make snapshots of my FOG server every Friday, AND I do a complete windows server backup every Friday… AND I have live replication enabled on my virtual FOG server…
If I go down, it won’t be for long lol.
@Quantum I do apologize. I didn’t know what you were talking about and mistakenly thought you were referring to auto registration. @Jbob explained it to me and I think what you’ve suggested is a great idea. Again, I do apologize.
Also, Welcome to the FOG community. 
You have to specify that the NIC is a USB adapter with a kernel parameter on the host’s general page. YOu must set the ‘has_usb_nic=1’ kernel parameter.
So, it should look like this:
But, I believe that Surface 3s are UEFI, so you will need to use an .efi boot file. All the boot files available are in the /tftpboot directory, I suggest trying ipxe.efi first.
Past these things, you will need to upgrade to trunk, I believe, for better Windows Tablet support. There’s been a lot of work done in this area in FOG Trunk. You will still need to use the .efi files and the kernel arguments with fog trunk, but you might have better odds with getting it working and getting all the partitions to recognize correctly. Here’s info on FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
Please report your findings - this is how you give back to the fog project - by reporting back with details.
You need to troubleshoot TFTP and FTP both, it sounds like.
Check these out. If you have questions, come back here and we will help.
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
There’s links in the TFTP one for DHCP, that needs looked at too, probably.
I think killing any existing lftp instances is possible with scripting.
for instance,
kill -9 $(pidof lftp)
Or this way:
kill $(ps aux | grep 'lftp' | awk '{print $2}')
Shamelessly Googled and found here:
http://askubuntu.com/questions/239923/shell-script-to-9-kill-based-on-name
http://stackoverflow.com/questions/3510673/find-and-kill-a-process-in-one-line-using-bash-and-regex
hash tagging this so I can find it later for addition to the wiki.
EDIT: Added
@Tom-Elliott said:
@Wayne-Workman I think a better approach would be:
./installfog.sh --docroot /var/www/html --webroot fog/
./installfog.sh --docroot /var/www/html --webroot fog/ -y
@need2 said:
Also ensure your 7020s are on the latest BIOS release. I have seen a number of PXE issues in Dell systems that are on early editions of their BIOS, especially in 3020, 7020, and 9020s.
The newer optiplexes (in my experience) auto update their bios. there’s a dell utility that, if installed, will keep it updated.
Added to the WkKi’s working hardware list here: https://wiki.fogproject.org/wiki/index.php/WorkingDevices
@plegrand said:
@Wayne-Workman but you agree it’s a litle bug ? or it’s a problem on my machine ?
Yes it’s likely a non-impacting bug.
And you can install with /var/www/fog with the commands below that I’ve provided.
It’s also very easy to change the storage location via the Storage Management area in the Web Interface.
For the record - I do not want the legacy client dropped.
The new client has yet to work for me.