Deployment of Total Return software
Hi All,
I am working on total return application. It is a Installshield exe, and capturing it to create the msi throws an error, and ther is no silent switches for it.. So I created a iss for the install.. and now I am trying to do the un install,
the setup.exe unstall does not work , so I tried creating the iss from C:\Program Files\InstallShield Installation Information\{GUID} . The uninstall does no work. I tried
"C:\Program Files\InstallShield Installation Information\{6E919D59-6AAC-4CFF-A6A1-12CA395723F6}\setup.exe" -runfromtemp -l0x0409 -removeonly ..
This works, but the guid number changes every install.
I am not sure how to unistall.
Please Guide me
Thanks
Answers (3)
Why dont you just run the setup.exe and record the uninstall iss file?
That should do the trick and it will aviod the GUID issue you have as you are refering to a local iss file.
Comments:
-
I never trust vendor set-ups and always capture to an MSI.
@OP:
If that process is erroring, why not simply find out why?!?! A few minutes with ProcMon will point to the issue. - anonymous_9363 10 years ago
Does the GUID that it appears under in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall change with every install as well? (it really shouldn't). If not, you could write a VBScript or PowerShell that captures the uninstall string from the registry and run that. We've had to do that with a few products.
If I run the setup.exe to uninstall, it does not give the option to remove, but gives only 2 options as below.
It has multiple MSI within the installshield setup.exe, So I thought capture was not a good idea, but still tried, and then is when I get errors.
The GUID changes every install.
Austin, Please can you guide me with the script.
Comments:
-
So, as each MSI is extracted, copy it somewhere safe and use those.
If the ProductCode (the GUID in the 'Uninstall' branch) is changing with every install, you should first find out *where* it's being changed. If it's in one of the MSIs, it'll be done via a Custom Action which you can easily condition out with an impossible-to-meet condition. I use '0-1'. If it's in the EXE, that will no longer happen if you use the MSIs. Second, you should then fire an email at the vendor, asking why his installation routine is so brain-dead. - anonymous_9363 10 years ago