Flash Player 9.x
Company: Adobe
Setup Type: Native Windows Installer setup (MSI)
Package Difficulty Rating: Somewhat Easy (2) [ Rate It or View Ratings ]
Most Commonly Reported Method: Windows Installer (with Custom Transform)
Record Created On: 2/14/2008
Number of Views: 129,418
 
  
 
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.

Full Name: Adobe Flash Player 9 ActiveX

Version: 9.0.64.0

Publisher: Adobe Systems

Help: http://www.adobe.com/go/flashplayer_support/

Uninstall String: C:\WINDOWS\system32\Macromed\Flash\FlashUtil9c.exe -uninstallUnlock

Quiet Uninstall String: RunDll32 advpack.dll,LaunchINFSection C:\WINDOWS\INF\swflash.inf,DefaultUninstall,5

Categories: Internet/Business

Threat: Unknown

 
 
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.

I tried the following command to install 9.x silently with no UI over previous version 8.0.24.0:

msiexec /i install_flash_player_9.msi /qn

But, in the middle of installation, it given a dialog box saying "Uninstallation succeed" and waiting for user to press OK to continue the installation.

Above Entry Provided on 7/30/2006 by rnanda
Rate It
Rating
130

MsiExec.exe /i install_flash_player_plugin.msi /q REBOOT=ReallySuppress

Above Entry Provided on 2/13/2007 by mry
Rate It
Rating
128

For Explorer and Firefox version:
install_flash_player.exe /S (silent installation)

Above Entry Provided on 12/11/2008 by jigga_what
Rate It
Rating
16
 
 
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.

There are two MSIs, one is for Mozilla: http://download.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_plugin.msi

and one for IE:

http://download.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_active_x.msi

In our active Directory, we already deployed the previous 8.0.24.0 for both browsers with no problems, but if I try to update these packages with the new ones, the mozilla thing succeeds and the IE plugin will never get installed, the computer shows it's being installed but simply never finishes.

I tried it on several computers and on two different domains.

Can you confirm that?

I will ask adobe as well and keep you updated.

Above Entry Provided on 7/12/2006 by Enrico Palazzo
Rate It
Rating
109

Remember to put msiexec /i in the beginning of the command line...

I used:

msiexec /i \\network drive\flashplayer9.msi

...and it worked.

Above Entry Provided on 7/18/2006 by fatstinkyadmin
Rate It
Rating
114

The above command line cause the computer to reboot. If you want a silent install without rebooting, use this command instead:

msiexec /I flashplayer9.msi /qb- Reboot=ReallySuppress

Above Entry Provided on 7/19/2006 by robmo
Rate It
Rating
115

Adobe confirmed that this is a problem with upgrading 8.0.24 - There exists a newer version of 8.0.40.0 which differs in size and does not contain this error when upgrading to 9.

For Adobe had no solution for me, I had to ask every user to hit the reset switch when his computer hung on "removing Flash Player Active X Plugin (V8.0.23.0)". After the reset, Flash 9 gets installed alright and 8.0.24.0 is nowhere to be found.

Above Entry Provided on 8/23/2006 by Enrico Palazzo
Rate It
Rating
2

Adobe now has an uninstall utility that will cleanly remove old versions of Flash Player.
-------------------------------------------

Run the uninstall utility prior to your Flash Player V9 installation. I have successfully uninstalled these versions of the Flash Player on a Windows XP SP2 machine:

Flash Player 6.0.84
Flash Player 8.0.22
Flash Player 8.0.24

Note: The utility closes open Internet Explorer Browser windows as part of its process
-------------------------------------------

I used a batch file (see below) that checks for Flash Player, runs the uninstall if needed, followed by the Flash Player 9 install. This worked fine for me.

-------------------------------------------
REM This command uninstalls Older version of Flash. It then installs Flash Player V9


:CHECKFLASHLEGACY
REM This will uninstall a legacy Flash Player
if exist "C:\WINDOWS\system32\Macromed\Flash\flash.ocx" (goto DELETEFLASHLEGACY) ELSE (goto CHECKFLASH8X)

:DELETEFLASHLEGACY
uninstall_flash_player.exe /silent

:CHECKFLASH8X
REM This will remove an advertised version of Flash 8
if exist "C:\WINDOWS\Installer\{6815FCDD-401D-481E-BA88-31B4754C2B46}" (goto UNINSTALLFLASH8X) ELSE (goto INSTALLFLASH9)

:UNINSTALLFLASH8X
uninstall_flash_player.exe /silent

INSTALLFLASH9
msiexec.exe /i install_flash_player_active_x.msi /qb

:EOF
-------------------------------------------

The Adobe Flash Player Uninstaller is available for download from Adobes website:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_14157

Good Luck!

Above Entry Provided on 9/19/2006 by MooreJD
Rate It
Rating
117

I had mixed results deploying the plug-in using this command line:

msiexec /I flashplayer9.msi /qb- Reboot=ReallySuppress

I tried different switches for the reduced UI level- /qb!, /qn, /qr, etc., and did not have a good success rate at all- maybe 50/50. However, on some of the same that were not installing correctly I ran the installation with no UI switches, manually clicked through the installation prompts and the program installed properly. This was kind of confusing...

I turning on logging (/L+ *logfilename*)for the installation I noticed that the same error was appearing in the logs for the failed installations:

GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3

I dug around for a while and it seemed like most of the information regarding the error led back to the InstallShield website formus. I read about some fixes being done by changing the DCOM execute privileges from "Interactive User" to "Launching User" in the InstallShield InstallDriver objects by running dcomcnfg.exe. Changing that setting prior to running the installation did not work for me either.

I was never able to find a clear answer for the error in the InstallShield forums or the Adobe forums, but what I did come to learn is that flash player installation was created using InstallShield, and because of that it relies on the InstallShield InstallScript engine. So, I changed my Flash player install script to first install the latest Install Script engine (v.11) before installing the Flash Player msi and boom- 100% success on hundreds of PCs.

So the procedure that worked for me is:

1. MsiExec.exe /i InstallDir\ISScript11.Msi /qb!
2. MsiExec.exe /i InstallDir\install_flash_player_9_active_x.msi REBOOT=ReallySuppress /qb! /L+ LogDir\Flash9msi.log

Notes:

-I registered and downloaded the redistributable corporate version of the flash player install.

-I downloaded the InstallScript engine from here: http://consumer.installshield.com/kb.asp?id=Q108322 (Click the link for ISScript11.zip)

Hope this can be of use.

SodaPop

Above Entry Provided on 11/25/2006 by SodaPopinski
Rate It
Rating
118

Managing Flash Player auto-update

Flash Player supports auto-updating itself by periodically checking for new versions of the player on the macromedia.com site. IT administrators can customize the parameters of this update.

The auto-update settings can be configured in two ways:

User settings in Flash Player
mms.cfg file in user's "home" directory
Users can disable the auto-update process or set the periodicity of the checks by using the properties panel in Flash Player. These user-configured auto-update settings are stored in a local shared object.

The second method for configuring the auto-update settings is to create a file named mms.cfg. The mms.cfg file is intended to be configured by an IT administrator and stored on the user's computer. The file is not created by Flash Player installation. You might use a third-party administration tools, such as Microsoft System Management Server, to replicate the configuration file to the user's desktop.

Store the mms.cfg file in the following location, depending on your operating system:
Windows NT, 2K C:/WINNT/System32
Windows XP C:/WINDOWS/System32
Windows 95, 98, or ME C:/Windows/System
Macintosh /Application Support/Macromedia
The format of the mms.cfg file is a series of name=value pairs separated by carriage returns. If a parameter is not set in the file, Flash Player assumes the default value. When set, values in this file override the user-configured settings.

The following table describes settings in the mms.cfg file:

AutoUpdateDisable
0 allows auto-update based on user settings.
1 disables auto-update.

AutoUpdateInstallerUrl
String specifies URL as download location for player update.

If this parameter is not set, Flash Player uses the Macromedia server.

AutoUpdateInterval
0 checks for updates every time the player launches.
>0 specifies the minimum number of days between check for updates.

AutoUpdateSettingsUrl
String specifies URL as destination for "Settings..." button in auto-update dialog. If this parameter is not set, Flash Player uses the Macromedia server.

AutoUpdateVersionUrl
Specifies the URL to retrieve XML file containing Flash Player update data. If this parameter is not set, the player uses the Macromedia server.

To disable the auto-update:
Open the mms.cfg file in a text editor.
Add the following auto-update setting:

AutoUpdateDisable=1

Save the mms.cfg file.

Close and restart Flash Player or the browser in which Flash Player is running.

You are not required to remove any other settings so that you can re-enable the auto-update feature and restore your original settings by removing this line (or setting its value to 0).

Above Entry Provided on 2/14/2008 by Axel
Rate It
Rating
121

In reference to the above, according to Adobe the file needs to be placed in %Systemroot%\system32\macromed\flash for versions greater than 8.x.

Above Entry Provided on 2/14/2008 by MGordon
Rate It
Rating
118

Here's a vbscript that runs the Flash Uninstaller, then installs the ActiveX version of Flash for everyone, then checks for a Mozilla or Netscape product, and if one is found, installs the plugin version of flash. To work, it needs to be in a directory with the adobe flash installer MSIs for both the ActiveX and Plugin versions of the player, and the uninstaller. I had better results with this (running the uninstaller for everyone) than using the batch file above -- I am deploying this through Altiris, set to run only when no one is logged in, so as not to force browsers to close. The script itself is short -- the longer function that's part of it might be useful in other situations, though--it tells you whether or not software is installed by searching the registry. This version is a fuzzy search -- you could make it an exact search by changing the InStr function to an exact comparison.

Option Explicit
Dim objWshShell

Set objWshShell = WScript.CreateObject("WScript.Shell")

objWshShell.Run "uninstall_flash_player.exe /silent", 1, True

objWshShell.Run "msiexec /i install_flash_player_active_x.msi REBOOT=REALLYSUPPRESS /qn", 1, True

If ((FuzzyIsInstalled ("Mozilla")) OR _
(FuzzyIsInstalled ("Netscape"))) _
Then
objWshShell.Run "msiexec /i install_flash_player_plugin.msi REBOOT=REALLYSUPPRESS /qn", 1, True
End If


Function FuzzyIsInstalled(strfSearchDisplayName)

' *********************************************************
' Purpose: Tells whether a piece of software is installed.
' Rather than looking for an exact match, this version searches
' for installed software that contains the search string.
' So searching for Mozilla will return true if Mozilla Firefox
' Is installed.
' Inputs: strfSearchDisplayName: the Display Name of the
' software to be searched for.
' Returns: A boolean saying whether or not the software
' is installed
' *********************************************************

dim strfComputer, strfKeyPath, fSubKey, strfFoundDisplayName
dim intfRet
dim blnfFoundYet
dim arrfSubKeys
dim objfReg
const HKEY_LOCAL_MACHINE = &H80000002

strfComputer = "."
strfKeyPath = "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\"
blnfFoundYet = False
Set objfReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strfComputer & "\root\default:StdRegProv")
objfReg.EnumKey HKEY_LOCAL_MACHINE, strfKeyPath, arrfSubKeys

For Each fSubKey in arrfSubKeys
intfRet = objfReg.GetStringValue(HKEY_LOCAL_MACHINE, strfKeyPath & fSubKey, "DisplayName", strfFoundDisplayName)
If intfRet = 0 Then
objfReg.GetStringValue HKEY_LOCAL_MACHINE, strfKeyPath & fSubkey, "DisplayName", strfFoundDisplayName
If (inStr (strfFoundDisplayName, strfSearchDisplayName) > 0) Then
blnfFoundYet = True
End If
End If
Next

FuzzyIsInstalled = blnfFoundYet
End Function

Above Entry Provided on 2/23/2007 by Matthew Dessem
Rate It
Rating
118

This is of possible relevance to those of us fighting with flash 9 that don't have a repackager: I got this working installing the msi manually, then "borrowing" the .ocx file installed in the windows directory. You can then push that file out to your clients and manually register it via a regsvr32 call.

For windows XP, that's all I found that was needed. It's cheating, to be sure. But it works, and that's all I was after. :D

Above Entry Provided on 3/9/2007 by skennedy95356
Rate It
Rating
3

To successfully deploy using Zenworks 7, use the Distribution Options/distribution scripts tab, and do something like:

if not exist %windir%\version, md %windir%\version
if not exist %windir%\version\flash9, md %windir%\version\flash9
xcopy \\%zserver%\apps\flash\flash9\*.* %windir%\version\flash9\*.* /s /e /i /y
c:
cd %windir%\version\flash9
msiexec.exe /iflash9.msi /lie %windir%\version\flash9b.log REBOOT=ReallySuppress /qb+
xcopy "%windir%\version\flash9\mms.cfg" "%windir%\system32\macromed\flash*.*" /y

This will copy the msi and the mms.cfg(to stop the upgrade window)to a local drive. The application object is now run as unsecure system user. This will work even on a corrupt install from my testing.

Above Entry Provided on 3/16/2007 by macdj2
Rate It
Rating
118

Installing the latest Flash Player will not necessarily remove all previous versions. Even running the latest Flash Player Uninstaller (http://download.macromedia.com/pub/flashplayer/current/uninstall_flash_player.exe">uninstall_flash_player.exe) did not remove the old Flash 6 Active X control, which was the one that has the known exploit. (Thanks to Secunia Software Inspector (http://secunia.com/software_inspector), for catching this).

So, once you have a Flash Player 9 or later installed for Internet Explorer, you'll have a flash9*.ocx Active X control in %SystemRoot%\system32\Macromed\Flash. If so, and you also have an old Flash.ocx in that same location, delete the old Flash.ocx.

My old Flash.ocx was dated 8/04/2004 and was 832872 bytes, but yours may be different. There were no references to Flash.ocx in the registry, so deleting it affected nothing.

Above Entry Provided on 2/14/2008 by snissen
Rate It
Rating
117

This article finally got us up and running.
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=4a8d52ae#msi_zap

Adobe had links to this utility that finally allowed us to deploy 9 and remove 8 silently without that stupid pop up. I had tried using just the uninstall utility to cleanup 8 but I would still get the pop up(Very Annoying!!). This was preventing me from being able to deploy this though SMS silently.

MsiZap Tool
http://support.microsoft.com/kb/290301/en-us

I installed the utility and grabbed MsiZap.exe out of my program files\windows installer cleanup utility directory.

I then created a wise script to copy MsiZap.exe to c:\temp\ and execute the command below.

Using this command to remove Flash 8.0.24.0 "c:\temp\MsiZap.exe" T {5E8A1B08-0FBD-4543-9646-F2C2D0D05750}

After that I used the uninstall_flash_player.exe /s to remove any existing files. Found here http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_14157.

I was then able to run the install_flash_player_active_x.msi /qn

Above Entry Provided on 6/4/2007 by jmx600
Rate It
Rating
118

Attempted to install the new 9.0.45 version this morning as an upgrade to 9.0.28. Regardless of switches used (/qn, /qb-, /qb!, with and without msiexec /i) the install would hang with a remote silent install of the .msi version.

Finally decided to cut my time losses and installed using the .exe version with the /s switch. It removed the previous version and installed perfectly.

Above Entry Provided on 6/20/2007 by Babscoole
Rate It
Rating
120

One issue that I've found is a Windows Update for a Flash 6 vulnerability.

http://support.microsoft.com/kb/923789

Installing this update may cause the later versions of Flash to fail.

Above Entry Provided on 8/29/2007 by BenD
Rate It
Rating
118

Also had problems upgrading 9.0.16 and 9.0.28 to 9.0.47
Found that the 9.x versions set some strange deny permissions in the registry, so you must uninstall previous version before installing newest. here's the script I used: (Note that 9.0.28 was a managed package of ours)

On Error Resume Next

Dim oWSHNetwork, oWSHShell, oFSO, oWSHUserEnv
Dim sUserName, sSystemFolder, sPreviousVersion, sPreviousKey, sRemoveCommand, sInstallCommand

'===================================

sPreviousKey = "HKLM\Software\Jonesday\Installations\Flash9"
sRemoveCommand = "C:\WINDOWS\system32\msiexec.exe /X{67BC8539-246D-47EA-AF13-65BF6005C19C} /QB-!"
sInstallCommand = "C:\WINDOWS\system32\msiexec.exe /I ""Flash Player 9.0.47.msi"" /qb-!"

'===================================

Set oFSO = CreateObject("Scripting.FileSystemObject")
Set oWSHShell = CreateObject("Wscript.Shell")

'Remove Flash 9.0.16
If oFSO.FileExists("C:\WINDOWS\system32\Macromed\Flash\UninstFl.exe") Then
oWSHShell.Run "C:\WINDOWS\system32\Macromed\Flash\UninstFl.exe -q",0,1
End If

'Remove Flash 9.0.28
sPreviousversion = oWSHShell.RegRead(sPreviousKey)
If Err.number = 0 Then
oWSHShell.Run sRemoveCommand,1,1
End If

'Remove Unmanaged Flash 9.0.47
If oFSO.FileExists("C:\WINDOWS\system32\Macromed\Flash\uninstall_activeX.exe") Then
oWSHShell.Run "C:\WINDOWS\system32\Macromed\Flash\uninstall_activeX.exe",0,1
oWSHShell.Sleep 5000
End If

'Install Flash 9.0.47
oWSHShell.Run sInstallCommand,1,1

Set oFSO = Nothing
Set oWSHShell = Nothing

Above Entry Provided on 9/25/2007 by rlgura
Rate It
Rating
117

http://www.adobe.com/go/6b3af6c9

Flash Player support on 64-bit operating systems
Issue

Flash Player is not supported for playback in a 64-bit browser. However, you can run Flash Player in a 32-bit browser running on a 64-bit operating system.

Reason

Adobe is working on Flash Player support for 64-bit platforms as part of our ongoing commitment to the cross-platform compatibility of Flash Player. We have not yet announced timing or release dates.


Solution

To use Flash Player to view Flash content on a 64-bit operating system, you must run a 32-bit browser.

Above Entry Provided on 2/14/2008 by nzdude
Rate It
Rating
118

Just a 'helper' for people suffering with the InstallShield error touched on above:

[quote]I dug around for a while and it seemed like most of the information regarding the error led back to the InstallShield website formus. I read about some fixes being done by changing the DCOM execute privileges from "Interactive User" to "Launching User" in the InstallShield InstallDriver objects by running dcomcnfg.exe. Changing that setting prior to running the installation did not work for me either.[/quote]

If, after changing the 'Identity' with DCOMCNFG, you still get similar errors, try setting the relevant Custom Action to run in User context instead of System. It worked for me.

Above Entry Provided on 1/28/2008 by VBScab
Rate It
Rating
116

If you only need the Internet Explorer plugin of Flash player you have to download the MSI file.
I cannot find it on Adobe's homepage so I've tried Google and found it (install_flash_player_active_x.msi).

After that you will have a native MSI package for deployment. You do not need any special MSI Features. Maybe only /qb for silent installation.

Above Entry Provided on 2/14/2008 by kaos.dll
Rate It
Rating
117

Without a doubt most of you, if not all, are technically more adept than I am but I wanted to note about the comments that 9.0.x will not update via Group Policy correctly.

I too have seen this behavior. However, when I set the new version's GPO to Update the prior version GPO AND set it to Uninstall the prior GPO before installing the new GPO AND ensure that the new GPO's link is sequentially AFTER the old GPO it works. I have not tested to know if the Uninstall portion is required, but the sequencing absolutely is critical. If the new GPO executes before your pre-existing GPO nothing happens with the new version... no side-by-side, duplications, etc. that I have seen.

Anyways, just wanted to comment that upgrading v9 can be done without scripts or frustration.

Above Entry Provided on 2/14/2008 by RLRPC
Rate It
Rating
118

Notes about testing auto-update and how to make sure it is disabled (using MMS.CFG as posted above by Axel):

I Started a VM session and installed Flash 9.0.47 (latest is 9.0.115). Added MMS.CFG to C:\WINDOWS\SYSTEM32\MACROMED\FLASH with AutoUpdateDisable=1. Visited a website with Flash, verified that Flash loaded by right clicking and seeing the Flash 9 pop up menu. Rebooted VM session. No update prompt as expected.

Edited MMS.CFG and changed AutoUpdateDisable to 0 and AutoUpdateInterval=0. Visited website with Flash, verified that Flash loaded and closed IE. Checked registry and the following entry was added:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce]
"FlashPlayerUpdate"="C:\\WINDOWS\\system32\\Macromed\\Flash\\FlashUtil9d.exe"

Rebooted and of course, received an update prompt telling the user that an update is available and asking to install now or remind later or don't install.

Above Entry Provided on 5/15/2008 by MicrosoftBob
Rate It
Rating
117

Had an issue installing Adobe's msi of Flash Player for Firefox 9.0.124 via GPO, it appeared to deploy/install ok but would still be prompted in Firefox that I did not have the correct version of flash installed. The solution was to make sure that the installation order via GPO was Firefox > Flash not Flash > Firefox.

A useful free tool to order existing GPO entries is Assigned Software Sequence Manager.

Above Entry Provided on 8/1/2008 by Sguilly
Rate It
Rating
117

@echo off
@TITLE Install / Uninstall / Upgrade :: Adobe FLASH Player :: Version 9,0,124,0
:: Remark: Language Independant
::
:: Author : DaMAN
:: Company: ComputerGenie
::
:: * Request Adobe Flash Player Distribution at: http://www.adobe.com/products/players/fpsh_distribution1.html
:: * and download the latest version for:
:: - Mozilla Firefox Plugin:
:: #1: http://download.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_plugin.msi
:: #2: http://fpdownload.macromedia.com/get/flashplayer/currrent/install_flash_player.exe
:: - Internet Explorer - ActiveX:
:: http://download.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_active_x.msi
:: * Check if Adobe Flasher is installed succesfully: http://www.adobe.com/shockwave/download/flash/completion/en/0/
::
:: * Adobe KB: How to uninstall the Adobe Flash Player plug-in and ActiveX control:
:: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14157
::
:: Version: 1.0
:: Release date: 05-10-2008
::
:: History:
:: v1.0 - First Production

IF EXIST %WINDIR%\system32\Macromed\Flash\NPSWF32.dll GOTO UNINSTALL

:INSTALL
@TITLE Installing Adobe Flash Player...
@ECHO Installation of Adobe Flash Player for: Internet Explorer (ActiveX), Mozilla Firefox
@ECHO Note: A restart of IE is not nessasary. But restart of Firefox is required!

msiexec.exe /qr /i "install_flash_player_active_x.msi"
"install_flash_player.exe" /s
GOTO END

:UNINSTALL
@TITLE Uninstalling/Upgrading Adobe Flash Player...
"uninstall_flash_player.exe" /s
msiexec.exe /qn /uninstall "install_flash_player_active_x.msi"
GOTO INSTALL

:END

Above Entry Provided on 10/6/2008 by DaMAN
Rate It
Rating
2

Command-line flags for FlashUtil.exe:

The utility file FlashUtil.exe is installed with Flash Player 9.0.28.0 and later in the C:\Windows\system32\Macromed\Flash directory. FlashUtil.exe includes functionality required by Windows Vista and by the auto-update notification process. The previous utility (UninstFl.exe) is no longer required by or installed with Flash Player.

The utility is versioned with the control. For example, FlashUtil9b.exe is installed with the control Flash9b.ocx. FlashUtil.exe also contains several options that developers can use to switch between player and debugger versions during testing. Developers can modify the default behavior by using the following command-line flags:

USAGE : %s [-uninstallUnlock] [-uninstallLock] [-uninstallControlPath] path]

* If run with no flags , the auto-update notification dialog will appear.
* -uninstallUnlock: unlock the control. Grant write/delete permission to OCX and registry keys without erasing files.
* -uninstallLock: lock the control. Deny write/delete permission.
* -uninstallControlPath path: Optional; override the default path to the control. Must be used in conjunction with one of the other flags. If omitted, the path is located based on registry information.

Reference : http://kb.adobe.com/selfservice/viewContent.do?externalId=4da116d3

Above Entry Provided on 4/13/2009 by rayz_0020
Rate It
Rating
0

Apr 2010 - SILENT uninstall Flash Player 10 ActiveX:

First, downloaded uninstaller from http://kb2.adobe.com/cps/141/tn_14157.html

Then, launch with silent switch:

uninstall_flash_player.exe /silent

Above Entry Provided on 4/29/2010 by PaulieD
Rate It
Rating
0

It seemes that the /silent switch has been removed in the latest version of uninstall_flash_player.exe

Above Entry Provided on 8/11/2010 by McBear
Rate It
Rating
0
 
 
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
 
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.

If you are using Zenworks to distribute in a locked-down environment, it will not install, even using "Run as System User" (secured or unsecured).

To fix this, edit the .msi file and remove AdminUser from LaunchCondition section. I used Orca.

Above Entry Provided on 8/14/2006 by rascal
Rate It
Rating
118

For a non-admin user these key and sub keys need change permissions.

HKEY_CLASSES_ROOT\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000}
HKEY_CLASSES_ROOT\CLSID\{D27CDB70-AE6D-11cf-96B8-444553540000}
HKEY_CLASSES_ROOT\CLSID\{1171A62F-05D2-11D1-83FC-00A0C9089C5A}
HKEY_CLASSES_ROOT\TypeLib\{D27CDB6B-AE6D-11CF-96B8-444553540000}

Above Entry Provided on 2/14/2008 by wmanser
Rate It
Rating
5

Note that for a 64 bit server these keys are under HKCR\Wow6432Node\CLSID

Above Entry Provided on 2/14/2008 by jonshelton
Rate It
Rating
117
 
 
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.

 


Report a problem
  Printer Friendly Version