Transform & Install MSI From Installation
I created a Transform file for a vendor MSI. I also created a custom MSI that I want to run at the end of the vendor MSI. From the MSI Script, Execute Immediate tab, I inserted the Action "Install MSI From Installation" immediately following the InstallFinalize sequence. The custom MSI shows up as a Resource, but as zero bytes in size. And obviously it doesn't run. How do I run a Custom Action with a Transform file (using WPS 7)?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Using nested MSIs is a deprecated methodology and is to be actively discouraged (disregarding WI v4.5 chaining...)
From your description, it seems obvious you're using Wise Package Studio (or one of the Altiris/Wise family) so use the other tools e.g. WiseScript to create a set-up stub for your install.
Having said that, what's in your own MSI that can't be included in the transform?
From your description, it seems obvious you're using Wise Package Studio (or one of the Altiris/Wise family) so use the other tools e.g. WiseScript to create a set-up stub for your install.
Having said that, what's in your own MSI that can't be included in the transform?
Posted by:
Ron Duca
15 years ago
I'm using Wise Package Studio 7 Standard, and that's the only packaging tool I have.
My custom MSI only contains one file and two registry entries, but they are dependent upon the vendor MSI being installed. If I include those three items in my transform, how do I do it so that they will install after the vendor install?
My custom MSI only contains one file and two registry entries, but they are dependent upon the vendor MSI being installed. If I include those three items in my transform, how do I do it so that they will install after the vendor install?
Posted by:
anonymous_9363
15 years ago
Just include the file and registry data in the transform. If any part of the install fails, it all fails, sou you need have no worries about orphaned files or registry entries being left behind.
Remember that, if the vendor MSI uses internal CABs, the transform will use an external CAB (for the file you are installing). You may want to rename the CAB and its corresponding entry in the Media table from the brain-dead Wise default of [MSIName]_WISETFRM.CAB to something more logical, like [MSIName].CAB.
Remember that, if the vendor MSI uses internal CABs, the transform will use an external CAB (for the file you are installing). You may want to rename the CAB and its corresponding entry in the Media table from the brain-dead Wise default of [MSIName]_WISETFRM.CAB to something more logical, like [MSIName].CAB.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.