Software Deployment

Yes, this has been like this for a while. Here's what we do at deploy.no to create a setup that lets you install both Firefox and Opera before or after Shockwave and still have it working. Some of this is in the knowledgebase but this will get you from start to finish

- Register at Adobe and download the "corporate" setup in two variants, the "msi" and the "slim" setups. You will be needing the slim setup to support Firefox and Opera.
- Use Orca or another tool to create a transform and

Fix the setPROFILE CA in the CustomAction table (which really must be a bug):
setPROFILE 35 PROFILE [AppDataFolder]\Macromedia\Shockwave Player\

Change these HKLM registry settings to prevent autoupdate and sats collection (phone home):
SOFTWARE\Macromedia\Shockwave 10\CollectStats n
SOFTWARE\Macromedia\Shockwave 10\AutoUpdate n
SOFTWARE\Macromedia\Shockwave 10\uicontrol\AlwaysRegister n
SOFTWARE\Macromedia\Shockwave 10\uicontrol\CollectStatistics n
SOFTWARE\Macromedia\Shockwave 10\CollectStatistics n

This msi+mst combo will work with both AD GPO and SMS and give you Shockwave in IE.

- The slim setup is a zipped executable, unpack the files NP32DSW.DLL and SHOCKWAVEPLUGIN.CLASS from it.
- Now, for Firefox and Opera, we author a new msi based on these two files:

In your msi editor, create a new component called Firefox or something with the base dir at [SystemFolder]\Macromed\Shockwave 10. Add the two files to this component. This is the same dir where the Adobe-provided msi has put its files and for some reason we'll probably never know chose to ignore Firefox. Shame! on them.

Add these registry settings to your component to enable Firefox to see the plugin at browser startup:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins]

[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer10]
"Description"="Adobe Shockwave Player 10"
"Path"="c:\WINDOWS\system32\Macromed\Shockwave 10\NP32DSW.DLL"
"ProductName"="Adobe Shockwave Player"
"Vendor"="Adobe Systems Inc."
"Version"="10.1.4.20"

[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer10\MimeTypes]

[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer10\MimeTypes\application/x-director]
"Description"="Shockwave Movie"
"Suffixes"="dir,dxr,dcr"

[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer10\Suffixes]
"dir"=""
"dxr"=""
"dcr"=""

These are documented well here http://developer.mozilla.org/en/docs/Plugins:_The_first_install_problem

Opera doesn't have this way of knowing where to find the plugins from the registry so we have to cheat a little. Create a new component which puts the same two files hardcoded to [ProgramFiles]/Opera/program/plugins. For purists that will probably taste bad as there will be an Opera dir in ProgramFiles even if you don't have Opera installed, but hey, why bother complicating things when this solution is the simplest and easiest =)

- Install the vendor msi first, then install your custom msi with the extra files. Provided you have done this right you don't have to bother with dependencies or installing browser first then plugins.


Good luck!

If I install Shockwave using MSI over network:
IE works
FF does not work

If I install Shockwave using MSI locally:
IE works
FF does not work

If I install Shockwave using EXE locally:
IE works
FF works

I just downloaded the EXE version of the shockwave installer (Shockwave_Installer_Slim.exe, which installs for any browser that might be installed; we only have Firefox and IE on our workstations) and captured the install into an MSI. It places files into ProgramFilesFolder\Mozilla Firefox\plugins\ and SystemFolder\Macromed\. In my installation it also put files into my Thunderbird directory, which I excluded. It also does a bunch of registry things. If you can capture the setup, you can either create a new MSI (which is what I did - made it a dependent object in ZENworks) or create a transform that includes all that information (probably cleaner).

Hi Mike,
i read your post doubtfully and checked the Shockwave MSI. And, unbelievable, there is no logic, no files, just nothing to support the mozilla-based browsers!
And no single word about this in a readme or something!
Regards, Nick

Just so folks are aware, the technique mentioned above for Opera, also works for FireFox. That is you can just copy NP32DSW.DLL and SHOCKWAVEPLUGIN.CLASS to the FireFox plugins folder and FireFox will automatically find and use the plugin. But, as mentioned above, the registry method is a little more professional.