02/14/2017 979 views

Hello all - I am packaging an MSI (from capture .IRP -> .ISM -> .MSI) with Transform using Installshield (no .MSI file was generated from opening setup.exe during install and is why I did a capture). On first launch after installing the application, I am presented with configuration question boxes, such as where to point to a database. Is creating a vbscript the only way to address the post install configurations? And can you please provide a script example I could use? Please also let me know of any other options.

I am using Installshield 2015

I am indebted to this community. Thank you in advance!

0 Comments   [ + ] Show comments


Community Chosen Answer

Errr...why not simply capture the post-install stuff and then either deploy it as exactly that or, as the changes are likely to be fairly trivial, add them to the MST?

If the config is in the user profile, you'll need to re-work the feature tree, in order to have an advertised entry-point such as a shortcut to trigger self-healing but that subject has been done to death here so just search for that term here.
Answered 02/14/2017 by: VBScab
Red Belt

All Answers


you either have to capture the post install configs and poke them into the 'package' or, which would hopfully just be user reg keys, you can import them into a user component in the IDE....

or,  start from scratch with the original exe install, kick off the before capture, then install app, then configure app, do the after capture, then IRP to ISM, then to your new MSI.

Answered 03/15/2017 by: Badger
Red Belt