This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Chained MSI - change install parameters
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 13, 2012
02:43 AM
Chained MSI - change install parameters
Hello, this is may first post on this forum so please be gentle.
I've recently come across the IsChainPackage table in a MSI we are trying to deploy (IBM Client Access 7.1) ...
I've searched the web trying to find out different things about the table.. and so far I still didn't find the info i've been looking for (table, table-columns description)
For my particular case we want to deploy the app totally silent, no UI, "/qn" equivalent. I can't seem to get to the UI in Installation Designer to be able to modify the install parameters of the chained-MSIs (think this is because it is already an msi), in an .ISM project i can see the "Releases" menu under "Media" and can change the install parameters.
My question:
Is there any way of modifying in the "IsChainPackage" table like in the "Option" column ... so the parent-MSI will pass different parameters (/qb! or /qn) to the chained-MSI??
Can any body point me in a direction to get my desired design?
Thanks!
I've recently come across the IsChainPackage table in a MSI we are trying to deploy (IBM Client Access 7.1) ...
I've searched the web trying to find out different things about the table.. and so far I still didn't find the info i've been looking for (table, table-columns description)
For my particular case we want to deploy the app totally silent, no UI, "/qn" equivalent. I can't seem to get to the UI in Installation Designer to be able to modify the install parameters of the chained-MSIs (think this is because it is already an msi), in an .ISM project i can see the "Releases" menu under "Media" and can change the install parameters.
My question:
Is there any way of modifying in the "IsChainPackage" table like in the "Option" column ... so the parent-MSI will pass different parameters (/qb! or /qn) to the chained-MSI??
Can any body point me in a direction to get my desired design?
Thanks!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 13, 2012
11:09 AM
I think this whitepaper discusses this a bit. But you can also just watch what InstallShield puts in the table in a new basic msi project as you twiddle the options.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 14, 2012
09:06 AM
Hello, that white paper doesn't realy tell much on the subject.
How is it posible for an entire table to exist without information on it?
I know i might find out something if i just keep trying... that's not the point.
How is it posible for an entire table to exist without information on it?
I know i might find out something if i just keep trying... that's not the point.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 15, 2012
08:44 AM
Ah, indeed, the whitepaper had less information than I remembered. The paragraph "Small and minor upgrades do not work by default" is most of it, and it also links to this thread with some more information: http://community.flexerasoftware.com/showthread.php?t=183641
But it leaves out the numeric details, so watch the values in the Options column of the ISChainPackages table as you change the UI setting in a sample basic msi project. Or just configure it how you want, and copy the values to your real file.
But it leaves out the numeric details, so watch the values in the Options column of the ISChainPackages table as you change the UI setting in a sample basic msi project. Or just configure it how you want, and copy the values to your real file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2012
12:37 PM
MichaelU wrote:
Ah, indeed, the whitepaper had less information than I remembered. The paragraph "Small and minor upgrades do not work by default" is most of it, and it also links to this thread with some more information: http://community.flexerasoftware.com/showthread.php?t=183641
But it leaves out the numeric details, so watch the values in the Options column of the ISChainPackages table as you change the UI setting in a sample basic msi project. Or just configure it how you want, and copy the values to your real file.
Can anyone elaborate on those numeric details? I know 16 is supposed to be for ecoreinstallall or something along those lines. what are all the options supported and the corresponding arguments that need to be passed to make them all work correctly. I desperately need to be able to send a repair command to a chained msi
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)