@ManofValor Yep clonezilla to a local usb hard drive. For the physical machines that is the easiest route.

I’ve imaged Ubuntu 15, CentOS 7, and Fedora 21-23 many times.

Ubuntu defaults to extfs while in Fedora 21-23 you can select Ext4 as the filesystem to use.

This is important because FOG only supports ext type file system resizing in Linux. (and only ntfs resizing in windows).

I’m not sure what puppy uses… but it should work as non-resizable at the very least.

Sebastian is on the right path, though. Follow his instructions.

@Timo Seams like we haven’t implemented a shutdown after snapin… Not sure if @Tom-Elliott is keen to add this right now. Other than that you can create a SFX including a windows cmd script to shutdown the machines after running the installer. See here for an example on how to create an SFX installer.

@Tom-Elliott Thanks for the quick help, can confirm it is fixed.

@jheikkila54 said:

@Wayne-Workman
Alright good news, I got everything working! First thing, connecting to the mysql server as ‘fogstorage’ on the main server will not work, fogstorage has host access from % (which includes all IP addresses except for localhost.) In order to get this working, this is what I had done (in-case anyone else runs into this)

Verify that the node cannot communicate with the main MySQL server
mysql -u fogstorage -h (your main servers DNS/IP address) -p
enter your fogstorage password and hit enter If you do not successfully log in, then you need to change your passwords. Go to the webpage of the main fog server and go to Fog Configuration->Fog Settings->Configure Storage Nodes Set the username to fogstorage and the password to whatever you want SSH into the main fog server Connect to the local MySQL server as root
mysql -u root -p
enter password (default is a blank password) and hit enter Change the fogstorage user password
use fog;
UPDATE mysql.user SET Password=PASSWORD(‘the new passord’) WHERE User=‘fogstorage’;
FLUSH PRIVILEGES;
exit; Test that you can connect to the mysql server by doing step 1 again. If you can connect successfully now, you should be working, if not please try removing and reinstalling fog and ensuring you use the correct mysql username and password during the install phase

This is already covered here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Enable_remote_mysql_access

@raice Your instructions would be greatly appreciated, the more the better! We can compare notes and come up with the best solution!

And for your environment, yes, being able to install windows from the network on many different models of PCs is the best option for you! I imagine you are a fan of Fog’s “Quick Image” feature that doesn’t require a registered computer, eh?

@Tom-Elliott Thank you. I removed / reinstalled vsftpd, and tested ftp as per https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords - deleted the image, the image dir, the host, and set all of it back up again. The new capture was successful.

@Hanz Thanks a lot for your answer! I’ll mark this solved for now but please keep us posted if you see it happen again!!

@Wayne-Workman said:

https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

Great job!! Especially since a picture is worth a 1000 words (as they say).

@Sebastian-Roth Hello
for the moment i didnt make any test about multicast.
But it’s planed
I will tell you
I have to look on switch configuration

@danilopinotti Is this still an issue or can we make this solved? Have you tried upgrading to the very latest version, re-upload and deploy again?

@TThax I am marking this solved as I guess you have got a new image ready by now. As well Tom and I have worked on getting those dell recovery partitions right as well. Upgrade to the latest version and test if you like.

@KJ-You I am marking this as solved as the initial question about kernel update/version is… Feel free to post again and open a new thread if you have another issue.

Well I didn’t solve it.

@Tom-Elliott Still running like a champ. So I do greatly appreciate it. You allowed me to go home and not have ot manually dis-join and rejoin every machine in the building by hand

@Scott-Adams Latest trunk version is around 65xx. Maybe this has been addressed already? As hostname changes happen through the client I suppose it would be interesting to know which client version you use right now and which you have used back then?

@Tom-Elliott said:

Can you update to the latest and see if this is still happening?

Updating to 6549 seems to have worked, funny it didn’t ask me to update/upgrade the database, just went straight to login. But I’m deploying an image so I’m happy! Thank you!! I will try that first next time, just thought if it was working yesterday it should still be working if I didn’t make any changes.

Working great now after moving to the Trunk. I was pleasantly surprised with how well the upgrade process worked. All I had to do after the update was reconfigure some of my settings for dnsmasq and then I was up and running.

Thank you for your help @Wayne-Workman !

@boeleke In your screen shots, it looks like the Image Path and the FTP Path are backwards. Usually, the FTP Path contains the entire path, while the NFS Path starts in the exact shared NFS Folder.

-EDIT-
Just read that @ch3i solved it. Good job ch3i!

ok guys. first of all… tnx for the quick responses!

dont blame me. i rebooted the machine and tried once more… exactly the same… and it worked !!!

no clue, what happened… but tnx for your replies - u are quicker than a gunshot 😉