Benefit of wrapping a exe to MSI


I would like to know if let say , we don't re-package any exe [due to any reasons] and run it through it's own switches into the Wise Script and inturn calling this Wise Script into the MSI.What is the benefit?

1.) Placing the CA [Wise Script] into the Deferred Sequence will make it run in System Context.is it?
or any other

2.) What can be the drawback with this approach?

The Add/Remove will have the EXE own listing and MSI has it's own [though we can delete it]

Now what can be the Uninstallation String for this another CA for Remove="ALL"

Please let me know if any one follow this kind of approach... though very rare case..

0 Comments   [ + ] Show comments

Answers (3)

Posted by: ekniranjan 12 years ago
Purple Belt
Best of my knowledge you can do for only some application like may be Microsoft one. But i don' think that's a good idea for all. For some application behavior they don't need MSI, even you do its sucks, so you do use switches.
Coming to drawback.................am not sure exactly or may be i can't explain them properly.
Posted by: mekaywe 12 years ago
Brown Belt
When you think that application shouldn't be captured OR any setup.exe calling multiple MSI's internally and you feel that separating the MSIs and creating transforms will affect the functionality of the application.

The above said concept will be implemented.
Posted by: anonymous_9363 12 years ago
Red Belt
Why bother with WiseScript when you have an EXE already?!? Just create the CA.

Myself, as a professional, I'd rather know exactly what an installation is going to do to my target workstations so would almost never run a vendor's install in the way you suggest. Heck, I don't even let vendor MSIs run without going over them in some detail. Capture it to an MSI and you will see exactly what it's going to do. If your client whines that they don't have the time/resources/whatever, ask them to sign a waiver to the effect that you will not bde responsible for any ill effect that your packages have. Otherwise, as sure as eggs is eggs, when the stuff hits the fan after that 2,500 workstation roll-out, there's only one person that it'll backfire on - look in the mirror.

And no, placing a CA in DE doesn't necessarily mean that it will run in System context. Look up execution sequence information on MSDN.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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