Repackaging Post-capture best practices, what to strip out, etc.

I've been sifting through google and various forums, trying to find a best practices guide. I'm familiar with the various tests to run (Installation test, legacy comparison test, advertisement test). I'm more interested in what is considered "best practice" with regard to elements being captured with Repackager. Specific user's folders, for example, should go. What else?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: vjaneczko 10 years ago
9th Degree Black Belt

One nifty thing you can do is to start a recapture, reboot the system, open a browser, open Explorer, then finish the recapture.  That'll show you a lot of what you want to exclude from any recapture you perform.

Posted by: Badger 9 years ago
Red Belt

Def do a reboot. it is surprising what happens on a machine.

The two tips I have on this when I do training, is the key or file you are looking at anything to do with your app.
That makes it easy to delete the (majority of) microsoft keys and files, ditto for McAffee, Sophos, SCCM, ALtiris, LANDesk etc

It is a bit trickier when you have apps that have swapped ownership. (Thos Softgrid reg keys under the Microsoft key are a good example)

Whilst your learning, leave as much stuff turned on, so the search service etc runs. Bear in mind this is NOT good practise, but will help you to understand just what is happening every minute of every day on that busy machine of yours.

2nd tip..
Keep a spare clean machine, when doing the clean up, look on the clean machine. If its there, (and as its clean, it does not have the app you are packaging on it) then you can remove it from your captured package.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ