I see many junk files and registries are captured in repackager. Instead of checking one by one ( compare the captured registy files with base machine) if we have any Vbscript or exe that will automate manual work, then it will very easy to complete our task.

Automation task should be,:

If we select our ISM file and click generate means, it should list caputred junk registries in txt file.

I will use the txt file as reference and delete all unwanted files in ISM. so that i will get quality MSI file.


Help please


0 Comments   [ + ] Show Comments


Please log in to comment



You are using AdminStudio? Isn't there an exclusion list feature that provides this capability already?

Answered 09/19/2013 by: bkelly
Red Belt

  • Thanks for your quick response!

    Yes , i am using Admin studio.

    I too using exclusion list for filtering junk registries and files eventhough some of the sharable files registries (addtionally service, patches..) are getting caputre.

    Earlier, i had a regcompare tool for wise package studio. which compare WSI and base registries. now we have moved to Admin studio and we cannot have an option to use the custom tool.
    It will be really helpful if there is any tools which compare capture ISM file with base registry.

    Expecting tool like,
    1. We have to select ISM file
    2. When i click execute buttion, it should search base rergistry with capture registry file.
    3. the output of the files and registries are considered as junk.
    4. we can delete the output file and compile the ISM file.
    5. we will get the quality MSI for packaging.
    • I'm not sure if you'll find such a tool, but I'm interested in understanding what it is you are working to gain here. What do you mean by the "base registries"? Do you mean the registry of the local machine? If so, it sounds like you are trying to exclude anything that might already be on the local machine as junk and that seems like a big mistake to me. Can you describe your end goal in the scenario you have outlined?
  • Yes, i mean base registries is local machine.

    I want to deliver quality MSI to my customer so before deploying msi applications to endpoints, i have to make sure it should not conflict with other files/registries.

    I am using exclusion list for filtering junk files and registries( here junk means, not related to capture applications) eventhough i found many registries are caputred which are not related to packaging.

    After caputre, if i found few registries to be exclude, then my job is easy (just think about lot of registry entries to be exclude).
    If i found many registry entries (after capture), then i have to compare one by one with local machine and capture entries ( if i see same entries are present in local machine, then i will delete from the ISM file)

    Instead of doing manual work, i am searching for automation tool (which will comapre with local machine (clean machine) and caputred ISM file).

    Hope you are clear.
    • Looking for conflicts certainly makes sense. Have you looked at AdminStudio's conflict resolution features included with Test Center?
  • Where i can see this conflict tool?
    • Here is a link to the documentation:

      The subject conflict resolution with Test Center is covered starting on page 1645. Both Testing for Conflicts Between Packages and Testing for Conflicts Between Packages and OS Snapshots.
Please log in to comment
Answer this question or Comment on this question for clarity