I would like to use the File Synchronization to drop Office sources on end-users computers. Problem is that I will have to frequently refresh those sources because of minor build releases (security updates, etc).
I've downloaded my sources, I've created the File Sync task but it seems that the file is being downloaded at each agent inventory, even if my custom inventory rule is verified.
I would like to know if I well understood File Sync and if it will match with my need. Here is what I was expecting from it :
1 - Extract the sources (a .zip file) on a client computer (Verified)
2 - Check the integrity by comparing hash (idk)
3 - If the folder exists, stop downloading to the device (Going wrong)
4 (Bonus) - If I change the source, overwrite what is already in the destination repository (comparing hashes)
Thank you by advance ! :)
Why are you dumping the source files on computers opposed to dynamically pulling whatever the latest build is or using a network share?
We decided to push sources on computers to allow quick rollback if needed. Office Suite is a major asset for our user's productivity and if something has not been detected during the qualification of the major build and creates issues, we want to be able to rollback to the previous major build with one script and without any download delay from a server.
We used to push a freezed version on the computer since last year, letting minor updates being installed on the side. I was looking for an improvment to always push the latest version on computers by using File Synchronization. - Nioky 1 year ago