Hey guys, its been over 2 years since I did any real packaging, and back then it was like snapshot everything. So now I wanted to know whats the best practice when it comes to packaging? To create MSTs and deploy from them or to do a snapshot? I know with snapshot you can capture more and it gets more complicated with tougher apps, but I wanted to get a general idea of whats the best way to start off with.

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.


In my opinion, things didn't change so much during the last two years.
However I'd say that it always depends on the kind of software you have to deal with.
Generally, if it is a vendor .msi package then don't repackage it by using snapshot technology. That way you'd loose too much of the intelligence of the original setup. Use a transform file instead.
Then there are a few vendors which provide there own tool for those tasks like the Microsoft Office Resource Kit, the Adobe InstallTuner and so on. In those cases I think it's the preferred way to use those.
Only if the software doesn't fit in either cases try repackaging them using Snapshot.

And by the way, there are new(er) technologies than just a simple Pre- and Post- Snapshot, like Virtual Captures, Smart Monitors and so on but if I've to repackage an application I still swear on the good ol' Snapshot [;)]

Hope this helps


Answered 10/02/2006 by: rpfenninger
Second Degree Green Belt

Please log in to comment
If it's an msi I would follow rpfenningers advice. If you do re-package an msi you will loose the support for vendor updated/patches.

If it's not an msi; legacy setup:s can sometimes be pre-configured and depending on deployment tool that could be a preferred action to take instead of having hours of time to get a working msi.
Answered 10/02/2006 by: AngelD
Red Belt

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