After installing Firefox, some configuration may be desirable, examples may include:
- Block auto updates
- Set home page
- Disable Mozilla First Run Pages
- FW Admin
- Firefox installer application already as a Fileset
- The provided configuration Fileset:
- Download the Fileset zip file, expand and drag into FileWave > Filesets
- Two files are present in the Fileset.
The autoconfig.js file specifies the file to be used for configuration. In this Fileset the name of the file has been set to 'mozilla.cfg':
To specify any desired settings, edit the mozilla.cfg file. The provided file is designed to prevent Firefox updates, disable privacy telemetry, disable the first run Mozilla home pages and set the user's homepage:
Preference types can include: pref, defaultPref, lockPref, amongst others. Details can be found at: https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig
This is used to set a preference that can be overridden by the user, but on next launch of the application it will revert back to the setting within the configuration file
A lockPref cannot be overridden by the user
This is used to set a preference that can be overridden by the user. The user's setting will persist until the user resets them, at which point the defaultPref will be used on next launch of the application
Navigating to 'about:config' in the Firefox URL bar will list all possible preference names and their values and types.
When associating, to ensure the configuration is installed with the Application, consider creating a Fileset Group:
Associating the 'Firefox' Fileset Group will ensure both the Application and Configuration are associated to devices.
When there is an update to Firefox, replace the version in the Fileset Group with the latest version after testing.
Profile With macOS
A Configuration Profile may be delivered to macOS for Firefox management:
The linked plist file, may be imported into the FileWave Profile Editor ('Upload File...') and then edited appropriately.
The key settings to focus on initially are:
Default values in the template will require editing: EnterprisePoliciesEnabled should be enabled to allow management to take control. RequestedLocales may require editing to meet the specific needs.
The template is preconfigured as:
To change from German to British for example:
These settings would enforce management for en-GB and en-US, whilst other English locales, e.g en-CA, en-AU would not be managed. Instead, one locale of 'en' could be set to block all English locales.
If EnterprisePoliciesEnabled is not set as true and a correct RequestedLocales is not included, management should not be expected.
If unsure which locale is in use, without management in place the 'about:config' URL may be used to view settings:
To ensure users may not circumvent management by changing the locale, enable 'BlockAboutConfig' (already set as TRUE in the template file)