How do I lockdown certain options in Firefox 10.0.7esr so I can deploy to the enterprise?
I have some settings in the user.js file and those seem to be working, but I can't lockdown a user from changing the setting for "auto updates". I can set the setting to "never check for updates", but I can't lock it down. How can I lock it down so a user can't change the setting? Our environment is very tight and the user can't install software nor download software from the internet, so we need to lock this setting down.
გადაწყვეტა შერჩეულია
The "lockPref" statement I was using in my mozilla.cfg file was not typed correctly. It is a case sensitive command and I didn't have the "P" capitalized. Once I capitalized the "P" it all worked as intended. Thanks for the assistance.
პასუხის ნახვა სრულად 👍 0ყველა პასუხი (6)
Hi lockdown
try this : in about:config find app.update.enabled and make it FALSE (just double click on it). Then see how to lock it : Locking preferences.
thank you
I already have mozilla.cfg file with the setting I want, so tomorrow I will review the URL you sent and see if I can get it to work. Thank you for the information.
I can not get it to read the the mozilla.cfg file, which is a text file so I created the local-settings.js file with the settings: pref("general.config.obscure_value", 0);
pref("general.config.filename", "mozilla.cfg");
Then when I execute Firefox it says it can't read the configuration file and exits. So I take out the first line in the local-settings.js file above. and then execute Firefox. Firefox starts up but doesn't have any of my settings in the config file.
A previous person that built the install for the 10.0.6esr had put the configuration modifications in a user.js file that gets placed in the user's profile. And this works fine. But I can't seem to get it to recognize the "lockpref" statement.
Any suggestions would be appreciated.
ჩასწორების თარიღი: , ავტორი: lockdown
შერჩეული გადაწყვეტა
The "lockPref" statement I was using in my mozilla.cfg file was not typed correctly. It is a case sensitive command and I didn't have the "P" capitalized. Once I capitalized the "P" it all worked as intended. Thanks for the assistance.
you are welcome