Skip to main content
Jamf Nation, hosted by Jamf, is the largest Apple IT management community in the world. Dialog with your fellow IT professionals, gain insight about Apple device deployments, share best practices and bounce ideas off each other. Join the conversation.
9

Adobe Flash through Policy

Posted: 3/20/17 at 3:55 PM by sabrina.oconnor

I know this has been discussed in regards to auto updating via a script. (https://www.jamf.com/jamf-nation/discussions/18495/best-way-to-set-flash-player-to-auto-update-your-thoughts)

However, I have not found anything recent for updating flash through a policy. I'm fairly new in JSS (really new and fumble my way through), I have Chrome and FF updating with the newest package I've made. With the configurations I've made, Flash of course does not install, when I try to push as an update, it sits at root and does not install.

I was wondering if someone could point in the right direction for updating Flash (and Java) as well as getting it to install during imaging (without dropping it at root).

We discussed the above script but want to have a bit of hands on, so we can test and make sure it does not affect. The patch reporting was nice for Chrome & FF, since I could use "less than" and go from there, of course that is not available.

Ideas? Thoughts?

Thanks all! :)

9
CCA Badge

Posted: 3/20/17 at 4:32 PM by Mhomar

@sabrina.oconnor are you dropping the Flash.dmg file in Casper Admin then deploying the .dmg via a policy? You should be using this file (Download DMG Installer (for System Administrators)) this is a link that contains the .pkg. Put the Flash.pkg file into Casper Admin then use that file in the deployment Policy payload. PS... in order to get this file (that contains the .pkg) from Adobe, you must apply for and be accepted for Flash distribution. this is the link for you application if you do not already have it. http://www.adobe.com/products/players/flash-player-distribution.html

Posted: 3/20/17 at 5:11 PM by rqomsiya

Why not use AutoPKG/AutoPkgr? It makes the packaging portion of the flash player a breeze. Simply drop the .pkg file in Casper Admin and deploy.

Here is a great link from @rtrouton: https://derflounder.wordpress.com/2014/07/15/autopkgr-a-gui-for-autopkg/

CCA Badge CJA Badge

Posted: 3/21/17 at 3:01 PM by Chris_Hafner

I've got to second @Mhomar That's the way we do it and it's super easy! You do have to dig into the java installer to get a proper .pkg but it's always been something that I was able to simply drag and drop into Casper Admin, and set to install in a policy scoped to a smart group. You could use AutoPKG of course. I never went that route because it was quite a bit of work that left me trusting in lists maintained by other non-commercial entities (i.e. people who I couldn't hold responsible for screw-ups).

Here's what I do:

•) Sign up for the adobe distribution license via the link •) Download the PPAPI and NPAPI flash.dmg for "Systems Administrators"
•) Open the .dmg and drag the .pkg somewhere. Your desktop or a folder
•) Rename the package so that the new version number is part of the name (otherwise you're going to have trouble tracking which flash .plg is which) In my case "Install Adobe Flash Player.pkg" becomes "Adobe-Flash-Player-25.0.0.127.pkg" and "Adobe-Pepper-Flash-Player-25.0.0.127.pkg" respectively.
•) Drag those two .pkg's into Casper Admin
•) At a minimum, assign them to a category and give them an install priority
•) Save, and replicate from Casper Admin

POLICY
•) Create a policy that installs both flash player .pkg's •) Scope that policy to the computers you wish to get the update. I use a SMART Group that includes everyone that doesn't have the version of Flash Player. I have an Extension Attribute that reports on the Flash player version. I can help you on that too if you need it.

SOLVED Posted: 3/21/17 at 4:11 PM by sabrina.oconnor

Hey All - Thanks for all the suggestions. It pointed me in the right direction. We actually already had one of our accounts signed up for the Adobe distribution. Grabbed the dmg (or co-worker did for me). It didn't show a pkg. I put that into composer and pkged it. Uploaded it to JSS, tied it to a policy pushed it out to a few test computers. Dropped into root but didn't install.

Next I went to the auto packager. Grabbed it from github, uploaded the pkg to jss, tied that into a policy and this time it at least installed, still dropped it at root though.

Added in a clean up script:

rm -rf Install\ Adobe\ Flash\ Player.app/

Then it was happy. Installed, no left over installer sitting on the computer. Finally good.

Thanks everyone for all the help and pointing me in the right direction. I greatly appreciate it :)

Now I'll follow the same steps to get Java going. :D

CCT Badge CCA Badge CJA Badge

Posted: 3/21/17 at 4:26 PM by duffcalifornia

So, just as a different take, even though you've marked this solved:

I install the Distribution package on my own machine, then use Composer to create a package from preinstalled software, then remove the user folder and create a DMG.

I then create a smart group that says "Flash is less than [insert current version number], then create a policy to install the newly created DMG with a scope of the Needs Flash Updated smart group.

Wash, rinse, repeat every time Flash updates.

CCA Badge CJA Badge

Posted: Yesterday at 8:14 AM by Chris_Hafner

I've got to jump back in here. Why would any of you install and then repackage a perfectly good .pkg installer? Additionally, it's perfectly fine that this installs as root. That's how policies work, they install with root privilege unless you script them otherwise.

Posted: Yesterday at 10:01 AM by sabrina.oconnor

@Chris_Hafner it was more of not wanting the installer sitting in root, vs it installing at root. After it was installed, the installer was still sitting there. Which I believe ended up being another issue. I need to further test today to be sure.

Posted: Yesterday at 10:01 AM by sabrina.oconnor

@Chris_Hafner it was more of not wanting the installer sitting in root, vs it installing at root. After it was installed, the installer was still sitting there. Which I believe ended up being another issue. I need to further test today to be sure.

Posted: Yesterday at 10:17 AM by sabrina.oconnor