This article is for IT Admins who want to configure Firefox on their arrangement'south computers.

Firefox Enterprise offers MSI installers per locale, per cpu architecture (32 and 64 bit) and per aqueduct to help system administrators customize and deploy Firefox in their environments. The MSI installer (supported on Windows vii and later versions) is a wrapper of the exe total installer that allows customizations through the apply of a MST file prior to deploying through standard Windows deployment tools such as Active Directory or Microsoft Arrangement Centre Configuration Manager.

1 MSI Installers
two Configuration options
- 2.1 Firefox custom MSI options
3 MSIEXEC options
- 3.i Supported MSIEXEC Options
- 3.ii Unsupported MSIEXEC Options
iv Example configuration
- iv.ane By using an external MSI editor (due east.g. ORCA)
- four.ii By using a transform (.mst) configuration
- iv.3 Past using command line parameters

MSI Installers

Visit https://world wide web.mozilla.org/firefox/all/ and use the drib-down options to select a MSI installer for Firefox Nightly, Programmer Edition, Firefox Beta, Firefox Release or Firefox Extended Support Release.

Use the Select your preferred language drib-downward to install a Firefox MSI installer in your preferred language.

Configuration options

MSI transforms (MSTs) for the Firefox MSI installers can be created or edited using the tool of your selection (MS Orca or other) to customize the installation. This section details the options bachelor.

Firefox custom MSI options

Prepare a directory path - INSTALL_DIRECTORY_PATH=[path] Absolute path specifying the complete install location. This directory does not need to be already (but it tin can). If INSTALL_DIRECTORY_NAME is set up, then this setting volition be ignored.

Set a directory name - INSTALL_DIRECTORY_NAME=[name] Name of the installation directory to create within Programme Files. For example, if INSTALL_DIRECTORY_NAME is set to Firefox Release, then the installation path will be something similar C:\Program Files\Firefox Release. The Program Files path used will be the correct one for the architecture of the application existence installed and the locale/configuration of the machine; this setting is mainly useful to continue you from having to worry near those differences. If this is ready, then INSTALL_DIRECTORY_PATH volition be ignored.

Install a taskbar shortcut - TASKBAR_SHORTCUT={true,fake} Set to false to disable pinning a shortcut to the taskbar. truthful by default. This feature only works on Windows seven and eight; information technology isn't possible to create taskbar pins from the installer on later Windows versions.

Install a desktop shortcut - DESKTOP_SHORTCUT={truthful,false} Set up to fake to disable creating a shortcut on the desktop. truthful by default.

Install a start bill of fare shortcut - START_MENU_SHORTCUT={true,simulated} Set to faux to disable creating a Start menu shortcut. truthful by default.

Disable the maintenance service - INSTALL_MAINTENANCE_SERVICE={truthful,false} Set to simulated to disable installing the Mozilla Maintenance Service. This volition effectively forbid users from installing Firefox updates if they practise not have write permissions to the installation directory. true by default.

Disable removing distribution directory - REMOVE_DISTRIBUTION_DIR={truthful,fake} Gear up to imitation to disable removing the distribution directory from an existing installation that's beingness paved over. By default this is true and the directory is removed.

Forbid rebooting - PREVENT_REBOOT_REQUIRED={truthful,faux} Gear up to true to keep the installer from taking actions that would crave rebooting the auto to consummate, usually because files are in use. This should non be needed under normal circumstances unless y'all're paving over a copy of Firefox that was running while the installer was trying to run, and setting this pick in that instance may result in an incomplete installation. imitation past default.

Bundle extensions - OPTIONAL_EXTENSIONS={true,false} Prepare to faux to disable installing whatsoever bundled extensions that are nowadays. true by default.

Application files extraction directory - EXTRACT_DIR=[directory] Excerpt the awarding files to the given directory and go out without actually running the installer. Of course, this means all other options will be ignored.

MSIEXEC options

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 utilize the MSI framework, do not support many of the command line parameters available to msiexec. This certificate lists the msiexec parameters that are supported and unsupported for employ with our MSI packages.

Supported MSIEXEC Options

/i or /package
- Installs the product.
/Fifty or /log
- Generates an MSI log file. All of this option'southward configuration parameters are supported.
/m
- Generates an SMS status .mif file.
- Without having a re-create of Systems Direction Server I've been unable to test this, but it should work.
/q, /serenity, and /passive
- Sets the UI fashion. The full UI selection (/qf) is accustomed merely ignored, because we take no total UI.
/norestart, /forcerestart, and /promptrestart
- The default behavior is always /norestart, simply the other options behave as expected.
PROPERTY=VALUE
- Control line holding configuration is supported for all public properties we provide (meaning the ones with UPPERCASE_NAMES).

Options that do non operate on a bundle file (/?, /h, /aid, /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 case of the production.
/p or /update
- Applies a patch (.msp) file.

Example configuration

Here's an example of a valid .mst file to help sympathise how options can be changed along with the MSI directory for mozilla central:

MST file instance
MSI installer nightly builds
MSI installer electric current release build

Logging can exist 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:

Past using an external MSI editor (e.g. ORCA)

and select the MSI to be edited.
Find the Holding table and select it.
Change the values for the PROPERTIES you need to.
From ORCA, select and save the custom modified MSI installer.

Note that this will invalidate the MSI file'due south signature; if you need the file to be signed, you'll have to sign information technology again using your organization's document.

By using a transform (.mst) configuration

Utilize Orca to open the MSI.
Select Transform > New Transform from the menu bar.
Change the values for the Backdrop y'all 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 control line parameters

Rename the Firefox MSI file as default.msi
Move the file in a C:\MSI directory
Run:

msiexec.exe /i "c:\MSi\default.msi" INSTALL_DIRECTORY_PATH="C:\Firefox\" TASKBAR_SHORTCUT=false DESKTOP_SHORTCUT=imitation INSTALL_MAINTENANCE_SERVICE=false /quiet

All private parameters (FIREFOX specific, present in CAPS tin exist used in the command line + the msiexec public parameters like /i and /quiet in the above example)