I have a vendor issued MSI. I will be taking all defaults on install. Easy enough. After the software is installed, it needs to be configured. What would be the best way to do this? Should I create another MSI capturing the changes I make?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Is this being installed through a software deployment mechanism? (eg. SMS, LanDesk) We deploy our software through SMS and I usually launch the installation through a batch file. Doing it that way, you can have commands that run after the installation of the software. If that doesn't work maybe create an executable wrapper for the installation that handles all of the post-install config. There's lots of ways to do this.
Answered 05/03/2007 by: danr29
Purple Belt

Please log in to comment
Why not add the configuration settings to a transform?
Answered 05/03/2007 by: AngelD
Red Belt

Please log in to comment
you should also be aware that using command line properties there is an issue where during repair those values are no longer present (unless "you" have catered for them somehow)

as such it can be quite messy during unscheduled repairs.
Answered 05/03/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment