Hi All,
JSS/Casper Newbie here, I have been tasked to do a Adobe Flash Player update and would like to know what the best practise to import and distribute Adobe Flash Player and it needs to be a scheduled?
Thanks
SEN73
Hi All,
JSS/Casper Newbie here, I have been tasked to do a Adobe Flash Player update and would like to know what the best practise to import and distribute Adobe Flash Player and it needs to be a scheduled?
Thanks
SEN73
@ernstcs][/url wrote:
Having Flash, or any Adobe product for that matter, just automatically update itself when a new version comes out? No thanks. There is this thing called testing...
Automagically deploying untested updates is a good way to violate corporate security mandates, can cost a company a lot of money, and goes without saynig may get someone in a whole lot of trouble.
@gregneagle wrote:
We've chosen software management systems like Casper to manage the software on our Macs. It should be fast and easy to manage updates for managed software.
...or Munki, or Absolute, or Filewave. Irrespective of the tool used, someone's got to vet the stuff before it goes out.
Don
Basically this...
Follow this page: https://jamfnation.jamfsoftware.com/viewProduct.html?id=41&view=info
Download the PKG when a new one is available. Dump it into your (hopefully a QA) JSS and go through whatever testing procedures are required of you. If you have none...scary voodoo, man.
Once tested (vetted as @donmontalvo uses) upload into Production JSS.
Update smart group that looks for Macs that DO NOT HAVE this new version number you updated for the group based on Extension Attribute for Flash version, and NOT the package Casper has deployed if your users have admin. I noticed there wasn't an official Extension Attribute on the above site, but just submitted this for approval:
#!/bin/sh
#
############################################################################
#
# Extension Attribute checks to display Adobe Flash Player Version number.
#
#
############################################################################
FlashPluginVersion=`/usr/bin/defaults read /Library/Internet Plug-Ins/Flash Player.plugin/Contents/Info CFBundleVersion`
echo "<result> $FlashPluginVersion </result>"
exit 0
Go to the policy that pushes it out and update it's deploy scope (like if you set the policy to expire at some point, which I recommend) and then flush the policy history.
Follow-up at pre-determined time, likely the next Flash update you'll get in about a week or less, with systems that did not update correctly.
Rinse and repeat.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.