/bundles/itninjaweb/img/Breadcrumb_cap_w.png

Utility to clean Installshield registry keys from captured .WSI/.MSI

  • Skaye
    Senior Yellow Belt
  • How helpful is this to you?
  • Average Rating 0
  • 5647 views
  • 07/17/2009
Several InstallShield-wrapped install routines dump hundreds of HKCR\Interface keys that get captured during the initial setupcapture of the installation. Is there any kind of utility that can be used with the .WSI or .MSI to clean the database of these unnecessary keys?
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
There are more entries than those you see in the 'Interface' section! You really ought to have set the keys up as 'Exclusions' already. They're easy enough to add after the event, though. In the capture process, highlight the IS junk and select 'Exclude' or 'Exclude Globally'.You can perform these steps 'manually' by editing %SystemRoot%\WisePSSC.INI or [WiseSharePoint]Repackage.INI, ensuring in both cases that you retain the sequencing of the IgnoreKeyXXX/IgnoreFileXXX. For that, it's handy to pass the files through Excel (or a text editor which can sort lines, e.g TextPad) to put them in order. As ever, make sure you have a back-up.
Answered 07/20/2009 by: VBScab
Red Belt

Please log in to comment
0
Is there any tool which will let us know the duplicate registry entries which are already present in system(clean build) form the captured registries?

Manually checking all the registry entries with system is time consuming.


Thanks.
Answered 05/31/2011 by: naveen.packager
Green Belt

Please log in to comment
0
If they're already present, why would a capture capture them? Your exclusion list should include anything which must NOT be overwritten.
Answered 05/31/2011 by: VBScab
Red Belt

Please log in to comment