@herb said in FOG, what can and can't it do?:

Q2: Can Images be deployed that I did not capture?

The short answer is No. You must capture the image from FOG to deploy it.

There is no central repository for OS images. You must create your own, based on your own requirements from DVD. In my company’s case we use MDT to build our golden image then capture and deploy with FOG. A hardware agnostic design is surely possible. We have a single image that we deploy to 15 different models in our fleet of computers. The key/trick is to use a FOG post install script to copy the correct drivers to a defined location on the target computer just after deployment, but before the first OS boot. Once the drivers are at the precise location then windows will detect them and load them. Sometimes we find that we need to use dism in the the setupcomplete.cmd to finish injecting the drivers after oobe but before first login. It does take time to setup your environment but once done you can regenerate your golden image at any time with the latest windows updates if you use MDT.

@merilious Do you already have a fogproject directory? If you are on an RC release I might say yes.

It might be in /root/fogproject or /opt/fogproject depending on who’s instructions you followed. If you can find that fogproject directory, then the update process is simple.

cd /root/fogproject
git pull
git checkout master
cd bin
./installfog.sh

You will need to do a checkout master because you were on a rc branch.

@merilious OK I just wanted to make sure that the password was blank. Then the instructions in the thread are spot on. Go ahead and follow the steps. Then you probably should update to current 1.4.0 had several issues with single disk resizable that was fixed in 1.4.1. But for now you need to get control of your fog server.

@merilious I want you to open a linux command prompt and review the settings in /opt/fog/.fogsettings especially the field snmysqlpass what is the value currently?

@merilious Since it WAS working and magically, IS NOT working AND you are running ubuntu this thread probably applies: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

But before you go and follow this thread blindly lets get some background information.

ok I want you to run the following command from a windows computer browser.

http://10.100.10.22/fog/service/ipxe/boot.php?mac=00:1c:42:86:14:c4
Post the output here.

I worked with the OP over DM for quite a while and then setup a TV session. The root cause here is that ubuntu is the enemy of fog (bug). Then during the execution of the ALTER USER step in the link I provided below the password for the mysql root user became confused. We ran through the mysql root user password reset process to reset the password which worked. But the upgrade still failed to backup the current database. Long story short, there was a second background mysql process running causing the process the fog installer was managing to fail causing the backup of the database to fail. Once we found this back ground mysql process running we killed it and then restarted mysql. This time the install succeeded as designed.

Case closed.

@elias-santiago As part of that post did you also execute the ALTER user command? If so the password for the root user is now <blank>.

If you can no longer log into the mysql server using a known password (or blank) then you will need to follow the process to reset the root account for mysql: https://support.rackspace.com/how-to/mysql-resetting-a-lost-mysql-root-password/

@elias-santiago just to confirm one more time. You know the password to log into mysql using mysql -u root -p fog right? If you can have your confirmed in your /opt/fog/.fogsettings file that snmysqluser='root' and snmysqlpass= the password you used to login to mysql and snmysqlhost='127.0.0.1'

There is something wrong here. The error says the .fogsettings file is wrong.

@elias-santiago In the same directory as the installfog.sh script, there is a log directory. In that directory there should be an error log file for the version you are currently installing. See if that log file contains why the backup failed.