«
»

Deploy Adobe Flash Player Updates with SCUP 4.5

Kent Agerlund - 9th August 2009

When deploying Adobe Flash Player updates with SCUP 4.5 you might run into a few problems with the installation of the update. My work around to fix that is by creating the update from scratch. In this post I assume that you have a working SCUP 4.5 environment up and running. The update being deployed is install_flash_player_ax.exe version 10.0.32.18 which can be downloaded from http://www.adobe.com/support/flash/downloads.html 

 

Open SCUP and select Create Update image
Type:
Update Title:
Adobe Flash Player 10 10.0.32.18
Describtion:
Something nice
Classification:
Critical Update
Bulletin ID:
APBB09-10
Vendor:
Adobe Systems, Inc.
Product:
Adobe Flash Player 10

Click Next

 image
Type:
Article ID:
APSB09-10
CVE ID:
CVE-2009-1862, CVE-2009-0901, CVE-2009-2
Severity:
Critical
Support URL: http://www.adobe.com/support/flashplayer/
More Info URL: http://www.adobe.com/go/apsb09-10
Impact: Normal
Reboot Behavior: Never Reboots

Click Next

 image
Click Next

Creating a preequisites rule is not needed. But it can be very beneficial to define the Operating systems and versions you wish to update.

 image
In Installer type select Command line installation (.Exe)

In Update Package Source:
Browse to the network location where you have the file. Just copy the entire UNC including the file name.

In Download URL:
Copy the location from the package source

Binary Language:
English
Success Code:
0
Success Pending Reboot Code:
3010
Command line:
/s

Click Next

 image
In DefineApplicability rules click the yellow plus sign to create a new rule.

Rule type:
Registry version in Sz
Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows\CurrentVersion\Uninstall\Adobe Flash Player ActiveX
Registry value: Displayversion
Use 32 bit Registry
True
Comparison:
Less than
Version
10.0.32.18

Click OK when the rule is created and Click Next

 image
In Define Installed rules click the yellow plus sign to create a new rule.

Rule type:
Registry version in Sz
Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows\CurrentVersion\Uninstall\Adobe Flash Player ActiveX
Registry value: Displayversion
Use 32 bit Registry
True
Comparison: 
Equal to 
Version
10.0.32.18

Click OK when the rule is created and Click Next

 image
Click Next and Close image
The update is now created in SCUP and needs to be published. Right click the update and select Set Publish Flag, Full Content image
In the Actions Pane select Publish Update(s).  
Click Next image
Click Close image
The update will automatically be replicated to Config Mgr. in the next WSUS Sync schedule. You can force the sync process in the Config Mgr. console. Navigate to Computer Management, Software Updates. Right click Software Reporsitory and click Run Synchronization image
You can monitor the sync process in the wsyncmgr.log file on the site server. image
The update is now in Config Mgr. and ready to be deployed like any other Windows Update. image
On the client (if you have visible deployments) it should like this image
image
Category: Custom Updates, Software Updates  |  Comment (RSS)

6 Comments

  1. Raj:

    What is the advantage of using SCUP to deploy flash player vs using SCCM’s software distribution to deploy flash player?

    29th December 2009, 22:41
  2. Kent Agerlund

    Kent Agerlund:

    Hi,
    The advantage is that you will have the update as part of your “normal” compliance” reports and that the update can be deployed as an update.

    30th December 2009, 07:39

  3. JoeVS:

    How did you disable the local automatic updates from Flash Player with this distribution?

    8th February 2010, 17:19

  4. SCCM SCUP: How to Install Adobe Flash Player 10.1.53.64 | Richard Balsley:

    [...] to install the Active X component for IE systems using the provided MSI file with SCUP. I’ve read in a few places that it’s best to utilize the .exe instead of the .msi that is provided by [...]

    16th June 2010, 04:15
  5. Kent Agerlund

    Kent Agerlund:

    Hi JoeVS,
    Sorry for the late answer, somehow I didn’t see you question. I create a file called mms.cfg with this line

    AutoUpdateDisable=1

    The file is then placed in C:\windows\system32\Macromed\Flash (or SYSwow64)

    17th June 2010, 11:16

  6. Roger:

    How are you copying mms.cfg over?

    When I deploy currently using software distribution I am able to run a script that does multiple things. SCUP is geared toward running a msi or exe. The only solution I see is repackage the msi (not something I want to do) or compile my script into an executable and use scup to deploy that.

    4th August 2010, 01:00

Leave a comment