Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Deploying Firefox ESR in an enterprise environment

  • 7 odpovedí
  • 3 majú tento problém
  • 13 zobrazení
  • Posledná odpoveď od Firefoxa

more options

Hi All, Currently Firefox is installed in our environment used by approx 400-500 users. We update Firefox twice a year to provide minimal impact to users although with security being a concern i believe Firefox esr is available and provides minor security patches but i'm unclear if this is the way to go.

Can someone please provide some guidance on a recommended way to roll out Firefox in an enterprise environment? How should we handle updates (auto updates turned on or off)? How do we handle Rollbacks? Etc.

Thanks

Hi All, Currently Firefox is installed in our environment used by approx 400-500 users. We update Firefox twice a year to provide minimal impact to users although with security being a concern i believe Firefox esr is available and provides minor security patches but i'm unclear if this is the way to go. Can someone please provide some guidance on a recommended way to roll out Firefox in an enterprise environment? How should we handle updates (auto updates turned on or off)? How do we handle Rollbacks? Etc. Thanks

Všetky odpovede (7)

more options
more options

cor-el said

See:

Cor-el,

Ive read this but it doesn't mention anything about rollback? If also i have auto updates turned on in ESR when it hits a major release do i have to upgrade firefox again once it stops updating? Will it wipe my customizations? etc

Thanks

more options

There is usually no need to rollback a minor ESR update that involves security updates.

For a major update like will happen with the switch from Firefox 38.x.0 ESR to 45.x.0 ESR there is an overlap that allows to test for issue before making the switch for all users as you can see in the diagram on the FAQ page.

more options

When 45.2.0 ESR is out the 38.8.0esr which came out when 45.1.0esr did will be EOL.

The Firefox 45 ESR will be until 45.8.0ESR when Firefox 53.0 is released unless Mozilla decides to extends support for 45 ESR in order to support Mac OSX 10.6-10.8 users and those on Windows that does not have SS2.

more options

cor-el said

There is usually no need to rollback a minor ESR update that involves security updates. For a major update like will happen with the switch from Firefox 38.x.0 ESR to 45.x.0 ESR there is an overlap that allows to test for issue before making the switch for all users as you can see in the diagram on the FAQ page.


I noticed when i install ESR and an update is available its asking to go to https://www.mozilla.org/firefox ? Is this correct, does it not just auto update when an update is available without having the user have to manually go to the webpage, download the stub update and then install it? See the attached image.

more options

Firefox 45.1.0 ESR is the current as 45.2.0 ESR will be out on June 7th.

https://wiki.mozilla.org/RapidRelease/Calendar

more options

Firefoxa said

cor-el said
There is usually no need to rollback a minor ESR update that involves security updates. For a major update like will happen with the switch from Firefox 38.x.0 ESR to 45.x.0 ESR there is an overlap that allows to test for issue before making the switch for all users as you can see in the diagram on the FAQ page.


I noticed when i install ESR and an update is available its asking to go to https://www.mozilla.org/firefox ? Is this correct, does it not just auto update when an update is available without having the user have to manually go to the webpage, download the stub update and then install it? See the attached image.

Worked out the maintenance service was not ticked on install. Now installs are occurring automatically :)