The power of the script comes from a case statement that sets a large number of variables to use as the script runs, which is set by whatever is passed in Parameter 4. The ReadMe has most of the information you need to understand how it works, but if anyone has questions on it, feel free to ask. Its the first script mentioned in the ReadMe, 'Update_Core_Apps.sh' which you can get to directly with this link: I've posted the script that I mentioned above to my github page now. The script also has both a silent mode and a Self Service mode, which uses cocoaDialog for dialogs, progress bars and feedback, etc. Its just a flag you can set in the script to install new or skip if not installed. If its not installed, in all cases except for Office since those are only updaters, it can install it new. The script checks the installed version and will know if it needs to be updated. My primary reason for working on it was that I was getting tired of needing to build complex Smart Groups to target the right machines with package install policies. If bandwidth use is not a concern, then it can be an option. For this reason, if internet bandwidth usage is a concern, then this wouldn't be a good solution. It will direct the client to download and install the product directly. In all above cases, it doesn't require any packaging of the apps or plug-ins. That said, I have a single script that can be used to update up to 8 different apps/plug-ins, including Flash Player, Oracle's Java, Silverlight, Adobe Reader, VLC, Flip4Mac (free version), Office 2011 and Firefox. However, everyone's needs and/or tolerances for what should be something packaged and contained in the JSS, versus just allowing the clients to download and install the latest version, will be unique. Autopkg would make the most sense overall to use for this purpose.

Firefox update