Hi, 
I am packaging Itunes for Windows 7 x64 deployment. I have extracted the MSI from the exe and have noticed that it contains 3 dlls and an OCX file in the SelfReg table. As per best practice I have extracted the com data using Repspyui.exe (adminstudio) and have noticed that it has a quite a few references to source path of the dll/ocx file (i.e. C:\users\username\desktop...). 

My question is:
1. Do I import all the reg keys into the MSI component and then clear out the hardcorded references to the source files. 
2. Do I need to further clean up the registry keys exported and only import into the MSI what will only be required (not sure how I can figure out whats required)

I'm pretty knew to this process so please can you let me know what would be the best practice method forward?

Thanks in advance. 

Regards,
-appviking
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

It sounds like you may have run REGSPYUI.EXE with the three files located on the Desktop.  You really need to run RegSpyUI with the files located in their intended locations, that way you will see the correct path in the exported Registry Data - you shouldn't be clearing out the paths, they just need to be correct.

All the registry data you import will initially be placed in the Registry table, but some of it may be better located in the appropriate COM tables (Class, ProgID, Extension, Verb) that's assuming you want to minimise ICE33 validation warnings/errors and avoid issues with uninstallation of your package causing other installed packages to self repair. You probably won't be able to move all the imported registry data into the COM tables, some of it will have no suitable table to accommodate it.

Moving the registry data to the COM tables is usually a manual process and can be a bit fiddly - I have seen scripts around that will do the job for you, but the last one I tried some years ago did more harm than good, so I move things manually now.

Spartacus 

Answered 06/16/2014 by: spartacus
Black Belt

  • Thanks.That explains it, so running the REGSPYUI.exe from the intended locations ensures the correct paths are captured.

    Out of curiosity i used adminstudio repackagers install monitoring feature and captured the registration of the dll's. I then compared this to the reg files that were created using Regspyui.exe.
    I noticed that the repackaged output was smaller and was missing components when compared to the regspyui output.

    Is this expected? Surely the repackager captured output ensures the right information is captured in the package?
    • Hope you are using snapshot method.
      in this case, do not use repackager..
      repackager does not capture the registry keys that are already present in the capturing machine.
Please log in to comment
Answer this question or Comment on this question for clarity