Looks like I have the last 2 posts, sheesh.
The application suite that I am trying to virtualize requires a large amount of configuration via an Administration tool. I am able to virtualize the suite but am not sure about how to go about capturing the settings that need to be configured after the installation. Some I can do right after the install but others have to be done later on. IS there a way to initiate another capture to "update" the package? After reading over the SoftGrid Sequencer Guide I found some info on "Upgrading a Package" but this seems to be more along the lines of modifications like shortucts, adding files, etc.

I am wondering if its just a variation in wording that is causing me to overlook this in the Sequencer guide.
0 Comments   [ + ] Show 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.


You could package your configuration changes as an upgrade but I guess it really comes down to what you want to do. If you want to make a sequence that has the base install then have different icons run different pre-launch scripts to populate the configuration settings necessary for the session the user selects or if you have a little more time you could get around the multiple icons and put a front end into your pre-launch EXE. The issue with this technique is that the pre-launch script will have to run some sort of script or non-MSI installer to inject the settings into the sequence. If you want to just revisit the Sequence and make changes after the fact then opening a sequence for upgrade is probably your best bet. There still is no registry import tool but you can use the encoding wizard to do filesytem changes without doing a capture.
Answered 02/20/2007 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity