Nope it’s still heavily in the beta phase, I bet when we do have an idea we will post it on the forums or on the main site letting everyone know we are close. There is a thread you are more than welcome to monitor it can be located here ->http://fogproject.org/forum/threads/latest-fog-0-33b.6476/
I can also confirm, with multiple pieces of hardware (In this case, Dell Optiplex 790, Dell E7450, Lenovo Thinkpad T520, and Thinkpad X140e), that zstd and 1.4 will give me sub 5 min deploys of a fully configured Win10 image, including Office, Adobe Suite, and all Win. Updates.
I routinely deploy to 100+ devices a week, in both uni and multi cast. Fog server is an old P4 with 4 gigs of ram and 4 nics in a LACP bridge.
Thank you very much for your replies. I think that the complexity of implementing this kind of security measure doesn’t worth the time. Perhaps just restricting access to several subnets is more than enough.
I will go that way.
yes I looked at fog transfert code too because I managed to connect glpi and fog but it’s not working further
and I’m not good enough with mysql to correct what’s wrong
anyway thanks for the tip of csv import
@Malos I must have been really under the weather when I escalated to the devs.
I actually know the answer. Currently the way replication works due to a bug in lftp concerning only replacing changed bits (remember that one @tom-elliott? ), If a change or difference is detected between the source file and destination file, the destination file is deleted and the copy is re-started.
There is going to still be a “trunk” branch and I’ll still be doing (albeit much less than in the past) work on the PHP side of FOG, but really limited to bug fixes and minor improvements. I don’t expect any new features to be added unless it’s to support some new functionality in regards to the new FOG Client that we find useful enough to be added to the current channel’s of FOG.
As we get closer and closer to a functional element of FOG 2.0 (which will likely take a while) we’ll most likely give up postings to try to get our testers and other developers updated to test and report things.