Adobe Flash Player 18.0.0.203

Download the System admin version from (sign up as well btw)

https://www.adobe.com/products/flashplayer/distribution3.html

Sign up at Adobe's site for an administrator distribution license. You'll get a link to a full standard package installer you can use instead of messing with their silly .app installer.

http://www.adobe.com/products/players/flash-player-distribution.html

Excellent. Both answers work and are exactly what I needed. Thank you!

I incorporated a fallback option to curl down the DMG from Adobe and install manually if our Flash update scripts fail for any reason (DP mount failure, pkg not found or verified, etc). We're doing a fast push for this right now since it's kind of a big deal.

#!/bin/sh

curl https://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_player_18_osx_pkg.dmg -o /tmp/FlashUpd.dmg
wait
if [ -f /tmp/FlashUpd.dmg ]; then
    hdiutil attach /tmp/FlashUpd.dmg -mountpoint /Volumes/FlashUpdateVOL -nobrowse
    installer -target / -pkg "/Volumes/FlashUpdateVOL/Install Adobe Flash Player.pkg"
    umount /Volumes/FlashUpdateVOL
 else
    echo "Could not find Flash installer DMG"
fi

Why you no use AutoPkg?

autopkg run AdobeFlashPlayer.pkg

or with some additional setup:

autopkg run AdobeFlashPlayer.jss

http://autopkg.github.io/autopkg/
http://www.lindegroup.com/autopkgr

I've never been able to figure AutoPkg/AutoPkgr out.

AutoPkgr + JSS:

JNUC 2014

Auto Update Magic

We utilize in our test environment and it's very helpful!

So I use Composer to create a snapshot DMG and then use this as a base for all further updates. The advantage of this is that you can push out the update, even if the browsers are open. Invariably the only thing that changes in an update is the Flash Player.plugin file

+1 for AutoPkgr. Though admittedly I tend to go right to Adobe for the Flash distributor if I hear about the update before the recipe gets updated.

I simply deploy the administrator pkg that Adobe distributes. It can be installed while browsers are open, but that doesn't mean they will start using the new plugin version without a relaunch.

In my testing, after installing the pkg Safari needs to be quit and relaunched to start using the new plugin version, but Firefox does not. After installing, I prompt users to quit Safari and give them 15 minutes before I killall Safari.

I'm honestly not sure what AutoPkgr brings to the table for Flash, apart from maybe adjusting the pkg metadata for consistency and putting it into the JSS for you. The pkg itself is perfectly fine to drop into Casper Admin.

There's also rtrouton's autoupdate script, which I prefer. Upon new updates, I just flush all logs, and new update gets installed on recurring checkin.