My Outer Monologue

Blocking Adobe Flash Player Automatic Updates With Group Policy.

In a previous post, I discussed deploying Adobe Flash Player in an enterprise environment. I also mentioned that in order to disable the automatic update feature of Flash, you should create an MST transform file to install a custom mms.cfg.

This is all well and good, unless you are intending on installing the EXE version of Flash, and not the MSI.

Usually, I’d go MSI over EXE any day of the week, but Flash Player is a fickle b*tch of an install. For some reason, I was seeing plenty of MSI installations fail while using SCCM 2007. Most of the failures related to certain files not being marked for installation. The following event log entry could be observed on the machines.

Product: Adobe Flash Player 10 ActiveX — Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\DOCUME~1\<username>\LOCALS~1\Temp\InstallAX.exe, command: -install activex -msi

For this reason, I bailed out and went with the EXE installation, which so far, when used with the new silent install switch (-install) works flawlessly.

Now, obviously we can’t transform an EXE, so I’ve had to come up with the following CMD script which can be applied to computer startup through the use of a Group Policy Object.

ECHO AutoUpdateDisable=1 > %WinDir%\System32\Macromed\Flash\mms.cfg
ECHO DisableProductDownload=1 >> %WinDir%\System32\Macromed\Flash\mms.cfg

The nice thing about this script is that it will only run if the Macromed folder exists.

Tags: , , , Posted in Deployment
3 comments. | July 26th, 2010 by Tom |

Comments.

  1. [...] Update: You might want to check out this more recent article which discusses a more reliable method of insta… [...]

  2. 15/10/2010 at 21:22
    Ryan Steele says:

    Thanks for this! I’m deploying the MSI with a Software Installation GPO but creating a transform seemed like a big hassle. The only thing I’m worried about is that the .cfg file will stick around even when the policy has been removed, which could result in some confusion if we ever went back to having users performing their own Flash player updates, but we’ll fall off that cliff when we come to it I suppose.

  3. 19/10/2011 at 08:30
    Kristof Bernaert says:

    It is still possible to document installations, updates, changes … to know in future what was done and how to undo things …

    @ssstofff

Leave a comment.

Recent Photos

img064 img063 img062 img061 img060 img059

Twitter Updates

Recent Comments

Categories