distribution_policies.json (folder and file) removed when installing (or upgrade) new FF version.
Hi,
We are creating and testing an easy method of a FireFox deployment within our environment. The result has to be : Easy installation and update of FireFox ánd easy setup of Firefox settings (both separated, but dependent) within our organization.
While started on the 'old' track, we have implemented the new method and forgot the 'old' stuff. We are using the 'autoconfiguration' and 'policies.json' -method, both using manual files. With a base installation of Firefox (using .INI) and installing the settings, everything works as a charme. The policies are there (as file) and also in Firefox and so are the autoconfiguration settings. At this point, there is no problem.
When installating a new update of Firefox, using the setup.<version>.exe , the distribution folder (with the policies.json -file) is removed from the FireFox installation folder, while the autoconfiguration files are still there (defaults -folder). Firefox is not started and does not access these files. I've tried installing with and without the .INI and also tried different versions (60.3.0ESR, 61.0.2 RR, 62.0.0 RR, 62.0.3 RR). In all cases, the distribution folder is removed.
Is there an unknown option to be set in the .INI to preserve this distrubution -folder, or is it a bug ?
I hope you can help us with matters.
With best Regards,
Mike
Izabrano rješenje
hi mike, running the setup file to update an installation is expected to remove the distribution subfolder. however you could change that behaviour by running the setup with the command switch
/RemoveDistributionDir=false
https://firefox-source-docs.mozilla.org/browser/installer/windows/installer/FullConfig.html
Pročitajte ovaj odgovor sa objašnjenjem 👍 1All Replies (5)
I think that you will have to provide a manual update with a .mar file to ensure that you keep all customization files.
- https://developer.mozilla.org/en/Setting_up_an_update_server
- https://wiki.mozilla.org/Software_Update:Manually_Installing_a_MAR_file
Otherwise you would have to modify the setup file and include a distribution folder and possibly autoconfig.js and autoconfig.cfg in the correct folders. I wouldn't have expected that autoconfig files would survive a full install.
Hi Cor-el,
Thank you very much for your answer.
Our goal is to setup a FF installation with a separate configuration, resulting in two installations, which are dependent, but manageable per item. With every update or change, we've just to replace one of the installations (SCCM application). Autoupdate is disabled and an extra system (web server) for updates will require extra time to manage.
For now, we are going to use a work-a-round, where a script is first installing Firefox and then (re-)install the configuration. By (re-)installing the configuration as the last item, the settings are there and are not deleted by the FF -installation.
Hopefully, we will find a better solution in the future.
With best regards, Mike
PS. We are using a x64 Windows 10 environment with AD. GPO is NOT used, because it can not reach every system.
Mike, we use SCCM to deploy and update Firefox (among other applications) and use PowerShell script to install the update using the setup.ini to limit some installed features (desktop icon and maintenance) and then to copy the local-settings.js and mozilla.cfg to the appropriate locations on Windows. It should be possible to add lines to the PS1 script to include the policy.json being copied to .\distribution\
Odabrano rješenje
hi mike, running the setup file to update an installation is expected to remove the distribution subfolder. however you could change that behaviour by running the setup with the command switch
/RemoveDistributionDir=false
https://firefox-source-docs.mozilla.org/browser/installer/windows/installer/FullConfig.html
How stupid that I have not seen (or found) this webpage.
I have done some testing on a clean machine. It is not working with version 62 of Firefox (in .INI or as command switch). With version 63 and newer, it is only working as a command switch. That will be enough for me.