Wo le biabia siwo wotag la fiam: Fia biabiawo katã
  • Wo ɖo eŋu
  • Wode archive me

Intune ExtensionSettings Policy No Longer Working in Firefox

Hello, in Firefox browser, my organization has always blocked all extensions except for ones we allow through OMA-URI ./Device/Vendor/MSFT/Policy/Config/Firefox~Policy~fi… (xle nububuwo)

Hello, in Firefox browser, my organization has always blocked all extensions except for ones we allow through OMA-URI ./Device/Vendor/MSFT/Policy/Config/Firefox~Policy~firefox~Extensions/ExtensionSettings.

About a month ago this stopped working and our end users can now install any extension in the Firefox browser that they choose, without approval, creating a security risk.

When checking in about:policies, there is a policy error: Unable to parse JSON for ExtensionSettings. We have checked with Microsoft Intune support and they verified that the policy looks to be configured and targeted correctly.

Here is a snippet of our JSON, this is a test policy where microsoft support had us remove "about:addons" from the 'install sources'. Both test and production policies are not working.

<enabled/>
<data id="ExtensionSettings" value='
{
    "*": {
        "blocked_install_message": "Contact Service Line",
        "install_sources": ["https://addons.mozilla.org/*"],
        "installation_mode": "blocked",
        "allowed_types": ["extension"]
    },
    "cloudmetering@snowsoftware.com": {
        "installation_mode": "force_installed",
        "install_url": "file:///C:/Program Files/Snow Software/Inventory/Agent/FFCloudmetering.xpi"
    },
    "fpdlpffext2@forcepoint.com": {
        "installation_mode": "force_installed",
        "install_url": "file:///C:/Program Files/Websense/Websense Endpoint/winFFext.xpi"
    },
    "jid1-5AULKXLKGyjuLQ@jetpack": {
        "installation_mode": "allowed"
    },
    "abb@amazon.com": {
        "installation_mode": "allowed"
    },
    "ciscowebexstart1@cisco.com": {
        "installation_mode": "allowed"
    },
    "linkedinConverted@firefox-extension": {
        "installation_mode": "allowed"
    },
    "{7bc53591-5218-45a0-b572-4366979097fd}": {
        "installation_mode": "allowed"
    },
    "queryamoid@kaply.com": {
        "installation_mode": "allowed"
    },
    "jid1-93WyvpgvxzGATw@jetpack": {
        "installation_mode": "allowed"
    },

Is this a bug? Or something wrong with our configuration? Has firefox changed the requirements of the extensionsettings OMA-URI?

Thanks for any help in advance.

Asked by victoria.gray 1 ƒe si va yi

Answered by victoria.gray 1 ƒe si va yi

  • Wode archive me

Windows 10: Automatic updates by GPO fails

Hi, i'm running Firefox on +70 Windows 10 PCs in three labs in a university. I've applied a computer configuration GPO with AppAutoUpdate enabled, BackgroundAppUpdate en… (xle nububuwo)

Hi,

i'm running Firefox on +70 Windows 10 PCs in three labs in a university. I've applied a computer configuration GPO with AppAutoUpdate enabled, BackgroundAppUpdate enabled and DisableAppUpdate disabled to my PCs, but it looks like i don't get automatic updates. In my labs i see some workstations have Firefox 108.0.1, but most workstations still have Firefox 107.0.1...

As my users can switch between workstations and labs, this leads to the annoying 'older version' message box when a user worked on a PC which already got the update and later uses another PC which didn't get the update. The users are also forced to create a 'new' profile then, which is quite problematic because of the size of the roaming profiles.

Any hints?

Asked by HTW IMI 1 ƒe si va yi

Last reply by Mike Kaply 1 ƒe si va yi