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

Mozilla.cfg not applying to some users

  • 5 replies
  • 1 has this problem
  • 1 view
  • Paskiausią atsakymą parašė fihGramex

more options

Hi Mozilla Support. I'm trying to make a .cfg file to disable all addons in my corporate environment. I've made the .cfg and the .js and checked that they work on several users.

My problem is that for no apparent reason on some users it just doesn't work! I've tested with multiple users on one system where the files are present, and with some of the users it works, and with others it doesn't. Some are allowed to freely install addons and others get the "this has been disabled by admin" message. What's extra wierd is that I can see on the about:config page that the setting is present, it just doesn't apply.

Any ideas on why this is?

-Thanks in advance

Hi Mozilla Support. I'm trying to make a .cfg file to disable all addons in my corporate environment. I've made the .cfg and the .js and checked that they work on several users. My problem is that for no apparent reason on some users it just doesn't work! I've tested with multiple users on one system where the files are present, and with some of the users it works, and with others it doesn't. Some are allowed to freely install addons and others get the "this has been disabled by admin" message. What's extra wierd is that I can see on the about:config page that the setting is present, it just doesn't apply. Any ideas on why this is? -Thanks in advance

Chosen solution

cor-el said

The file content looks OK to me, so I assume that this should work. Did you check the ownership and permissions for both files to make sure that all users have access? Is there only one Firefox installation (this is the 32 bit Firefox version)? If local-settings.js is found and applied then you won't be able to start Firefox if there is a problem with mozilla.cfg. You could check the startup sequence with Process Monitor to see if the files are accessed.

I solved it. The problem was that firefox was for some reason installed in appdata in stead of Program Files! It also turned out that my test client had two versions of Firefox installed -one under appdata and one in program files. Is there any reason why it would install under appdata? Might it be that it's an old installation made in the days before admin controlled installation on the individual clients? (I know, the admin then was a doof)

Skaityti atsakymą kartu su kontekstu 👍 0

All Replies (5)

more options

Could you post the content of the mozilla.cfg file?

Are you only using lockPref() or also defaultPref() and pref()?

more options

cor-el said

Could you post the content of the mozilla.cfg file? Are you only using lockPref() or also defaultPref() and pref()?

I'm using both lockPref() and pref(). My batch files look like this:

#1
@echo off
echo pref("general.config.obscure_value", 0); > C:\local-settings.js
echo pref("general.config.filename", "mozilla.cfg"); >> C:\local-settings.js

move "C:\local-settings.js" "C:\Program Files (x86)\Mozilla Firefox\defaults\pref"
exit

#2
@Echo off
echo //Firefox Default Settings > C:\mozilla.cfg
echo //Disable add-on installation >> C:\mozilla.cfg
echo lockPref("xpinstall.enabled", false); >> C:\mozilla.cfg

move "C:\mozilla.cfg" "C:\Program Files (x86)\Mozilla Firefox"
exit

Do you need the entire .cfg? Thanks for the response BTW

Modified by cor-el

more options

The file content looks OK to me, so I assume that this should work.

Did you check the ownership and permissions for both files to make sure that all users have access?

Is there only one Firefox installation (this is the 32 bit Firefox version)?

If local-settings.js is found and applied then you won't be able to start Firefox if there is a problem with mozilla.cfg.

You could check the startup sequence with Process Monitor to see if the files are accessed.

more options

Chosen Solution

cor-el said

The file content looks OK to me, so I assume that this should work. Did you check the ownership and permissions for both files to make sure that all users have access? Is there only one Firefox installation (this is the 32 bit Firefox version)? If local-settings.js is found and applied then you won't be able to start Firefox if there is a problem with mozilla.cfg. You could check the startup sequence with Process Monitor to see if the files are accessed.

I solved it. The problem was that firefox was for some reason installed in appdata in stead of Program Files! It also turned out that my test client had two versions of Firefox installed -one under appdata and one in program files. Is there any reason why it would install under appdata? Might it be that it's an old installation made in the days before admin controlled installation on the individual clients? (I know, the admin then was a doof)

more options

cor-el said

The file content looks OK to me, so I assume that this should work. Did you check the ownership and permissions for both files to make sure that all users have access? Is there only one Firefox installation (this is the 32 bit Firefox version)? If local-settings.js is found and applied then you won't be able to start Firefox if there is a problem with mozilla.cfg. You could check the startup sequence with Process Monitor to see if the files are accessed.

Thank you for the help BTW! While I have you here, you wouldn't happen to know how to whitelist say, Adblock using the pref() or lockpref()? :)