@x23piracy I don’t remember the details exactly, I think it had something to do with the inability to chainload in EFI mode, which would be essential to network boot.
I was looking into the same thing a while ago.
@x23piracy I don’t remember the details exactly, I think it had something to do with the inability to chainload in EFI mode, which would be essential to network boot.
I was looking into the same thing a while ago.
@Tom-Elliott I copied the info as is. That’s webgui login information, I haven’t altered anything to do with FTP passwords, they’re all stil set to what they were weeks ago in .fogsettings as well, so I’m not even sure how that would have happened.
At any rate, I’ll recheck all the ftp passwords and report back below.
I reentered the password for the fog storage node and now the error log viewer is back, good call Tom!
I’m guessing this is also why the clients were unable to update the database.
That just leaves the minor errors about mysql outlined in the original post.
Thank you already for you help 
This seems familiar, I believe it was a MySQL connection issue that causes this.
@wcheung Do you need the standard Lenovo thingies? Because otherwise you can download the latest iso from Microsoft to install a clean 1607.
I’m late, but if you’re using inf files and such to install drivers, it’s sufficient to place them in a folder under Windows\inf and windows will install them during first boot. (which means I’ll also recommend copying them over during postdownloadscript stage of imaging)
Just my two cents
My understanding is that you use “fog” as your login account for ssh and what not. (I generally recommend having a user that is not fog to manage the system precisely in case something goes wrong)
The Webgui login is entirely unrelated to the login you use for ssh and what not.
So, the only thing left to do if that’s your only account is to boot into recovery mode and change the password or add a new account and login using that info.
If you still can’t SSH after that then your SSH is misconfigured or broken.
Moved to FOG Problems.
Can you post Apache error logs when this occurs?
@Wayne-Workman
http://www.askvg.com/how-to-change-sata-hard-disk-mode-from-ide-to-ahci-raid-in-bios-after-installing-windows/ instructions for windows 7
I believe Windows 8 and 10 don’t even require this, they tend to be able to handle these things much better, but just in case
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\StartOverride
Change the 0 DWORD value from 3 to 0.
@daUK2010 Yes, you can restart the process, but if you’re low on space, you’ll want to clear out the folder with the mac address as name of your current capture computer in /images/dev
Are you sure you chose the correct image type when adding the images to the database?
I believe “size on client” is something generated when capturing the image, by the way.
@ablohowiak Your MYSQL Server is crashing.
Which Linux distribution and version are you running?
Similar problem noted here:
https://bbs.archlinux.org/viewtopic.php?id=186503
Try usbcore.old_scheme_first=1 as kernel argument
@Mastriani Assuming you can access the data (and the data isn’t damaged/corrupted), it is theoretically possible to get the entire database and the images and put them on a different disk.
These answers are both correct, but there’s another way and that’s to use the FOG Menu Configuration in the Webgui to change the paramaters passed to boot.php
Here is my fog.multijoin for instance
params
param mac0 ${net0/mac}
param arch ${arch}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
Notice three lines are remove, the login param, the user param and the password param. Although, for me personally, this does not work on newer revisions. Works on 6186 and before, not sure about anything after (in my testing it no longer worked and just brought you back to main menu saying invalid login)
Try
sudo rm -rf /var/www/html/fog
sudo rm -rf /var/www/fog
Then rerun installer
It’s because it downloads a BIOS PXE file, when it needs an EFI PXE file.
Did you configure a DHCP server to serve this file?
The file it needs is ixpe.efi (or any other one ending in .efi)
@TCS_Taylor Does it need to stay in audit mode? Might be better off running sysprep so it can shutdown cleanly and be ready for capture.
Is this Windows 8-10? If so, turning off Fast Startup in Energy Management in Windows might also do the trick, but it might indeed be tripping up due to audit mode.
@gwhitfield If I’m not mistaken, the “Please enter tftp server” has to do with either another DHCP server conflicting or some IP helper thingy.
@pmonstad I recommend going over each step in the Wiki (check George’s post for a link) to troubleshoot FTP credentials.
Perhaps a picture would help clarify what exactly happens.
What’s your DHCP server setup like?