/build/static/layout/Breadcrumb_cap_w.png

Uninstall in general

IF i make an installation like this : MSIEXEC /i AcroStan.msi TRANSFORMS="AcroStan.mst" /qn

If i have to uninstall do i need to include the MST in the UNINSTALL string as well?

like this MSIEXEC /x AcroStan.msi TRANSFORMS="AcroStan.mst" /qn

or will this do MSIEXEC /x AcroStan.msi /qn

And what if the transform file has been changed since the the first installation?

Sweede

0 Comments   [ + ] Show comments

Answers (3)

Posted by: AngelD 16 years ago
Red Belt
0
You don't need to specify the transform during uninstall.

And what if the transform file has been changed since the the first installation?
Are you talking about reinstalling the package with the "new" transform?
Posted by: Sweede 16 years ago
Second Degree Green Belt
0
Yes

I have this first installation applied to a number of computers, then i found reason to make a small thange to the MST file
and the same installation but with newer MST has then been applied to another number, of computers.

Now I have this first number of computers that I need to update with the last MST changes.

Can I make a reinstall with the new MST,? and what if i need to apply this MSP also

AcrobatUpd810_euro_incr.msp

The installation set is a normal install with a MST not an administrative installation

Sweede ;-)
Posted by: AngelD 16 years ago
Red Belt
0
Depending on your distribution tool you could replace the cached MST with the new one and perform a reinstall.
For the patch you will need to apply that after the reinstall has occured.
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