This article is for IT Admins who want to configure Firefox on their organization's computers.
Download Firefox MSI Installer On the Enterprise downloads page, the Firefox browser is available for following OS – Windows 64-Bit, macOS and Windows 32-bit. If you have got an environment running both 32-bit and 64-bit OS, you can download both of them. If it’s just 64-bit OS in your setup, download the 64-bit bit installer. If you need to run 32-bit Firefox or manually install 64-bit Firefox, you can simply download and re-run the Windows (32-bit or 64-bit) Firefox installer from the Firefox platforms and languages download page. Your download should begin automatically. Try the button below!
Firefox Enterprise offers MSI installers per locale, per cpu architecture (32 and 64 bit) and per channel to help system administrators customize and deploy Firefox in their environments.The MSI installer (supported on Windows 7 and later versions) is a wrapper of the exe full installer that allows customizations through the use of a MST file prior to deploying through standard Windows deployment tools such as Active Directory or Microsoft System Center Configuration Manager.
Table of Contents
- 2Configuration options
- 3MSIEXEC options
- 4Example configuration
Visit https://www.mozilla.org/firefox/all/ and use the drop-down options to select a MSI installer for Firefox Nightly, Developer Edition, Firefox Beta, Firefox Release or Firefox Extended Support Release.
Use the Select your preferred language drop-down to install a Firefox MSI installer in your preferred language.
![Download mozilla firefox offline installer 64 bit Download mozilla firefox offline installer 64 bit](https://desktopwalls.net/wp-content/uploads/2014/12/Asus Inspiring Innovation Logo Desktop Wallpaper.jpg)
MSI transforms (MSTs) for the Firefox MSI installers can be created or edited using the tool of your choice (MS Orca or other) to customize the installation. This section details the options available.
Firefox custom MSI options
Set a directory path - INSTALL_DIRECTORY_PATH=[path]Absolute path specifying the complete install location. This directory does not need to exist already (but it can).If INSTALL_DIRECTORY_NAME is set, then this setting will be ignored.
Set a directory name - INSTALL_DIRECTORY_NAME=[name]Name of the installation directory to create within Program Files. For example, if INSTALL_DIRECTORY_NAME is set to Firefox Release, then the installation path will be something like C:Program FilesFirefox Release. The Program Files path used will be the correct one for the architecture of the application being installed and the locale/configuration of the machine; this setting is mainly useful to keep you from having to worry about those differences.If this is set, then INSTALL_DIRECTORY_PATH will be ignored.
Install a taskbar shortcut - TASKBAR_SHORTCUT={true,false}Set to false to disable pinning a shortcut to the taskbar. true by default. This feature only works on Windows 7 and 8; it isn’t possible to create taskbar pins from the installer on later Windows versions.
Install a desktop shortcut - DESKTOP_SHORTCUT={true,false}Set to false to disable creating a shortcut on the desktop. true by default.
Install a start menu shortcut - START_MENU_SHORTCUT={true,false}Set to false to disable creating a Start menu shortcut. true by default.
Disable the maintenance service - INSTALL_MAINTENANCE_SERVICE={true,false}Set to false to disable installing the Mozilla Maintenance Service. This will effectively prevent users from installing Firefox updates if they do not have write permissions to the installation directory. true by default.
Disable removing distribution directory - REMOVE_DISTRIBUTION_DIR={true,false}Set to false to disable removing the distribution directory from an existing installation that’s being paved over. By default this is true and the directory is removed.
Prevent rebooting - PREVENT_REBOOT_REQUIRED={true,false}Set to true to keep the installer from taking actions that would require rebooting the machine to complete, normally because files are in use. This should not be needed under normal circumstances unless you’re paving over a copy of Firefox that was running while the installer was trying to run, and setting this option in that case may result in an incomplete installation. false by default.
Bundle extensions - OPTIONAL_EXTENSIONS={true,false}Set to false to disable installing any bundled extensions that are present. true by default.
Application files extraction directory - EXTRACT_DIR=[directory]Extract the application files to the given directory and exit without actually running the installer. Of course, this means all other options will be ignored.
The command line parameters for msiexec.exe (the Windows component responsible for installing, uninstalling, and otherwise working with MSI files) are documented here and also by the output of the /? option. Our MSI packages, because they wrap a .exe installer and don't really use the MSI framework, do not support many of the command line parameters available to msiexec. This document lists the msiexec parameters that are supported and unsupported for use with our MSI packages.
Supported MSIEXEC Options
- /i or /package
- Installs the product.
- /L or /log
- Generates an MSI log file. All of this option's configuration parameters are supported.
- /m
- Generates an SMS status .mif file.
- Without having a copy of Systems Management Server I've been unable to test this, but it should work.
- /q, /quiet, and /passive
- Sets the UI mode. The full UI option (/qf) is accepted but ignored, because we have no full UI.
- /norestart, /forcerestart, and /promptrestart
- The default behavior is always /norestart, but the other options behave as expected.
- PROPERTY=VALUE
- Command line property configuration is supported for all public properties we provide (meaning the ones with UPPERCASE_NAMES).
Options that do not operate on a package file (/?, /h, /help, /y, /z)
Unsupported MSIEXEC Options
- /f
- Repairs the product.
- /a
- Administrative installation.
- /x or /uninstall
- Uninstalls the product.
- /j along with /t, /g, and /c
- Advertises the product.
- /n
- Specifies a particular instance of the product.
- /p or /update
- Applies a patch (.msp) file.
Here’s an example of a valid .mst file to help understand how options can be changed along with the MSI directory for mozilla central:
Logging can be configured on the MSI to help troubleshoot installation issues.
There are several ways to use the MSI file with configurable parameters exposed in Firefox MSI:
By using an external MSI editor (e.g. ORCA)
- File/Open and select the MSI to be edited.
- Find the Property table and select it.
- Change the values for the PROPERTIES you need to.
- From ORCA, select File/Save as and save the custom modified MSI installer.
Note that this will invalidate the MSI file's signature; if you need the file to be signed, you'll have to sign it again using your organization's certificate.
By using a transform (.mst) configuration
- Use Orca to open the MSI.
- Select Transform > New Transform from the menu bar.
- Change the values for the PROPERTIES you need to.
- Select Transform > Generate Transform to save your changes as a transform (.mst) file.
- Run: msiexec /i “Firefox.msi” TRANSFORMS=”custom.mst”
By using command line parameters
- Rename the Firefox MSI file as default.msi
- Move the file in a C:MSI directory
- Run:
- msiexec.exe /i 'c:MSidefault.msi' INSTALL_DIRECTORY_PATH='C:Firefox' TASKBAR_SHORTCUT=false DESKTOP_SHORTCUT=false INSTALL_MAINTENANCE_SERVICE=false /quiet
All private parameters (FIREFOX specific, present in CAPS can be used in the command line + the msiexec public parameters like /i and /quiet in the above example)
MSI package for Mozilla Firefox
Package Overview
Every time a new version of Firefox has to be installed you must search or test if the settings from the config file have changed, to check if they are still valid or not.
Instead of hunting down, sometimes blind, the new settings from the config file or older ones that got new parameters, wouldn't it be great to just configure the Firefox installation from the UI and have all those settings captured automatically and included into your final package (MSI in this case)?
Firefox 71 Msi Download
Using a repackager to capture the installation in a VM (hosting an OS similar with the one on which you plan to deploy Firefox) means you don't have to know anything about the files Firefox installs or where it keeps its settings.
In what follows we'll show how to repackage Firefox and generate an MSI for it. The new package will be pre-configured to:
- not show the import wizard for the bookmarks when you first launch Firefox
- disable the automatic updates check
- not install the silent updates maintenance service
- disable the check for the default browser
- how to set a default homepage
- configure shortcuts locations
Repackaging Process
Mozilla Firefox Msi Download
The process is similar to the one presented in our tutorials. For this demo, we'll use a VMware virtual machine, but Hyper-V is supported too.
Short list of important steps done during packaging:
- select the VM profile used by the repackager
- specify the correct product (Mozilla Firefox) and company name (Mozilla), during the wizard. This is very important as these parameters influence directly the install paths detection heuristics.
- configure Firefox as desired in the VM, after the repackager installed it
- edit the generated project in Advanced Installer, to customize/clean it before you build the final MSI
- build the MSI and test it in the same VM (same snapshot)
Video Tutorial
Deployment Stage
Once you have the MSI built and tested you can go on to the next stage, deploying it to your users. You can deploy an MSI easily using Active Directory/GPO or through SCCM.
Advanced Installer has a wizard that helps you to publish the MSI to your SCCM server directly from your packaging/development machine.