disable app update
Hi,
I'm used to deploying/configuring Firefox in an organization with settings in autoconfig.js, etc. Recently, I've seen that some settings are honored, others aren't, so I started using policies.json as well as keeping my autoconfig.js. Can they work together?
In any case, I am unable to disable app update with either of them. I have the following in policies.json:
{
"policies": {
"DisableFirefoxAccounts": true, "DisablePocket": true,
"DisableAppUpdate": true,
"DontCheckDefaultBrowser": true, "DNSOverHTTPS": { "Enabled": false }, "Certificates": { "ImportEnterpriseRoots": true } "PopupBlocking": { "Allow": ["http://10.215.144.56:8080", "https://intranet.mydomain.org"], "Default": true | false, "Locked": true | false }
}
}
I'm also showing a snippet of my autoconfig.js file:
lockPref("app.update.auto", false); lockPref("app.update.enabled", false); lockPref("app.update.mode", 0); lockPref("app.update.service.enabled", false); lockPref("app.update.disable_button.showUpdateHistory", false); lockPref("app.update.url", ""); lockPref("app.update.url.details", ""); lockPref("app.update.url.manual", ""); lockPref("signon.rememberSignons", false); lockPref("extensions.update.enabled", false);
The problem is that when I start Firefox 78.3.0 ESR and go to the about Firefox window, I can see that the app update is not disabled.
How can I make sure that all the above settings in autoconfig.js are actually honored?
Thanks
Избрано решение
app.update.enabled is no longer supported and thus won't have effect. app.update.auto is still supported and should work and controls this setting.
- Automatically install updates (recommended)
- Check for updates but let you choose to install them
There is no list possible for all pref settings you can use in autoconfig.cfg. You can possibly search the Firefox source code if you want to know if a pref still has effect.
Note that in some cases you may have to leave out leading branches in the pref name.
Прочетете този отговор в контекста 👍 0Всички отговори (3)
You can check the Browser Console for possible error messages about autoconfig.cfg (this file is run a privileged JavaScript).
You can check the about:policies page to see if there are errors reported. Of course true | false is not a valid value and you need to use either of true or false.
"PopupBlocking": {
"Allow": ["http://10.215.144.56:8080",
"https://intranet.mydomain.org"],
"Default": true | false,
"Locked": true | false
}
Променено на от cor-el
Right, that was a mistake on my behalf. Thanks for pointing me to about:policies. I didn't know about it.
BTW, am I right if I understand that PopupBlocking -> Default = true means that popups are blocked by default?
Also, the browser console (F12) shows no errors (I'm pressing F12 after starting Friefox and loading the home page). I know some settings in autoconfig.js are actually applied, so why weren't these?
lockPref("app.update.auto", false); lockPref("app.update.enabled", false);
Are they obsolete?
Where can I find a list of currently valid options for autoconfig.js like there is for policies.json?
Thanks
Променено на от vieri
Избрано решение
app.update.enabled is no longer supported and thus won't have effect. app.update.auto is still supported and should work and controls this setting.
- Automatically install updates (recommended)
- Check for updates but let you choose to install them
There is no list possible for all pref settings you can use in autoconfig.cfg. You can possibly search the Firefox source code if you want to know if a pref still has effect.
Note that in some cases you may have to leave out leading branches in the pref name.