+11http://www.adobe.com/products/flashplayer/distribution3.html shows that lash Player 15.0.0.152 is now available.
However, if you download the .pgk DMG the installer is still 14.0.0.176
This is the direct link - http://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_player_14_osx_pkg.dmg
Best answer by jcurrin
Here is the new version link http://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_player_15_osx_pkg.dmg
+24Yeah, not a surprise. The FlashPlayer auto update xml is also still listing version 14.0.0.176. Adobe has been pretty horrible at actually getting all their resources updated to the same version in a timely manner. This kind of disconnect seems to happen with every Flash update. Give it until later today or tomorrow and they should have it fixed
+13Here is the new version link http://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_player_15_osx_pkg.dmg
Changed @rtrouton's Flash script from 14 to 15 in the fileURL and it's working as expected, fyi.
https://github.com/rtrouton/rtrouton_scripts/tree/master/rtrouton_scripts/install_latest_adobe_flash_player
If folks are using the latest version of my script, it should now be downloading Adobe Flash Player 15.0.0.152 as of a few hours ago. I updated the script in July so that it now automatically grabs the latest major version number from Adobe's update feed and plugs it into the correct place for the fileURL value. If you're still using a previous version of my script, I recommend getting the latest.
It wasn't getting 15.0.0.152 this morning because Adobe had not yet updated the update feed from listing 14.0.0.176 to 15.0.0.152. Now that Adobe updated the feed, it should be good to go.
+16Rich your script works perfect , same for the java onces ....... Looking for a Silverlight autoupdater :)
+21Also, you do have the ability to update the Flash Player third party page with new info if you are sure about it. =D
+16I kept getting an error that the policy (running this script) failed. I discovered the problem is not with the script (it installs the latest version fine), but the reporting mechanism in the JSS that returns a "failed" value.
The word "error" appears in the output of the installer because this Mac has a mounted volume that does not have an OS on it.
JS: Flash Player Install: Performing volume check for /Volumes/Backup HD
Sep 12 07:47:00 name.company.org installer[2664] : JS: Flash Player Install: Error: Non-OS Volume detected.
The JSS sees that and flags it as the policy failed, even though the script completes like this:
installer: Running installer actions…
installer:
installer: Finishing the Installation….....
installer:
#
installer: The software was successfully installed......
installer: The upgrade was successful.
"disk3" unmounted.
"disk3" ejected.
I have users running the policy over and over, thinking it failed, then creating a Help Desk ticket, and it is working the whole time. I don't want them to ignore failed policies, but they have no way to know… Ideas?
I addressed this in my own shop by using a payload-free package to run the script. The logging from the package installation process goes to /var/log/install.log, so the JSS's reporting never sees the "error" output.
I have a payload-free package for the script available from here:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
