Adobe Flash Player 11.6.602.167

http://fpdownload.macromedia.com/get/flashplayer/pdc/11.6.602.167/install_flash_player_osx.dmg is the offline installer.

you do realize @colonelpanic the email you get from adobe asks you very nicely not to share that information with people right?

Thanks @colonelpanic for sharing this, keep up the good work.

you do realize @colonelpanic the email you get from adobe asks you very nicely not to share that information with people right?

I don't get an e-mail from them, I just found a link to an older version and had been placing the new version number into the URL and checking to see if it works. I was not aware Adobe does not want that shared. I'm assuming you get the e-mail you are referring to, do they say why? If that is private information I can stop posting the links.

I have not received notification yet interestingly enough.

Andl if you are smart enough to have found it on your own and you have not registered to be deploying Adobe applications like Greg Neagle posted you should, then, maybe brilliant ignorance will work out well :)

from their email when you register

You may not share the above link, share information with others, or publish the above link on websites, blogs, or by any other means that can be publicly accessed. The information contained on this site is meant for your use only in accordance with Adobe Flash Player Distribution License Agreement you accepted. You may direct others to http://www.adobe.com/products/players/fpsh_distribution1.html to request distribution rights.

All I did to find a direct download link was look at a prior Flash download link from my Safari history and substitute the version number. It works. Does that mean I'm bound by something I did not see nor sign?

Seems a little extreme, no?

And since when do laws make sense?

It's listed at http://www.macupdate.com/app/mac/4783/adobe-flash-player as non-beta. So how is this not for public consumption?

Hi.
Adobe has a program for TechAdmin to get these .pkg installers, but you have to sign up and agree not to share.
I signed up yesterday and got access same day.
http://www.adobe.com/products/players/flash-player-distribution.html
S

I'm part of the program and I still get the .app installer, not a pkg. Also, the URL he posted is not the one that you get when you sign up for the developer program, it is close, but slightly different. I downloaded from both the link from Adobe and from the Colonel and they both appear to be the same package (same size, same mod date, etc).

I believe the reason why they want you to register is because you are bypassing the additional installers that can come with Flash (bloat-ware) that comes mainly with the windows installers (setting default search engines, banners, anti-virus trials, etc). The developer account gives you access to bypass all of that and only install the plugin.

@damienbarrett I would ping Misha and let him know to update the MacUpdate listing, this happens all the time.

11.6.x is beta.

http://linkedin.com/in/mishasak

Don

11.6.602.167 is the current release as of today, per this security bulletin:

http://www.adobe.com/support/security/bulletins/apsb13-05.html

I just downloaded Flash from the Adobe webpage and got version 11.6.602.167

@rtrouton I stand corrected...

http://get.adobe.com/flashplayer/

Wow, the Flash Player team are spitting out updates like they're PEZ dispensers.

Wouldn't it be nice if they put their efforts into fixing the cr@ppy installer instead? Oops...I forgot...

PS, notice Joe Consumer now gets the full installer DMG...

external image link

We don't worry about the frequent Flash plug-in updates anymore. We turned on the auto update mechanism for it on all managed clients and we are beginning to see some Macs already with this new version with zero effort on our part.
We're OK with leaving Flash to auto update, since its really not going to break anything major on our side. Java is a slightly different story...

@mm2270 wrote:

We don't worry about the frequent Flash plug-in updates anymore. We turned on the auto update mechanism for it on all managed clients and we are beginning to see some Macs already with this new version with zero effort on our part. We're OK with leaving Flash to auto update, since its really not going to break anything major on our side. Java is a slightly different story...

Yep, and there's a thread on the ARD list where some folks decided to extract the PKG from the installer *.app breaking the auto update. I guess to each thier own, we've wrapped the *.app and trigger the install using Adobe's (wonky) install command, works fine.

Don

@mm2270: Are your users admins on the machines?

Mine have been auto updating until today. I'm assuming that's because admin credentials are not needed for point releases, but are for major releases.

I was reading a lot on this when 11.5 was released and I seem to remember Adobe stating somewhere (I can't find the source) that the auto updater will wait 30 days for credentials and then perform it anyway.

Either way, what I'm doing is deploying the /Library/Application Support/Macromedia/mms.cfg file in a DMG package, then the Adobe installer.pkg. This is not disabling the automatic updates.

@donmontalvo

Care to share the syntax for the Adobe Installer inside of Install Adobe Flash Player.app/Contents/MacOS?

@hkim, this is the way we deploy the Flash plug-in. I assume the process Don is using is basically the same:

1- Create a folder in /private/tmp/ called "FlashPlayer"
2 - Edit the "Install Adobe Flash Player.app"'s Info.plist file (inside /Contents/) by adding the following to the end:

<key>NSUIElement</key>
<string>1</string>

The above entry makes the installer invisible, as in no Dock icon, so you can deploy it silently (as long as someone is logged in)
3- Copy the modified "Install Adobe Flash Player.app" into the /private/tmp/FlashPlayer/ folder
4a- (Optional step): Set Flash to auto-update on a Mac with it installed and create another package that deploys the "mms.cfg" configuration into /Library/Application Support/Macromedia/ from Composer. (This file sets the auto update prefs)
4b- Copy the above pkg install into /private/tmp/FlashPlayer/
5- Create a new Composer package (blank) and drag the 2 files from above into the window. You should have "Install Adobe Flash Player.app" and "mms.cfg" (or whatever you named it) in the list under /private/tmp/FlashPlayer/
6- Create a post install script in your Composer package with these contents:

#!/bin/sh
## postinstall

pathToScript=$0
pathToPackage=$1
targetLocation=$2
targetVolume=$3

/private/tmp/FlashPlayer/Install Adobe Flash Player.app/Contents/MacOS/Adobe Flash Player Install Manager -install

/usr/sbin/installer -pkg /private/tmp/FlashPlayer/FlashPlayer_mms.cfg.pkg -target /

sleep 2

rm -R /private/tmp/FlashPlayer

exit 0      ## Success
exit 1      ## Failure

The above will install Flash and then the configuration package to set auto update on, and finally clean up the folder in /tmp/. It uses Adobe's admittedly wacky but effective install process so all the pieces get put in place properly.

If you decide not to deploy a mms.cfg file, just edit out the line in the script above that would be calling that install.
Edit: you could of course deploy this file with auto update turned off if that's what you want, and would be more important than the former use, since the default setting is to have it on anyway. We just push it out as part of our package for good measure. :)

Hope that helps.

I'm doing it exactly like mm2270 these days, with the exception that I'm placing the mms.cfg file in /Library/Application Support/Macromedia using the same package as the one that executes the adobe installer. In my testing, the installer didn't create the mms.cfg, so I didn't see a need to package it separately.

mm2270, did you see something in your testing that made the 2nd package for mms.cfg necessary?

@nkalister - no, not really. I had created that package to push to Macs that were already running an up to date version (11.3.x or higher) so we could set it "on" for them. I only included it in the full install so I could be certain the auto update process was enabled. We likely could leave that out and it would be fine. But I've seen nothing negative by including it.

It would be great to have a policy template that creates a temporary admin account so we can push software that requires a logged in user, but to logged off Macs. The jamf binary can create/delete an admin account, but we haven't found a way to log that account in during a push, and log the account off after the push, then commit suicide. Is it something obvious that we're missing? :)

What is the program with Adobe For TechAdmins?

@TheMacGuys wrote:

What is the program with Adobe For TechAdmins?

Huh?

I, like @mm2270, package the file separately. I mainly do it so that I don't have to worry about it with each release.