Adobe Flash Player 18.0.0.203 via Trigger

sepiemoini
Contributor III
Contributor III

I am using the Casper 9.72 and followed some instructions from a related thread to obtain the newly released Flash Player update. I signed up at Adobe's site for an administrator distribution license and downloaded a copy of Flash Player 18.0.0.203. This was then uploaded to Casper Admin and a Smart Computer Group and policy were created to carry out the software update via a "recurring check-in" trigger.

Our organization would like to push this out to users only with Adobe Flash Player 18.0 and greater so the following criteria was set in the smart group.

Application Title has "Adobe Flash Player Install Manager.app"
and
Application Version like "18.0.0"
and
Application Version is not "18.0.0.203"

After saving this group, I hit view and see that 128 computers are included in this grouping. Because we are merely testing this push for the time-being, a more narrow scope has been used.

The policy has been created and is enabled. The trigger is currently set to "recurring check-in" and the execution frequency is set to "once per computer." The correct package is selected and an "update inventory" is checked. The smart computer group is currently selected as the "target computers" and an LDAP group exclusion has been set up to only include a narrow scope of computers in my department reserved for testing. Self Service has been disabled as we would like for this to be pushed via the trigger in place.

When selecting the enabled policy, all three computers in eligible for the installation appear but have been stuck in a "pending" state all day. Any ideas on how to tweak this? This appears to be an issue with mounting.

UPDATE: one computer successfully installed this package (contents from log below).

Executing Policy Adobe Flash Player 18.0.0.203 Push...
Mounting Package Share to /Volumes/Packages...
Verifying package integrity...
Copying Adobe Flash Player 18.0.0.203...
Installing Adobe Flash Player 18.0.0.203...
Successfully installed Adobe Flash Player 18.0.0.203.

1 ACCEPTED SOLUTION

Kedgar
Contributor

This has been working for me

e247b3d9b38e479ea7e205b11433170a

View solution in original post

6 REPLIES 6

alexjdale
Valued Contributor III

I've been using a control script that evaluates Flash and installs via trigger policy to install the standard Adobe deployment pkg from a DP, and if that fails for any reason, it downloads from Adobe's FTP site. DP mount issues are too common.

That said, if it was a DP mounting issue, the logs would show that. It sounds like it's something else.

jduvalmtb
Contributor

I've always done mine like the attached file (old screen shot, but same effect), with trigger: recurring check-in & logout, Frequency: ongoing. No problems. Does require Updating Inventory to be checked. I'd check out client logs to make sure they're actually checking in with the JSS to execute policies.
ebab4a428d5e4ac2b42bc8a3d613cc36

jhalvorson
Valued Contributor

What is the frequency of your Recurring Check-in? Within the JSS, verify the number of minutes within Management Settings >> Computer Management >> Check-In to see the number of minutes.

If it is set to 15 minutes, then if the computers are awake they should check in every 15 minutes + an additional random time of 10 minutes. (I think 10 minutes is how wide of a spread that can be added to the check-in time.) As long as it can reach the JSS on the network, then it should run the policy. If you have laptops, they might be disconnect from WiFi if no one is logged in depending on how they connect to your wireless network.

Next, look at the client logs on one of the devices that is within-scope. View the contents of /private/var/logs/jamf.log to verify that it is or has recently checked in.

Also, do you have any network or time of day exclusions set in the Policy?

You don't necessarily need to include a the Update Inventory. The fact that you have it set to once per computer will limit the policy.

Kedgar
Contributor

This has been working for me

e247b3d9b38e479ea7e205b11433170a

stevevalle
Contributor III

I use a payload free installer that @rtrouton created from HERE to install flash.

Then scope it to any machine that does not have flash v18.0.0.203 installed (see image attached)

Works really well, error free!

9ef9f8dfafb4437ea10adbf15b7982f1

dstranathan
Valued Contributor II

@stevevalle

Would it be possible to run Rich's script via a "Files and Processes" Payload, rather than creating a payload-free package? Or is it not possible to run multi-line scripts via the "Files and Processes" Payload?