X
Tap here to go to the mobile version of the site.

Support Forum

Deploying Firefox ESR in an enterprise environment

Posted

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

Additional System Details

Installed Plug-ins

  • ActiveTouch General Plugin Container Version 105
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.10
  • Citrix Online App Detector Plugin
  • Google Update
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Next Generation Java Plug-in 1.6.0_21 for Mozilla browsers
  • The plugin allows you to have a better experience with Microsoft Lync
  • The plugin allows you to have a better experience with Microsoft SharePoint
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Shockwave Flash 21.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.1.7.157
  • 5.1.41212.0
  • The VMware Client Support Plug-in
  • VMware Remote Console Plug-in
  • VMware Remote Console and Client Integration Plug-in
  • NPWLPG

Application

  • Firefox 41.0.1
  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
  • Support URL: https://support.mozilla.org/1/firefox/41.0.1/WINNT/en-US/

Extensions

  • FiddlerHook 2.6.0.4 (fiddlerhook@fiddler2.com) (Inactive)
  • McAfee ScriptScan for Firefox 15.4.0 ({D19CA586-DD6C-4a0a-96F8-14644F340D60}) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) HD Graphics Family
  • adapterDescription2:
  • adapterDeviceID: 0x0102
  • adapterDeviceID2:
  • adapterDrivers: igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID: 04ad1028
  • adapterSubsysID2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.17568
  • driverDate: 6-10-2011
  • driverDate2:
  • driverVersion: 8.15.10.2418
  • driverVersion2:
  • failures: [u'[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(9180,16) Code: 0x80070057', u'[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(9180,16) Code: 0x80070057', u'[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(9180,16) Code: 0x80070057', u'[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(9180,16) Code: 0x80070057', u'[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(9180,16) Code: 0x80070057', u'[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(9180,16) Code: 0x80070057']
  • indices: [0, 11, 12, 13, 14, 10]
  • info: {u'AzureCanvasBackend': u'direct2d 1.1', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d 1.1', u'AzureSkiaAccelerated': 0}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • supportsHardwareH264: True
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11

Modified Preferences

Misc

  • User JS: Yes
  • Accessibility: No
cor-el
  • Top 10 Contributor
  • Moderator
17876 solutions 161748 answers
See: *https://www.mozilla.org/en-US/firefox/organizations/faq/

Question owner

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

''cor-el [[#answer-883365|said]]'' <blockquote> See: *https://www.mozilla.org/en-US/firefox/organizations/faq/ </blockquote> 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
cor-el
  • Top 10 Contributor
  • Moderator
17876 solutions 161748 answers

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.

There is usually no need to rollback a minor ESR update that involves security updates. *https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html 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.
James
  • Moderator
1603 solutions 11349 answers

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.

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.

Question owner

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.

''cor-el [[#answer-883424|said]]'' <blockquote> There is usually no need to rollback a minor ESR update that involves security updates. *https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html 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. </blockquote> 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.
James
  • Moderator
1603 solutions 11349 answers

Helpful Reply

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

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

Question owner

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 :)

''Firefoxa [[#answer-883437|said]]'' <blockquote> ''cor-el [[#answer-883424|said]]'' <blockquote> There is usually no need to rollback a minor ESR update that involves security updates. *https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html 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. </blockquote> 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. </blockquote> Worked out the maintenance service was not ticked on install. Now installs are occurring automatically :)