Is this a new problem? Has it worked in the past and just quit?

Ask your local computer resellers or support companies. One of them may be familiar with FOG.

For reference, the ONLY time you use FOGCrypt on a password is when setting the user credentials for joining computers to AD. All the other passwords in the FOG settings and config files are in plain text. I know some of them look encoded, but they are just random strings made complex enough so they are not easily guessed from 1 FOG install to the next.

All you really needed to do what reset the password for the “fog” user in the WEB ui, which you can do through mysql command line if you can login to the fog server.

You need to set the passwords in the /var/www/fog/commons/config.php and the web UI.
[LIST=1]
[]open /var/www/fog/commons/config.php
[]set the TFTP_FTP_PASSWORD, doesn’t have to be complex, but write it down.
[]set the STORAGE_FTP_PASSWORD to the same value as TFTP_FTP_PASSWORD.
[]save the file.
[]from the command line: sudo passwd fog
[]Enter the same value you used for TFTP_FTP_PASSWORD and STORAGE_FTP_PASSWORD
[]open the FOG web UI.
[]login as user: fog
[]go to other information, FOG Settings
[]Go down to the TFTP Server section, make sure the FOG_TFTP_FTP_PASSWORD value matches the TFTP_FTP_PASSWORD value from step 2
[]Save changes
[]Schedule a task and see if it works.
[/LIST]
In FOG 0.32, some settings are duplicated between the config files and the database. So you have to make sure both spots are updated or you have weird problems. It’s getting cleaned up for the next version I think, but for now, change the values in both the web UI and the config files.

After hours upon hours of trying to figure out a config file parameter I may be missing, that dummy file workaround is music to my ears. Thanks a lot!

You set it in the fog settings, pxe boot menu settings. You have to enter a master password before you can set any of the sub-passwords.

I had actually done all 3 of those things with no luck. I ended up getting the root MySQL account password removed and updated the files again to use root with no password and all of the sudden, everything worked.

Are your storage nodes accessible from the main fog server? Can you ping and FTP to them?

I blew the installation and set up Ubuntu 10.4 and it worked fine.

The only difference with the Debian is that I set up a password for the root user for MySQL on Debian (and created a user that was granted all rights to the whole DB; and provided that information in the fog config file as explained).

Thanks anyway 🙂

You’re going to run into index value overlaps or orphaned data in other tables. You’ll need to modify the data before you import it. Basically you’ll update the hostid in the hosts table and all tables that reference that value. Then you can import the data into all the existing database.

I’d be willing to work with you on this, but I don’t think it’s going to be quick and easy.

Okay, I think I might know where the problem lies. When I try to run cupsaddsmb to add the printer drivers to the Samba I get a “[I]NT_STATUS_UNSUCCESSFUL” [/I]error. I’m not sure where to go from here though. [I][/I]

You know what? ive been a complete numpty. I should have tested it before I asked for help.

If I press a keystroke is aborts the automatic boot and I can select the options.

Thank you so much for your help though regardless, youve got my FOG up, running and useable, your a legend.

Thank You Chad I did do this at your last suggestion and that is how i was able to add the new virtual drive.
Guess i missed the last move step but its working!!

Thank you for all your help

If you are going to be isolated to any switch and not connected to the rest of the network then you must enable DHCP on the FOG server in order to answer PXEboot requests. It doesn’t matter if you use the 4 port wireless router, but you need to disable DHCP service on the router when you are trying to PXEboot, or you have to jump through hoops to get them two systems working together ([URL=‘http://www.fogproject.org/wiki/index.php/Setting_up_ProxyDHCP’]proxydhcp[/URL])

The command line is all there in the wiki article. You’ll fdisk to find the disk and set the type, then you’ll make the filesystem, then you’ll move the images folder to images1, create a new images folder, mount the new virtual disk to the /images folder, then move the images from /images1 to /images

So after I uploaded one of my existing images successfully, I made a new image and uploaded the contents of the VM to it.

Now it works. One thing I noticed is FOG can see two partitions rather than just one which is all it was seeing before. I’m not sure FOG can only see one partition on the disk I was using previously. I didn’t do anything different to prep it this time.

Ahh okay – yeah I had been eyeing the wiki article about buildroot: ([url]http://www.fogproject.org/wiki/index.php/Build_FOG_file_system_with_BuildRoot_-_init.gz[/url])

I was holding off on diving in to that, since I was hoping there would be a way to mount the init.gz, import the installation (somehow or another), and gzip init back up without having to rebuild the whole thing. But if there’s no other way, then that’s what I’ll do.

I think you have a valid argument for your boss to change his opinion about volume licenses. 125 images per computer must be hard to manage no matter where you store them.