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

Policy.json wins over GPO

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 1 view
  • Last reply by Mike Kaply

Thanks Mike for the description here: https://support.mozilla.org/en-US/kb/firefox-enterprise-87-release-notes by Mike Kaply

Does the following section meant that policies.json would win a conflict with a setting that is also set in GPO: The policies.json file is no longer ignored if policies are specified via GPO (Windows) or configuration profiles (macOS). The policies are combined with GPO or configuration profile taking precedence over policies.json where there are conflicts.

Thanks Mike for the description here: https://support.mozilla.org/en-US/kb/firefox-enterprise-87-release-notes by Mike Kaply Does the following section meant that policies.json would win a conflict with a setting that is also set in GPO: '''The policies.json file is no longer ignored if policies are specified via GPO (Windows) or configuration profiles (macOS). The policies are combined with GPO or configuration profile taking precedence over policies.json where there are conflicts. '''

All Replies (3)

Note that ESR has transferred from 78.15.0 ESR to 91.3.0 ESR with the release of Firefox 94.

Thanks for pointing this out. We are moving very soon to the 91.3.0 version. But now we are still on 78.15.0 and this version jump would include the change I have mentioned before which was introduced in Firefox Rapid Release 87.0.

So this would be new to our 91.3.0 version and I just want to double check on this.

> Does the following section meant that policies.json would win a conflict with a setting that is also set in GPO:

No, GPO would win. That's what this statement says:

> The policies are combined with GPO or configuration profile taking precedence over policies.json where there are conflicts.

GPO takes precedence.

The reason it was done this way is because without this, a user could theoretically put a policies.json in a local copy of Firefox and overide policy set by their company in the registry.