Banjo,

That error occurs when the SQL database information doesn’t match what is in fog. This is what I would suggest doing.
[LIST]
[]Open up [CODE]sudo nano /var/www/fog/lib/fog/Config.class.php[/CODE]
[LIST]
[]Notate both the host, username & password
[/LIST]
[]Open up [CODE]sudo nano /opt/fog/.fogsettings[/CODE]
[LIST]
[]Fill in the following portions
[/LIST]
[/LIST]
snmysqluser=“{root}”
snmysqlpass=“{password if you have one}”
snmysqlhost=“{localhost}”
[LIST]
[]Reset the mySQL database password to be what is in the config files
[LIST]
[]run [CODE]sudo dpkg-reconfigure mysql-server-5.5[/CODE] replace the last two numbers if using a different version of mySQL
[*]enter in the new password
[/LIST]
[/LIST]
If you still have issues re-run the installer. I tested with a VM using 14.04 and it resolved the same issue

Boot one of the computers that are ready registered into fog boot menu select “Client System Information” and then “Show DMI Information”. When you do that does the missing information show up? If it does show the information have you updated fog after the clients were added? I am not sure but maybe those fields are newer and if the host was already registered it wouldn’t update the database unless you remove the host and re do a full host register.

log into your fog web page and go to “Fog Configuration” (question mark) then click on “PXE Boot Menu” it is the last option change it and then click “Save PXE MENU”

On the host if you select host compatibility and then host information does the information populate?

You could also check to see if it pulled this information by installing webmin [url]http://www.webmin.com/download.html[/url]. This would allow you to look at the SQL database data if you do install do the following to look at the table to see if the data was pulled or if it is just not pulling in the report. If you do install follow these steps
[LIST]
[]login with root account
[]Click on Servers
[]Click on MySQL Database Server
[]Click on fog
[]under “Edit table” click on “Inventory”
[]It will then open the table where you could either export the data into CSV or view the data in the browser
[/LIST]

Disable UEFI by setting the computer to legacy mode in bios, and change the “exit to hard drive type” from I assuming “Sanboot style” to "Grub "

You can also check the ftp password in the GUI under Fog Configuration/Fog Settings/TFTP Server/FOG_TFTP_FTP_Password and make sure it matches what is in Storage Management/{Your Storage Node}/Management Password.

It sounds like a issue with boot record on the boot computer you used to upload. Check out post 6 and after on [url]http://fogproject.org/forum/threads/stuck-on-dev-sda.11105/[/url]

Could you give a more information on what it does when you try to boot? What OS are you deploying? Are you using legacy bios or UEFI?

Its a javascript item I would think that could be modified to always show maximized instead of show on hover. I am not familiar enough with javascript to change it myself. The file that looks that would need to be modified to change this is located in /var/www/fog/management/js/fog.tasks.js

So I take it if “it was working before” you could image but you were having issues after deployment with the machine just boot looping through fog?

Maybe try this post [url]http://fogproject.org/forum/threads/chainloading-ipxe.10915/[/url]

Sysprep is normally for used in when you know a computer will be added to a domain due to it resets the Security Identifier, Driver Cache, and Computer Name for example. If you want to create a universal image check out [url]http://www.fogproject.org/wiki/index.php/Create_a_windows_7_image_for_many_different_hardware[/url]

Fog uses kernels basically as an interface to pass commands or pull information off of a computer. It doesn’t install the kernel to the computer you are imaging

Hope this helps

It seems like a lot of people run into issues like this when building an image on a physical machine. I would recommend by starting off by wiping all partitions out with a gparted disc and then making sure BIOS is set to legacy mode (at least until UEFI issues are resolved) and then install Windows. It would prevent issues like this from occurring