Software Deployment

I seem to recall that IS removes the registry information which WI uses to determine installed state, e.g.

HKCU\Software\Microsoft\Installer\Products\[CompressedProductCode]
HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Managed\[UserSID]\Installer\Products\[CompressedProductCode]

so you may be able to recreate the entries first, using the relevant ProductCodes in compressed form, then attempting the uninstall. I have some VBS code for managing the ProductCode<==>CompressedProductCode nonsense, if you need it.

Failing that, your only option is a a scripted uninstall. Luckily, the CLSIDs are documented (here on AppDeploy, IIRC) so it should be relatively straightforward.

Just curious really, but why do you need to remove the InstallShield engines ?

Multiple versions of the engine can coexist on the same system quite satisfactorily in my experience - in fact, I've seen several organisations choose to incorporate them into their core build to simplify deployment of InstallScript MSI's at any future stage.

Regards

Spartacus

We also have multiple versions of the InstallShield engine incorporated into our core build. Unfortunately we've now encountered the known problem with InstallShield whereby its DCOM server is set to run as an interactive user, not a launching user. This means InstallShield-based MSIs could fail to install when a non-admin user tries to run them.

The only way of correcting this when the InstallShield engine has already been rolled out to many workstations is to do an automated uninstall, then re-install with the DCOM changes.

VBScab - Thanks for your reply, I'll have a look at your solution, though as InstallShield have made the uninstall so messy we may end up manually changing the DCOM settings using dcomcnfg.

Hi Nick,

Have a look at the vbscript at http://www.appdeploy.com/messageboards/fb.asp?m=19850 under the "Summary of InstallShield InstallDriver DCOM Identity problem" section to set back the identity.

Ah ha! Well, go with Kim's suggestion and use that script. It'll be a hell of a lot simpler than thrashing about with the WI registry stuff! :) IIRC, you'll need to add some GUIDs to the list in that script to cater for versions not listed therein but you'll have those details already.

ORIGINAL: VBScab
you'll need to add some GUIDs to the list in that script to cater for versions not listed therein but you'll have those details already.
If you were referring to the script I provided then there is no need to update it as it will "reset" all installed versions.