issue with an installation running silently
hi all,
i've got an msi i'm deploying via sms and it has a custom action to run an executable to perform configuration at the end of the installation. i can run the msi silently obviously, but cannot hide the dialog box that appears to perform the post config. even if i configure the sms program to hide all windows and suppress all notifications.
is anyone aware of a wrapper i can deploy that will ensure the entire process runs silently?
i've got an msi i'm deploying via sms and it has a custom action to run an executable to perform configuration at the end of the installation. i can run the msi silently obviously, but cannot hide the dialog box that appears to perform the post config. even if i configure the sms program to hide all windows and suppress all notifications.
is anyone aware of a wrapper i can deploy that will ensure the entire process runs silently?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Posted by:
groulder
15 years ago
i'm not capable of doing that.
it's running in the execute immediately part of the msi script. seems to run a vbscript stored in the binary table first which determines the parameters for the executable. the next line calls the executable from the command line with the parameters the vbscript previously determined.
if only you could execute hidden in msi script. cutting all this out of the msi script and moving it into a seperate msi may be beyond my abilities.
it's running in the execute immediately part of the msi script. seems to run a vbscript stored in the binary table first which determines the parameters for the executable. the next line calls the executable from the command line with the parameters the vbscript previously determined.
if only you could execute hidden in msi script. cutting all this out of the msi script and moving it into a seperate msi may be beyond my abilities.
Posted by:
groulder
15 years ago
Posted by:
groulder
15 years ago
Posted by:
anonymous_9363
15 years ago
The answer to both of your questions is "No."
It seems you have fallen victim to a lazy packager. I *could* suggest a nasty lash-up such as using AutoIt to automate the pressing of the necessary buttons but, while you're going to the lengths of learning how that utility works and building a script for it, it'd be simpler and more robust to capture it to an MSI. Have you seen/tried AppDeploy's Repackager tool? That strikes me as a no-cost, easy thing to try first.
BTW, a hint: use the 'Edit' link at the top-right of your post instead of making multiple posts.
It seems you have fallen victim to a lazy packager. I *could* suggest a nasty lash-up such as using AutoIt to automate the pressing of the necessary buttons but, while you're going to the lengths of learning how that utility works and building a script for it, it'd be simpler and more robust to capture it to an MSI. Have you seen/tried AppDeploy's Repackager tool? That strikes me as a no-cost, easy thing to try first.
BTW, a hint: use the 'Edit' link at the top-right of your post instead of making multiple posts.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.