We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

How do I enable auto-updating in an enterprise environment?

  • 3 одговорa
  • 2 имају овај проблем
  • 78 прегледа
  • Последњи одговор послао Holden_Swann

more options

I have many devices running outdated versions of Mozilla Firefox in an enterprise environment and wish to force automatic updating to be enabled with SCCM. Is there a configuration file that's used to enable these settings for Firefox?

I've attempted to create a .cfg file and put it in the same directory as Firefox.exe, however the application doesn't seem to utilize the settings or the config file made. The line placed in defaults\pref\channel-prefs.js is lockPref("general.config.filename", "mozilla.cfg");

Any assistance in finding a solution for updating these devices would be greatly appreciated.

I have many devices running outdated versions of Mozilla Firefox in an enterprise environment and wish to force automatic updating to be enabled with SCCM. Is there a configuration file that's used to enable these settings for Firefox? I've attempted to create a .cfg file and put it in the same directory as Firefox.exe, however the application doesn't seem to utilize the settings or the config file made. The line placed in defaults\pref\channel-prefs.js is lockPref("general.config.filename", "mozilla.cfg"); Any assistance in finding a solution for updating these devices would be greatly appreciated.

Изабрано решење

You can't/shouldn't use lockPref in the file in defaults\pref folder and you shouldn't edit channel-prefs.js, but use a separate .js file instead.

See Configuration:


You can use the mozilla.cfg file in the Firefox program folder to set or lock preferences and run privileged JavaScript code.

The mozilla.cfg file needs to be in the main Firefox program folder.

These functions can be used in the mozilla.cfg file:

defaultPref();	// set new default value
pref();	// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

This requires a local-settings.js file in the "defaults/pref" folder where the channel-prefs.js file is located that specifies to use mozilla.cfg.

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

The mozilla.cfg file and possibly local-settings.js need to start with a comment line (//).

See also:

Прочитајте овај одговор са објашњењем 👍 1

Сви одговори (3)

more options

I'd suggest you use Firefox ESR and join the enterprise mailing list for help with your particular environment. https://www.mozilla.org/en-US/firefox/organizations/

more options

Одабрано решење

You can't/shouldn't use lockPref in the file in defaults\pref folder and you shouldn't edit channel-prefs.js, but use a separate .js file instead.

See Configuration:


You can use the mozilla.cfg file in the Firefox program folder to set or lock preferences and run privileged JavaScript code.

The mozilla.cfg file needs to be in the main Firefox program folder.

These functions can be used in the mozilla.cfg file:

defaultPref();	// set new default value
pref();	// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

This requires a local-settings.js file in the "defaults/pref" folder where the channel-prefs.js file is located that specifies to use mozilla.cfg.

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

The mozilla.cfg file and possibly local-settings.js need to start with a comment line (//).

See also:

more options

Thank you for your quick responses!

I removed the entries made to channel-pref.js and had a little bit of a fun time attempting to implement the .cfg file. I was getting an error message when opening Firefox stating the configuration file was incorrect.

It took me a moment to figure out that it was case sensitive for lockPref and I'd written lockpref for the updating piece.

I have a working solution at this point and have moved it into a powershell script that will be used as a configuration item inside of SCCM.

Thank you again for your assistance, great detail and links in your posts, as I wouldn't have been able to get this far without it.