/build/static/layout/Breadcrumb_cap_w.png

Excluding files and registry keys

I have some experience of creating .msi packages and I´ve been working with Adminstudio before, but knowing .msi and Windows registry completely is not something I´m best in. So I would like to know your approach, when excluding registy hives and system files. The problem with packaging for me is, that the packaging tool offers a lot of different keys and paths to include or exclude. If I include too much, there will be useless crap within .msi, if I include too little, the .msi wouldn´t work. Is it always enough to include only c:\Program Files (x86)\Desired_Software_Folder and HKLM\Software\Desired_Software_Hive by default?


0 Comments   [ + ] Show comments

Answers (5)

Posted by: yannara 7 years ago
Blue Belt
0

Once again I came up with this problem. I tried to create an msi package with Appdeploy Packager of a special software with hardware drivers included. This software wrote in lot of different locations and I didn´t recognize them all. I tried to create package 3 times, every time it came corrupted. I gave up, and got back the Adminstudio. Created MSI with monitoring method, it came up fine with very clean registry, so.... Appdeploy is not good enough.

Posted by: swetha539 8 years ago
Orange Belt
0

And the files that are related to odbc connections also we include them.

 

Posted by: terebent 8 years ago
Second Degree Brown Belt
0

You have to include in the capture all new files and registry added to the machine. Some of them are useles, and you can exclude them. Exemple: logs, registry keys related to IE or Windows setings.

Posted by: deepali 8 years ago
Second Degree Brown Belt
0

What gets included in our package by default depends on the packaging build/image we are using.If it has unecessary services running, or applications installed like mcafee etc, there are chances files related to these applications will get included.Best way is try to see what all files are not related to your application.Something like log files, uninstall.exe, files related to apps like IE, mcafee, if you are using an image with CCM client installed, you will also get files related to this.Exclude all these files from your package.Same goes for registry keys.

Posted by: yannara 8 years ago
Blue Belt
0

Now I really understand, why creating your own msi is not really the first option you do for mass deployment. It gets ricky, when you import too much files and registry keys in msi, not knowing for sure, are they part of application or not. Packaging small programs is easy, but now when I´m trying to pack big and complex software, there are tons of files and reg hives I need something to do about....


Comments:
  • I´ve learned, that this free Packager utility is no good enough, I could package my apps with Adminstudio, using excluding, which Packager couldn´t handle. - yannara 8 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ