Your solution work pretty good, but there is one mark:
With ‘yum install partclone’ you will have the latest version, instead of this you need to download version 0.2.89 and compile it.

Please mark this topic as solved.

Thank you.

@george1421 I’m using dnsmasq 2.76.
I just tried your ltsp.conf file and it works.
Thank you very much.

@sebastian-roth oh… This Fog Project is something different from Fog Computing?
Thanks for the information. I am in search of some forum on Fog Computing where I can get some guidance on how this work in Fog Computing If you can help me with some.

Works like charm.

Thanks alot.

@msaglioc99 I don’t quite understand, you said you had already done that earlier when it wasn’t working, what changed?

@sebastian-roth It’s working now.

@taspharel

I’ll look into this - thanks again…

Jim

After I update the version of FOG I was able to image the 7240’s without issue. So issue is solved.

Yeah little tricks like that should be recorded somewhere.

Well lets start out with NAS devices are not officially supported as storage nodes. The only supported storage nodes are FOG servers configured as a storage node.

With that said, you can turn most nas devices into storage nodes as long as they can support nfs shares, a ftp server, and a tftp server. All three services must be able to point to the same storage location. I know I’ve personally configured a synology nas as a storage node.

Secondly yes you can configure a storage node in a different storage group than your master fog server. No replication will happen, but you can direct your image files to that storage group. It is much less complex to just add the space to your FOG server than doing it this way, but in theory it should work. Just be aware you can only capture to a master node in each storage group. You can not capture to storage nodes in the storage group.

Well looks like i have my answer to my problem. Thanks for the help.

@george1421 I did thoses manipulations… It didn’t works.

EDIT: wait i’ve forget to run ./installfog.sh again… And its works fine! Tanks

@wayne-workman Like i said, i remove all damaged files manually, where the base command was sudo apt-get remove xxxxx Also I may use sudo apt-get xxxx and sudo apt-get upgrade xxxx Sorry if i don´t detail my fix steps very well, my english isn’t good 😞

@george1421 only using a filled advanced menu with a handful isos nothing more. sorry

@amjfrankenstein said in sub-menus on images page for deploying images?:

…out of date and rusty

If you rest you rust 😉

@tywyn That’s the “processes” (called tasks in systemctl) that are running for the service. Those, themselves, are not tasks in the sense as you’re referring to them.

@datastream said in Active task still showing even when complete:

@george1421 At the end a window does pop up that says installation successful and it has an ok button that I have to click.

Well that is / was it. If the application never quits then FOG (as well as other deployment tools like PDQ Deploy) rely on the installer exiting with a success code to consider the application installed. The -silent or -quiet (or any other number of switches which means a silent install) are typically required for this to be a success.

Glad to help 🙂

@wayne-workman said in Changing image to a group, I get " There is a host in a tasking ":

Commands

I ran your command, it works, thanks

Next time, I will try after each command line

@jhalbert said in Snapins does not deploy:

an I reset encryption on 600 pcs? Can I use a script or is their a place where I can reset them all?

Use the web interface - put all of them into a group called “all” and use the group to reset the encryption on them all.

@wild1 said in Snapin Error:

without specifying the ip address of the Fog server the client install had a certificate error.

What exactly do you mean by that? Do you know about the installer options? See here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options