Updating Shockwave in our business environment and trying to get rid of all older versions. I've written a package in Wise Package Studio 8 that uninstalls the older versions, except I'm having trouble with one version, which is listed in the registry as Shockwave Director 8.5.1. My uninstall string is this:

C:\WINDOWS\system32\Macromed\SHOCKW~1\UNWISE.EXE /S C:\WINDOWS\system32\Macromed\SHOCKW~1\Install.log

That works, but the uninstall forces a reboot, which we don't want to happen in an effort not to disrupt users workflow.
I've tried throwing all the parameters I know of at it--/noreboot, -noreboot, /REBOOT=R, /REBOOT=ReallySuppress,and so on--but so far none have worked.
Just curious if there are any other tricks I could try.
I should also note that I've tried creating an uninstall package using WPS8 and AdminStudio, but something about the reboot seems to be problematic--AdminStudio never attempts to create an MSI post-reboot, and Wise creates an MSI, but doesn't capture any of the file or registry changes that happen after the reboot. I was going to try creating a package manually, but there were approximately 2000 reg changes, and so that idea went out the window because I don't have that much time for this project.
I reckon worst-case scenario would be get the PCs running this version of Shockwave into a separate SCCM collection, then do a special push just to those PCs, and attempt to notify the users in advance that we'll be rebooting their PCs.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
The Wise installer for SW is using WiseScript. Its silent switch is '/S' as detailed here. Thus your MSI arguments are ignored.

I imagine the reboot is because, IIRC, SW adds to the PATH.

Use the INSTALL.LOG to build an uninstalling MSI or you may want to capture the uninstall to get to the same point. If that capture recreates the removal of entries from PATH, there's no need to reboot, as Windows is happy to ignore non-existent folders in the PATH.
Answered 11/05/2010 by: VBScab
Red Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Excellent. Using the Install.log as reference for writing the uninstall package worked like a charm.
Answered 11/05/2010 by: RonW
Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity