What About Firefox Deployment?

You might have noticed that I spend most of my resources around configuring Firefox and not around deploying Firefox. There are a couple reasons for that:

  1. There really isn’t a “one size fits all” solution for Firefox deployment because there are so many products that can be used to deploy software within different organizations.
  2. Most discussions around deployment devolve into a “I wish Mozilla would do a Firefox MSI” discussion.

That being said, there are some things I can recommend around deploying Firefox on Windows.

If you want to modify the Firefox installer, I’ve done a few posts on this in the past:

If you need to integrate add-ons into that install, I’ve posted about that as well:

You could also consider asking on the Enterprise Working Group mailing list. There’s probably someone that’s already figured it out for your software deployment solution.

If you really need an MSI, check out FrontMotion. They’ve been doing MSI work for quite a while.

And if you really want Firefox to have an official MSI, consider working on bug 598647. That’s where an MSI implementation got started but never finished.

Please note: I reserve the right to delete comments that are offensive or off-topic.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “What About Firefox Deployment?

  1. Most of the demand for an MSI is a weakness in some tools to deploy anything else or an excuse to live the status quo (Internet Explorer). However MSI installations (when they work) are convenient and FrontMotion’s service works really well (whilst we can deploy exe’s, FrontMotion has some nice value adds and costs very little).

    Add all of Mike’s knowledge sharing and CCK2, deploying Firefox is pretty trivial. So much so it’s now our default browser, with IE causing it’s regular hair pulling when someone feels they must use it.