Problem has been solved. Looks like there was two other things he needed to do that solved the problem for him, so his server is now working normally.

Hi all,

We currently have 2 FOG servers setup, one that I setup with the default configuration to learn on, and one another person here setup for a subnet of computers they maintain.

They changed the fog linux password, so we went through and made adjustments per the forums and this page: [url]http://www.fogproject.org/wiki/index.php/Password_Central[/url] to the GUI configuration and the config.php file.

Everything seemed to be working fine at this point (they were able to create a task and start the upload process and then they got the message:

image uploaded
task complete
FTP connection to storage server has failed

Which makes no sense - it was able to connect to the ftp server to add the MAC address to initiate the task, but the client can’t connect to change it back? The password is set to what it should be afaik in the GUI (does it normally display it in plain text or should it md5 the password or what?), the only thing we didn’t change was the FOG quick Image password stored in the pxe boot image since it stated that it will be overridden by the settings in the gui. Any suggestions as to where to look would be most appreciated!!

x23: Thanks, using that seemed to solve my problem - I appreciate the info - I hadn’t even noticed that entry, I’m still really new to FOG

Hi all,

I’m experimenting with FOG on a specific system and had an odd issue I’m hoping someone can help me with.

The target machine has 2 hard drives (sda and sdb)

Process:

Setup a basic install of windows 7 on sda. Formatted sdb to act as extra storage

Image created using Single drive method that recorded all partitions of sda

Normal wipe pushed and performed on sda

Image deploy to the machine.

I expected the image to be deployed to the sda drive (as I didn’t remove the drive from the system and it was the drive that the image was originally made from) but instead it imaged to the sdb drive. This is NOT a good thing as I would like to be able to have a second drive in this system that would contain data that if the OS was corrupted and needed to be re-deployed that the data drive would remain untouched, but FOG seemed to completely ignore the wiped drive and instead installed on the drive that would be designated for data.

Granted this wasn’t a production setting (had it been, this would have been REALLY bad) - I was wondering if anyone had any tips on how to make sure that sda is restored to sda even if the sda drive was wiped…