/build/static/layout/Breadcrumb_cap_w.png

help needed please

hi all,

i have made a mistake into a msi file i have done and i need your input from you gurus.

i have a msi file which have some upgrade information to remove previous versions. the mistake i made is that i forgot to relocate action RemoveExistingProducts in the InstallExecuteSequence table. so RemoveExistingProducts is the last action in the sequence.

now this msi is installed on all workstations. for 2 weeks now, sometimes the application gets removed and i wonder if that mistake could be the cause.

since they are now all installed, should i go ahead and fix this and re-install on all computers? i wish i could not impact computers again so i was wondering, since all installations are finished, can i leave it like this and hope no more problem will happened in the future, or should i fix my mistake?

thank you very much!

edit: i just found this;

After the InstallFinalize action. This is the most efficient placement for the action. In this case, the installer updates files before removing the old applications. Only the files being updated get installed during the installation. If the removal of the old application fails, then the installer only rolls back the uninstallation of the old application.

it seems i have done no mistake after all!

thanks!

0 Comments   [ + ] Show comments

Answers (1)

Posted by: AngelD 15 years ago
Red Belt
0
Event if it states that it is "most efficient" don't have to mean it's the best way to do it, they are both usable in different scenarios.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ