How to cleanly install Flash Player 20 cleanly with use of msi and vbs script?

[jennyb61225062]

In order to maintain updates, we push releases through means of .vbs script and SCCM. With Adobe Flash in particular we uninstall any prior version installed, then the version setup (20 for example) which is pushed silently launches. From the two recent major version releases its been noticed this method doesn't seem to be successful, as Flash Player Active X 19 and 20 fail to remove from Programs and Features rather during the push the additional Flash Player simply installs in addition to the one currently installed resulting in two Adobe Flash Player on one machine.

To uninstall we currently use /maintain activex /uninstall switch which is successful for all versions aside from version 19 and 20. As mentioned, with these it simply leaves the application within Programs and Features. We've tried the Uninstall exe, though are unable to make it silent. And at times it seems a reboot is required.

Is there something further we can do or any other steps we can try when pushing to remove these two versions? Or when using the uninstall .exe is it required to reboot between uninstall and install, and also is there a switch to make it run silently through a .bat or .vbs?

Any suggestions would be much appreciated, thank you!

[_maria_]

Hi,

What specific versions are you seeing this in?  Are you using the EXE or MSI installer?  Please provide exact steps to reproduce (including exact command-line arguments) and I will investigate further.

The uninstaller does have a silent switch, -uninstall (e.g. uninstall_flash_player.exe -uninstall) to remove only one player type, do the following:

• ActiveX Control: uninstall_flash_player.exe -uninstall activex

• NPAPI Plugin: uninstall_flash_player.exe -uninstall plugin

The Flash Player Admin Guide, http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html, contains more information on this.

--

Maria

[jennyb61225062]

m_vagas-

Thanks for the reply! In the script we ended up using the uninstall exe with both \uninstall and \force switch. The ones you recommended worked when manually running, though when push through SCCM they left multiple instances of the application in Program and Features.

I do have another question you may be able to answer. When installing Shockwave Player is there a way to disable automatic updates with either a another command switch or through an edit in the registry?

Again, thanks for your help!

[_maria_]

Hi,

Can you expand upon this comment "though when push through SCCM they left multiple instances of the application in Program and Features."?  The uninstaller should remove everything from Control Panel.

I don't work on Shockwaver Player and am not familiar with how to disable automatic updates.  You can post your question on the Adobe Shockwave Player forums.

If you're referring to disabling automatic updates for Flash Player, yes, there is a way to do this.  We recommend deploying a custom mms.cfg file disabling updates when you push through SCCM. Put the following in the mms.cfg (along with any other settings you may use in the mms.cfg) and push it along with the installer:

AutoUpdateDisable=1

SilentAutoUpdateEnable=0

The mms.cfg file is saved at the following location:

• 32-bit OS: C:/Windows/System32/Macromed/Flash
• 64-bit OS: C/Windows/SysWOW64/Macromed/Flash

--

Maria

[jennyb61225062]

When deploying through SCCM ActiveX Control: uninstall_flash_player.exe -uninstall activex wouldn't remove all previous versions from the machine before install of the newest release. Rather it would allow both versions 19 and 20 or 18 and 20 to be installed simultaneously, leaving two Adobe Flash applications installed on one machine.

[_maria_]

Hi,

Only one instance of Flash Player for a particular browser can exist on a system at any given time. 

Including 'activex' in the uninstall command will ONLY remove the ActiveX Control.  If you deploy the NPAPI plugin as well you don't need to specify the player type in the uninstall command.

What versions are you observing this behaviour in?

Can you post a screenshot of the Control Panel displaying the multiple versions after running the uninstall command?

--

Maria

[jennyb61225062]

We only push (deploy) ActiveX, so I can't speak for the plugin. But we've experienced version 18, 19 and 20 having the ability to exist on the same machine simultaneously. Meaning any of the will exists with one another: when trying to uninstall 18 the command may not remove it leaving it and adding the new releases being pushed.

[_maria_]

Hi,

Since you're only deploying the ActiveX Control there really is no need to specify activex in the uninstall command.  It doesn't hurt, but it's not necessary.  Specifying the player type in the command is mainly for people who have both ActiveX and NPAPI plugin and only one to install one type.

Regarding "we've experienced version 18, 19 and 20 having the ability to exist on the same machine simultaneously"  If Flash Player is in use during the uninstall/upgrade, some files for the previous version will remain on the system until the system is rebooted, since files in use can't be deleted.  If you're seeing previous version files in C:\Windows\System32\Macromed\Flash and/or C:\Windows\SysWOW64\Macromed\Flash this could be why.

We did have a bug last  year that the uninstaller wasn't cleaning up correctly in situations where both the EXE and MSI were used to install/upgrade the player, but that was fixed about 6 months ago or so.  But I don't think this is what you're experiencing.

Please provide the exact versions you are able to reproduce this with, including if the EXE or MSI was used to install, and steps to reproduce, and I'll try to reproduce, preferably in the following format:

It'd be great if you could provide a FlashInstall.log file from an impacted system and your .bat or .vbs script.  The FlashInstall.log file is located at C:\Windows\System32\Macromed\Flash on a 32-bit OS.  64-bit OS also has a file at C:\Windows\SysWOW64\Macromed\Flash (both files are required from a 64-bit OS).  You can upload the file(s) to cloud.acrobat.com using the instructions at How to share a document or some other file sharing service of your choice that doesn't require a log in.  Post the link to the uploaded files in your reply.

Thank you.

--

Maria