Hi Eric, I've had a quick look and the functionality would be useful, but when they wrote our software acquisition policy it expressly forbids using modified software, and that we can only use software we've obtained directly from the originator. <sigh>
If you can get that kind of functionality into the ESR version, that would be really beneficial. Regards Will Will Spratt IT Science Support Specialist Tel: 01904 46 2631 From: Ing-Long Eric Kuo [mailto:[email protected]] Sent: 20 December 2017 14:46 To: Kaply Consulting <[email protected]>; William Spratt <[email protected]> Cc: [email protected] Subject: RE: [Mozilla Enterprise] Announcing the next Extended Support Release of Firefox - ESR60 with policy engine Hello William, I want to chime in here, and get your thoughts. I am (hopefully) going to be helping Mike and the Mozilla team to make the GPO part useful for your use case. I am not sure if you have looked at the FrontMotion community edition. But for the policy engine, the idea is to formally take the thing that worked from the community edition, combine with some user friendliness and deeper integration and make it easily to deploy using Group Policy through administrative templates. -Eric ________________________________ From: Enterprise <[email protected]<mailto:[email protected]>> on behalf of Kaply Consulting <[email protected]<mailto:[email protected]>> Sent: Wednesday, December 20, 2017 8:07:37 AM To: William Spratt Cc: [email protected]<mailto:[email protected]> Subject: Re: [Mozilla Enterprise] Announcing the next Extended Support Release of Firefox - ESR60 with policy engine > Are you saying we'll do something similar with "configuration.json", and that > this will replace the two files we currently use? And that eventually we'll > be able to set these via GPO, and so won't need to deploy > "configuration.json"? Yes, that is the plan. Mike On Wed, Dec 20, 2017 at 8:03 AM, William Spratt <[email protected]<mailto:[email protected]>> wrote: Hi All, So, at the moment during deployment (post-installation) we drop a file named "local-settings.js" into "%PROGRAMFILES%\Mozilla Firefox\defaults\pref\" and a file named "mozilla.cfg" is dropped into "%PROGRAMFILES%\Mozilla Firefox\". All "local-settings.js" does is tell Firefox to look at "mozilla.cfg", and all that does is turn off the auto-updater and set the homepage to our intranet page with Firefox set to auto-detect the proxy. Are you saying we'll do something similar with "configuration.json", and that this will replace the two files we currently use? And that eventually we'll be able to set these via GPO, and so won't need to deploy "configuration.json"? Regards Will Will Spratt IT Science Support Specialist Tel: 01904 46 2631 From: Enterprise [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Sylvestre Ledru Sent: 20 December 2017 13:07 To: [email protected]<mailto:[email protected]> Subject: [Mozilla Enterprise] Announcing the next Extended Support Release of Firefox - ESR60 with policy engine The Firefox ESR (extended support release) is based on an official release of Firefox desktop for use by organizations including schools, universities, businesses and others who need extended support for mass deployments. Since Firefox 10, ESR has grown in popularity and many large organizations rely on it to let their employees browse the Internet securely. We want to make customization of Firefox deployments simpler for system administrators and we're pleased to announce that our next ESR version, Firefox 60, will include a policy engine that increases customization possibilities and integration into existing management systems. What is the policy engine? The Policy Engine is a project to build a Firefox desktop configuration and customization feature for enterprise users. The policy engine will work with any tool that wants to set policies and we intend to bring Windows Group Policy support soon. We'll be initially supporting a limited set of policies but this will be evolving through user feedback. More details on the policy engine can be found here.<https://wiki.mozilla.org/Firefox/EnterprisePolicies> Bug reference<https://bugzilla.mozilla.org/show_bug.cgi?id=1419102> What's the plan? In order to accommodate the group policy implementation, we are making Firefox 60 our next ESR version and will be following this plan: * May 8th - ESR 60.0 released (we'd love feedback from early adopters at that point and will be sharing a feedback form through the enterprise mailing list) * July 3rd - ESR 60.1 released * August 28th - End of life for ESR 52 and release of ESR 60.2.0. No further updates will be offered for ESR52 and an update to ESR60.0.2 will be provided through the application update service Also please keep in mind that Firefox 57, released last month, supports only add-ons built with the WebExtensions API<https://developer.mozilla.org/en-US/Add-ons/WebExtensions>. This means that Firefox 52 ESR is the last release that will support legacy add-ons. If you developed an add-on that has not been updated to the WebExtensions API, there is still time to do so. Documentation<https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on> is available, and you can ask questions by emailing [email protected]<mailto:[email protected]> or joining the #webextensions channel at irc.mozilla.org<http://irc.mozilla.org>. If you are supporting users who use add-ons, now is a good time to encourage them to check if their add-on works<https://support.mozilla.org/en-US/kb/frequently-asked-questions-firefox-addon> with Firefox 57+. Erin, Felipe, Jeff, Kev, Mike Kaply, Romain, Shell & Sylvestre _______________________________________________ Enterprise mailing list [email protected]<mailto:[email protected]> https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected]<mailto:[email protected]> with a subject of "unsubscribe"
_______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
