Diễn đàn hỗ trợ Firefox Enterprise

I have Mozilla Firefox and Mozilla ESR browsers updates to manage across the devices. Policies have been configured on browser from Intune and same has been reflected everywhere in registry, and update.json file. still task is missing. can someone help on this. Also i have few ESR so will same ADMX file will work for that?

Hi all,

We use a service integration in our organization that only works in the latest ESR version of Firefox (140.14). The latest regular release breaks our integration due to added security policies preventing the software from communicating with Windows services.

After installing the ESR version and disabling auto updates in the settings and adding the DisableAppUpdate registry key, the software still keeps updating to 154 (not the ESR version). I've also chosen to not install the Mozilla Maintenance service when installing the ESR version. I can't seem to find any support articles of people having the same issue. Is there something I may be missing? Any help would be greatly appreciated.

Recently we've began installing Firefox 140.2.0esr to our environment via the .msi file that Mozilla provides, however we're running in to a very odd incident.

After approximately 24 hours from installing Firefox esr to devices, it appears that the application is "updating" to 141.0.3 on the "release" channel. As far as I'm aware, this shouldn't be possible to begin with. But we've applied these settings via GPO:

Computer Config > Policies > Admin Templates > Mozilla > Firefox Application Autoupdate = Disabled Pin updates to a specific version = Enabled = Set to 140.2.0 Background updater = Disabled Disable Update = Enabled Manual Update Only = Enabled

After applying the GPO, confirmed this appears within the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\ AppAutoUpdate = 0 AppUpdatePin = 140.2.0 BackgroundAppUpdate = 0 DisableAppUpdate = 1 ManualAppUpdateOnly = 1

At this point, I'm at a loss. We cannot have rapid release be what's installed in our environment. Is there something broken with 140.2.0 or are we doing something wrong here?

When a user logs onto the PC, FF creates the Task scheduler folder but not the task inside. This only get created once the user opens FF for the first time.

So as an admin how would I manage the updates for FF when the user never opens Firefox?