Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Why does the GPO setting for "Disable Developer Tools = disabled" not take effect when mozilla.cfg "devtools.policy.disabled = true"?

  • 1 antwurd
  • 1 hat dit probleem
  • 17 werjeftes
  • Lêste antwurd fan Mike Kaply

Ed
Ed
more options

Our organization currently runs FirefoxESR versions and uses mozilla.cfg to control some lock down that are not available using the GPO. Below is the setting in question: 

     - mozilla.cfg 
            lockPref("devtools.policy.disabled", true);
     - GPO deviation setting
            Computer > Policies > Admin Templates > Mozilla > Firefox
                    Disable Developer Tools = Disabled

When the computer updates the policies and users launch Firefox, Developer Tools is missing as an option. Below are the results after gpupdate /force: 

    - about:config
            devtools.policy.disabled > locked > true
    - Registry (regedit) 
            HKLM\Software\Policies\Mozilla\Firefox
                  DisableDeveloperTools = 0

THANKS Everyone!

Our organization currently runs FirefoxESR versions and uses mozilla.cfg to control some lock down that are not available using the GPO. Below is the setting in question: - mozilla.cfg lockPref("devtools.policy.disabled", true); - GPO deviation setting Computer > Policies > Admin Templates > Mozilla > Firefox Disable Developer Tools = Disabled When the computer updates the policies and users launch Firefox, Developer Tools is missing as an option. Below are the results after gpupdate /force: - about:config devtools.policy.disabled > locked > true - Registry (regedit) HKLM\Software\Policies\Mozilla\Firefox DisableDeveloperTools = 0 THANKS Everyone!

Alle antwurden (1)

Mike Kaply
Mike Kaply
  • Moderator
more options

I'm a little confused by what you are trying to accomplish.

Are you trying to disable developer tools via Autoconfig and enable them via policies?

Because you have DisableDeveloperTools set to 0.