Hi Everyone,

In our Windows XP environment, we have a wrapper that we put around all our MSI's or silent installs that basically just puts up a standard start screen (prompt user to hit next), reads through an INI to run through a series of MSI's and EXEs with silent switches, and then shows a finish screen.

While we work on moving to Windows 7 I thought it'd be a good time to revisit this. What are others doing for wrappers? Did you build your own or are you just calling the MSI from batch files & scripts? Anything else?
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


Or use a deployment tool? Most deployment tools support running the MSI's and EXE's with the appropriate switches. No need for wrappers anymore.
Answered 12/22/2010 by: Rheuvel
Brown Belt

Please log in to comment
Thats been the case for sometime. With v.Next (or is it 9 now?) we should finally have a webpage to launch our installs from rather than techs going straight to file servers to run installs when needed. But until then, it is nice to keep installation sources 'secure' using a wrapper. It also ensures the techs are installing applications with correct configurations.

My primary focus is ensuring that packages that are deployed are installed in the exact same way by techs. And its best in my experience to give the techs a file to just double-click rather than provide documentation for each step of every install. Yea, there is always UIResource.UIResourceMgr and advertising every install without notifications, but our inventory is huge. Heres to hoping v.Next's web based installation method can replace the file servers!
Answered 01/07/2011 by: hashref
Senior Yellow Belt

Please log in to comment