Can I use a Profile to deploy the same Firefox config to all users?
I manage a small office with a dozen users. We do an annual refresh of the PCs and so far I have manually managed configuring Firefox for each user. It takes a fair amount of time.
I add about a half dozen extensions, configure search providers and reconfigure the main tool bar (add remove icons). I have a bookmarks.json file I import to all users and I did, at least in the older 52- versions set up the the default new tab with favorites (icons) to the most relevant business sites. I believe that I can re-config some of the "top sites" functionality in about:config. I change other things in the config (This started today as learning how to config for session cookies) and want ALL users to start off with identical config and lower my effort
The only exception (I can think of) would be I would want to export their passwords and restore them back.
Can I do all this with building a profile and importing it to each user? How can I start with a clean profile (refresh Firefox?) How well do profiles survive version upgrades? Users will all be different. Does this paly in?
What can i NOT get from this and what am I not asking?
Geändert am
Alle Antworten (4)
Hi, there is no date or version number on this but deployment would be done this way : https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig
First, it sounds like the ESR version is the best for your Firefox needs.
"Extended Support Release (ESR) based on a regular release of Firefox for desktop for use by organizations including schools, universities, businesses and others who need extended support for mass deployments." https://www.mozilla.org/en-US/firefox/organizations/
And there is a separate area of this support forum for enterprise users. https://support.mozilla.org/en-US/products/firefox-enterprise
@Pkshadow, this may be the technically correct solution, but probably deeper and more controlling than I need.
I think I am asking if I can realistically build out Firefox on my PC and then export the profile to all the other users so I do not need to config (much) for the dozen or so clients? Not sure I want to spend the time understanding each policy, and do not need to "lock down" all the stuff, as much as give each user the same starting point.
@ the-edmeister, I did use the 52 ESR, mostly as some of the extensions were being sunset and I did not have good replacements (Save as MHT was big). This does look like a good option as opposed to the retail path. I am not clear, but will assume that, if I choose the ESR and allow updates that it will auto-update to point releases and not full number releases. Did not know that i could get point releases under 52 and set Firefox not to update.
I already have at least 2 clients that are over 60, including mine. I think I will try to take a sub-60 "test" machine and upgrade it to 60ESR and then downgrade mine and import the profile from the test machine. Seems like downgrading may be problematic with the profile, so I think agood test all around
Thoughts?
It is best to follow the update path for security for ESR as you are a business still so I would imagine that would be in the forefront to use 60.02esr rather than 52 which will come under attack now that it is not supported.