Upgrading to a new version...
Greetings all!
I'm using Wise Package Studio 4.51 and I'm trying to get my MSI to first uninstall a previous version of software before putting down the new version.
The original software was put down on the system via MSI, and my new installation does seem to successfully get the product code from the old MSI... I'm doing this in the Upgrades dialog under the Distribution section.
But when I install the new MSI, it doesn't seem to search for nor uninstall the previous version...
Any ideas?
Am I missing a step?
Any help here would be greatly appreciated...
Respectfully,
- Sean Roberts
I'm using Wise Package Studio 4.51 and I'm trying to get my MSI to first uninstall a previous version of software before putting down the new version.
The original software was put down on the system via MSI, and my new installation does seem to successfully get the product code from the old MSI... I'm doing this in the Upgrades dialog under the Distribution section.
But when I install the new MSI, it doesn't seem to search for nor uninstall the previous version...
Any ideas?
Am I missing a step?
Any help here would be greatly appreciated...
Respectfully,
- Sean Roberts
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
WiseMonkey3
19 years ago
Hi Sean,
Here are a few things I do with MSI upgrading.
If you are using AD to deploy the old & New apps you can manually add the old package to the upgrades tab and select "Required upgrade"in the GPO settings of the new app.
I like to increment the version number by at least .1, ie; if your old version is 2.0 increment the new version to 2.1 or even 3.0. This will automatically detect the older version (when using AD) and it will be displayed in the upgrades tab, you still need to select the "Required Upgrade".
By default wise places the "RemoveExistingProducts" after the InstallFinalize" under the MSI Script "Execute Immediate" tab.
I often move the "RemoveExistingProducts" up and place it in between the "InstallValidate" and "InstallInitialize". This will force the old app to be uninstalled before the new one.
For an explaination select the "RemoveExistingProducts" and press F1.[:D] it will tell you where and why you place this sequence.
If this doesn't work you could try a execute immediate custom action like "Install MSI From Destination" put in the product code and a /x. I've used custom actions to uninstall .exe's before but I haven't tried the MSI actions.
Good luck [;)]
Here are a few things I do with MSI upgrading.
If you are using AD to deploy the old & New apps you can manually add the old package to the upgrades tab and select "Required upgrade"in the GPO settings of the new app.
I like to increment the version number by at least .1, ie; if your old version is 2.0 increment the new version to 2.1 or even 3.0. This will automatically detect the older version (when using AD) and it will be displayed in the upgrades tab, you still need to select the "Required Upgrade".
By default wise places the "RemoveExistingProducts" after the InstallFinalize" under the MSI Script "Execute Immediate" tab.
I often move the "RemoveExistingProducts" up and place it in between the "InstallValidate" and "InstallInitialize". This will force the old app to be uninstalled before the new one.
For an explaination select the "RemoveExistingProducts" and press F1.[:D] it will tell you where and why you place this sequence.
If this doesn't work you could try a execute immediate custom action like "Install MSI From Destination" put in the product code and a /x. I've used custom actions to uninstall .exe's before but I haven't tried the MSI actions.
Good luck [;)]
Posted by:
sean_c_roberts
19 years ago
Thanks, Monk(ey)! :)
We deploy using SMS (not AD GPO).
The problem turned out to be that, while I had valid entries in the Min and Max version ranges, I didn't check the Include Max Range... checkbox, and so Wise was not searching the system for a prior app at all.
Simply checking BOTH the Min and Max checkboxes seems to have forced my new MSI to search for and uninstall the old MSI.
Thanks for your help!
Regards,
- Sean Roberts
We deploy using SMS (not AD GPO).
The problem turned out to be that, while I had valid entries in the Min and Max version ranges, I didn't check the Include Max Range... checkbox, and so Wise was not searching the system for a prior app at all.
Simply checking BOTH the Min and Max checkboxes seems to have forced my new MSI to search for and uninstall the old MSI.
Thanks for your help!
Regards,
- Sean Roberts
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.