Greetings kind folks!

A question, please:

I have an app which already has its own MSI installation file.

Unfortunately for me, this MSI installs files from uncompressed external files.

Since I need to push this app via SMS, I'm pretty sure my app needs to be self-contained.

I TRIED changing settings (to internal cabs) in my transform file, but predictably, no files were compressed INSIDE the MST.

I'm fairly sure that I could just edit the original MSI file, but our best practices say to leave vendor MSIs alone and always use transforms.

Any ideas or suggestions?

Any help would be GREATLY appreciated.


- Sean Roberts
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


SMS should not need everything self contained because it will install from a UNC or drive letter. If it's SMS 3.0 with the advanced client well I am not too sure on how that has been changed.

If you want the files to be self contained I think you'll have to edit the vendor MSI. I don't think you can change that with a MST because you have to remember the whole principle of a MST is not not modify the vendor MSI.
Answered 08/04/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Hi Sean,

Yes, kkaminsk is right, one of our clients uses SMS 2.0 and we have no problems deploying applications that aren't "self contained" from UNC paths.

Hope that helps

Answered 08/04/2004 by: plangton
Second Degree Blue Belt

Please log in to comment