Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Do "ESR Only" settings still work on non-ESR via .cfg file? Does GPO 'win' in this case?

  • 3 replies
  • 1 has this problem
  • 14 views
  • Last reply by cor-el

more options

Hello,

We deploy Firefox with updates disabled by mozilla.cfg, but now the app is updating automatically.

  • Mozilla.cfg - settings correct here
  • Prefs.Js - shows update settings are not applied
  • User.js - does not exist

In particular, the settings of auto-update, homepage, and similar ones noted as "ESR Only" have been ignored.

But those settings should be still working via Autoconfig, right?

\Program Files (x86)\Mozilla Firefox\Mozilla.cfg:

 // Disable application auto-update
 lockPref("app.update.auto", false);
 lockPref("app.update.backgroundErrors", 2);
 lockPref("app.update.disable_button.showUpdateHistory", false);
 lockPref("app.update.enabled", false);
 lockPref("app.update.service.enabled", false);
 (..and more)

\Program Files (x86)\Mozilla Firefox\defaults\pref\autoconfig.js:

 pref("general.config.obscure_value", 0);
 pref("general.config.filename", "Mozilla.cfg");

\Program Files (x86)\Mozilla Firefox\defaults\pref\channel-prefs.js:

 * This Source Code Form is subject to the terms of the Mozilla Public
  * License, v. 2.0. If a copy of the MPL was not distributed with this
  * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
 
 pref("app.update.channel", "release");
Hello, We deploy Firefox with updates disabled by mozilla.cfg, but now the app is updating automatically. * Mozilla.cfg - settings correct here * Prefs.Js - shows update settings are not applied * User.js - does not exist In particular, the settings of auto-update, homepage, and similar ones noted as "ESR Only" have been ignored. * https://github.com/mozilla/policy-templates/blob/master/README.md But those settings should be still working via Autoconfig, right? \Program Files (x86)\Mozilla Firefox\Mozilla.cfg: // Disable application auto-update lockPref("app.update.auto", false); lockPref("app.update.backgroundErrors", 2); lockPref("app.update.disable_button.showUpdateHistory", false); lockPref("app.update.enabled", false); lockPref("app.update.service.enabled", false); (..and more) \Program Files (x86)\Mozilla Firefox\defaults\pref\autoconfig.js: pref("general.config.obscure_value", 0); pref("general.config.filename", "Mozilla.cfg"); \Program Files (x86)\Mozilla Firefox\defaults\pref\channel-prefs.js: * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ pref("app.update.channel", "release");

Modified by AnotherBlake

All Replies (3)

more options

Your issue to figure out a new cfg file, g'luck

Type about:preferences#advanced<enter> in the address bar. Under Advanced, Select Update.

[v56+] Type about:preferences#general<enter> in the address bar. Select Update.

Select Never Check For Updates.

Also turn off Use a background service to install updates <Windows Only>

Further you can rename Updater.exe to updater-old.exe

Please let us know if this solved your issue or if need further assistance.

more options

Hi Blake, According to your data, you're using Firefox 59.0. Is your question about a deployment of Firefox ESR, not the version you're using?

more options

The filename is usually mozilla.cfg and not Mozilla.cfg. Also make sure that both files start with a comment line (//) because the first line is ignored for security reasons. You can use the mozilla.cfg file in the Firefox program folder to initialize (set/lock) preferences and run privileged JavaScript code.

//
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);

See also: