I want to cover few more topics to wrap this things up.
The first thing you might be thinking is “man that seems like a lot of work. Isn’t there something else I can do?” As I pointed out in the first post, Benjamin Smedberg’s Firefox Release Repackager is great if you are a Mac user. If you are not using a Mac, or you want to add more than two extensions, or if you need to add files to the removed-files list we talked about, you can’t use the release repackager. Here’s how to manually modify a Firefox install.
First, download a Firefox setup executable. Unpack that file into a directory using 7z.
7z x "Firefox Setup 22.214.171.124.exe"
If you want to add files to the removed files list, do it now. Edit the file
removed-files.log and add your files and directories following the syntax in the file. If you want to add extensions, you can follow the steps we outlined earlier, unzipping them in a temporary directory in
nonlocalized/extensions and then renaming the temporary directory to the extension ID based on the information in
If you are not interested in having a self extracting executable, this is actually enough. If you were to run setup.exe at this point, it would do the install, removing the files and directories you specified, and including the extensions you unzipped. If you want to create a self extracting executable, you would need to manually repackage the EXE. Unfortunately, I don’t have those steps in front of me right now. I’ll update this post if I find them.
Another problem that might arise is that you don’t mind updates coming from Mozilla, but you’d like to determine when they get pushed to your users. For instance, you might want to do some internal testing. You can actually set preferences that prevent specific updates from being offered to your users. For instance, the preference
app.update.never.126.96.36.199 tells Firefox to never offer the 188.8.131.52 upgrade. So you can use the CCK to set these preferences, and then update the CCK when you have verified a particular version.
What if Firefox can’t upgrade your users because it is running at the wrong permissions level? If this is the case, you’ll obviously need to create your own upgrade solution and turn off the Mozilla upgrades. To turn off the Mozilla upgrade checking, set the preference
app.update.enabled to false.
Forgot one – if you want to do a silent/unattended install, invoke the installer (setup.exe or the full installer executable) with -ms.
Well, that’s about all I have. I hope you’ve enjoyed this series of posts. If you have any questions about deploying Firefox in the enterprise, please let me know.
In addition, I’ll take this moment to shamelessly plug IBM. If you are an enterprise and need help customizing and/or deploying Firefox, IBM can help. Contact me at email@example.com