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

setting lock preferences on win 10 enterprise

  • 1 reply
  • 1 has this problem
  • 5 views
  • Last reply by cor-el

more options

I created the .cfg and .js files. the .js file has the following lines in it: pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0); When i implement the lock preferences, they do not get set. If i remove the line: pref("general.config.obscure_value", 0); the lock preferences do get set however when i open Firefox i receive an autoconfig alert. I need to have the lock preferences set and not receive an autoconfig alert I am using Mozilla Firefox V63.0.3. Any assistance would be greatly appreciated.

I created the .cfg and .js files. the .js file has the following lines in it: pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0); When i implement the lock preferences, they do not get set. If i remove the line: pref("general.config.obscure_value", 0); the lock preferences do get set however when i open Firefox i receive an autoconfig alert. I need to have the lock preferences set and not receive an autoconfig alert I am using Mozilla Firefox V63.0.3. Any assistance would be greatly appreciated.

Modified by user1607246

All Replies (1)

more options

Are you starting each of the two files with a comment line? You can also use Unix line endings (LF and not CR/LF).

You can use the autoconfig.cfg file in the Firefox program folder to initialize (set/lock) preferences and run privileged JavaScript code.

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

This requires an autoconfig.cfg.js file in the "defaults\pref" folder where the channel-prefs.js file is located that specifies to use autoconfig.cfg.

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

The autoconfig.cfg and autoconfig.js files need to start with a comment line (//) and autoconfig.cfg needs to use Unix line endings (LF).