/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi,

While repackaging, wise captures many files which are unwanted. I see many files under "C:\windows\WinSxS". Could someone help me tell how to identify whether those files are related to the software I'm repacking or not? Keeping ""C:\windows\WinSxS" a side. In general, what is the best way to identify unwanted files and registry and cleanup the package?

Thanks in advance,
Prakash
0 Comments   [ - ] Hide Comments

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

Answers

0
If you dont know what files are unwanted I dread to think how dirty your packages are :)

The only way to know what files and registry keys are not wanted is experiance, research and web searching, for example a simple google search for C:\Windows\WinSxS told me what this folder did, although I knew anyway.

P
Answered 03/26/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I think there's a selection of exclusion lists available for d/l on the Altiris web site. Have a browse/search of the forums there: the Knowledgebase searching is useless unless you know exactly what to search for (in which case, why would you be searching?!?)
Answered 03/26/2008 by: VBScab
Red Belt

Please log in to comment
0
I would only ever use exclusion lists if I knew without any shadow of doudt that what I was exluding will never be used in any application. TBH I prefer to not use 1 and have everything shown then strip out the rubbish as you know you have everything.

P
Answered 03/26/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
OMG, Paul! Your packaging must take forever! :)

My tactic is to install my MSI, take a 'before' snapshot with a lightweight snapshotter, run the vendor's install over the top, then take an 'after' snap. That means I save time not having to edit out junk and that anything I may have over-zealously removed is flagged.

Each to his own, I guess...
Answered 03/27/2008 by: VBScab
Red Belt

Please log in to comment
0
Well I usually start with a clean virgin machine, snapshot, install software, end snapshot. As part of this I will ensure that I dont have anything excluded, clean up the result and then compile and test. Doesnt take too long and I generally have MSI's cleaned and packaged inside a day, I dont think I have had 1 take longer.

The development time generally comes during uninstall, or deployment through the deployment tool, for example developing a vbscript to restore the .zip extension after removing winzip or winrar.

As you said, each to their own :)

P
Answered 03/27/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
the best way to learn this is find someone better than you to teach you.

get him to highlight you crap but you remove it.

as for Winsxs i expect most of the stuff in there you would want to keep. its a very safe folder to be deploying to, it can only add assemblies if they are signed and as Paul mentioned a quick search will highlight you can put multiple dll's of the same name in there assuming they are strongly named.
Answered 03/30/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment