Comments on: Mozilla Firefox 3.0.6 .msi package for distribution

By: Brian Jackson

Brian Jackson — Fri, 18 Sep 2009 04:36:51 +0000

Thanks for the kind remarks. Ya I try to post as often as I can. I hope once I graduate and am in a full time career that I might be able to dedicate some more time to blogging The MSI packaging is something I also want to work a lot on this year at work. So far I have had about 24 MSI packages working 100%. It saves so much time when reformatting a computer. You basically can just double click on a batch script that will then do a silent administrator install and watch your programs start appearing. Also installs of MSI packages are way faster than standard installs. Really fun and challenging project. Each application to package has its own challenge. Have a great evening!

By: PC Arbor

PC Arbor — Fri, 18 Sep 2009 04:07:31 +0000

Saw this during my Thursday night web searches. Amazing what stuff you can find doing a search XP repair ideas.
Kind of caught me off guard.

Thanks for posting.

By: Brian Jackson

Brian Jackson — Sun, 19 Jul 2009 19:23:53 +0000

Yes, that does work fine for our network installations, however we are wanting to package MSI’s for notebooks as well. If a person has a notebook and does an install, we don’t want the MSI to perform a repair. The problem I am working with right now is that the additional users that login and launch the application, the MSI is currently performing a repair, and if the MSI install file has been deleted then the APP is unable to run. Currently using:

ALLUSERS=1

But it is still searching for dependencies somewhere.

By: Enes

Enes — Wed, 15 Jul 2009 05:34:20 +0000

I have a suggestion from previous experience.

ALLUSERS=2
SOURCELIST=x:\distribution\apps\msisource

Have that as your install switch as well, put the path of the MSI where you are executing it from.

In multi user environment depending on how you have set it up, you would have controll of who gets what applications and generaly with SMS/SCCM/GPO you would have a general directory where you would keep all of your application and execute them from.
Having that as a shared drive with user can’t delete/modify the folder structure, you can set your SOURCELIST and eliminate your need for local msi files for repair, if it can’t find it in the temp folder it would go to the sourcelist to get the MSI.