Showing results for 
Show  only  | Search instead for 
Did you mean: 

Data to remove from Capture after reboot


I am trying to put together a list of things to remove from an ISM if the Snapshot required a reboot in the mddle of it. I have certain things like NAV, InstallShield info, certain IE settings, and some W2K specific info, but was wondering if anyone had an already existing list I could use for reference and use? I want to make sure I don't forget anything when I teach new employees how to repackage.

Thanks in advance,
(1) Reply

Take a snapshot, reboot and take another snapshot. That'll be what you need to ignore when you reboot

generally speaking, you are asking a $1Million question, as what needs to be removed involves a huge amount of skill, judgement and experience. Here are some pointers:

1) Look for things that are machine specific, usernames, SIDs, database names, network paths, IP addresses or things that were requested at installtime.
All those things need to be turned into Properties

2) Things that are always safe to remove are temporary data. Their names are generally a giveaway: MRU, bag, bucket, cache, last, temp, etc.
Most log files too are safe to ignore.

3) Try to use Repackager's Monitor mode as it (when it works) gives far cleaner results by watching the changes that are made by the installation, ignoring those made by Windows.

4) Maintain a central exclusions list on one of the servers and only give the supervisor (yourself) write access to default.ini. If everyone runs repackager from this central location then you should get consistant results.

5) Read this book.