For preferences on this list: http://kb.mozillazine.org/index.php?title=Category:Preferences you can use 2 files to lock preferences in place for both new and existing users.
The first file you need is local-settings.js. Unzip the firefox packaged exe, and create this file under defaults\pref. Then paste this:
This tells firefox to look for the locked config file firefox.cfg at the root level of the firefox program files folder. The obscure value 0 sets it to read the cfg as plain text, you can also byte shift the cfg by 13 (for encryption) if you want to but its not necessary.
The second file you need is firefox.cfg. Place this somewhere that your deployment solution can copy to clients. In this file you customize settings you wish to have locked. More info here on formatting: http://kb.mozillazine.org/Locking_preferences
Next you can deploy the setup.exe as usual, with -ms and /INI=filename if you want as suggested above. After that, run a script to copy firefox.cfg to the root level of the firefox program files folder. Those settings will then be locked for all users.
IMPORTANT: DO NOT MIX command line options from different lines below (e.g. don't mix /S with /INI, etc.)
Silent install (always installs into the default location. Use the "Configuration ini file" option below to set the install location and other install options):
<path to setup executable> -ms
Silent uninstall:
All version of Firefox
<path to setup executable> /S
Firefox 4.0 and later
<path to setup executable> -ms
Configuration ini file:
<path to setup executable> [/INI=<full path to configuration ini file>]
When specifying a configuration ini file the installer will always run silently. When specifying a Configuration ini file other command line switches should not be specified and may have unexpected results
Configuration ini file syntax and available settings:
[Install]
;
; Remove the semicolon (;) to un-comment a line.
;
; The name of the directory where the application will be installed in the
; system's program files directory. The security
; context the installer is running in must have write access to the
; installation directory. Also, the directory must not exist or if it exists
; it must be a directory and not a file. If any of these conditions are not met
; the installer will abort the installation with an error level of 2. If this
; value is specified then InstallDirectoryPath will be ignored.
; InstallDirectoryName=Mozilla Firefox
; The full path to the directory to install the application. The security
; context the installer is running in must have write access to the
; installation directory. Also, the directory must not exist or if it exists
; it must be a directory and not a file. If any of these conditions are not met
; the installer will abort the installation with an error level of 2.
; InstallDirectoryPath=c:\firefox
; By default all of the following shortcuts are created. To prevent the
; creation of a shortcut specify false for the shortcut you don't want created.
; Create a shortcut for the application in the current user's QuickLaunch
; directory.
; QuickLaunchShortcut=false
; Create a shortcut for the application on the desktop. This will create the
; shortcut in the All Users Desktop directory and if that fails this will
; attempt to create the shortcuts in the current user's Start Menu directory.
; DesktopShortcut=false
; Create shortcuts for the application in the Start Menu. This will create the
; shortcuts in the All Users Start Menu directory and if that fails this will
; attempt to create the shortcuts in the current user's Start Menu directory.
; StartMenuShortcuts=false
; The directory name to use for the StartMenu folder (not available with
; Firefox 4.0 and above - see note below).
; note: if StartMenuShortcuts=false is specified then this will be ignored.
; StartMenuDirectoryName=Mozilla Firefox
As of Firefox 4.0 StartMenuDirectoryName is ignored due to the removal of the start menu directory for Firefox and the creation of a start menu shortcut in the root of the start menu (see bug 598779).
you will find the folder "core" and the file "setup.exe"
2. in \core\defaults you have to create the folder "profile"
it should look like this: "\core\defaults\profile"
3. in this folder "profile" you can place your own user settings to share it to new firefox profiles
4. either you can place in this "profile" folder the file prefs.js for user settings or you use my method which is explained in point 5
5. instead of prefs.js - I placed one file in the profiles folder which is called "user.js"
By this file the user settings will also set AND if one user will change his own settings, after an restart of firefox - this file will reload my settings to this user
This method is only for new profiles. Existing user profiles will receive the settings either by active setup or by one script, which I have written.
In this script, I ask every existing local user folder for the file prefs.js. If this file existing - I will write in real time my user.js in the assigned Firefox profiles folder.
Now we have one deployable firefox package for new and existing firefox profiles.
These are my settings I am still testing but so far;
Download Firefox from
http://www.mozilla.com/en-US/firefox/all-older.html
Run the Firefox Setup until you get the âWelcome To the Mozilla Firefox Setup Wizardâ
Copy C:\Users\YourUserName\AppData\Local\Temp\7zS5205.tmp\All Files to a working directory on your desktop
The 7zS5205.tmp folder name will be different but it will hold the setup.exe and folders for the Firefox install
You can exit the setup wizard.
Open your working directory on your desktop
*Disable Migration Tool â Create an override.ini and place it at the root of you working directory
Copy this in that file
[XRE]
EnableProfileMigrator=false
*Create another file called Firefox.ini at the root and copy this to that file(I only want the start menu ICON)
[Install]
QuickLaunchShortcut=false
DesktopShortcut=false
StartMenuShortcuts=true
Search this file and edit you settings by changing what you donât want to false in you working folder
*Nonlocalized\defaults\pref\firefox.js
Disable Checking for Updates
pref("app.update.enabled", false);
Disable Check for Default browser.
pref("browser.shell.checkDefaultBrowser", false);
pref("extensions.update.enabled", false);
pref("browser.search.update", false);
pref("lightweightThemes.update.enabled", false);
pref("browser.tabs.warnOnClose", false);
pref("browser.warnOnQuit", false);
*Change the default home page
Edit localized\browserconfig.properties
Delete the page and copy this
browser.startup.homepage=http://www.google.com
Copy the working directory to the SCCM server create a package
*In SCCM command select the setup.exe then add this to the command line
setup.exe /INI="%CD%\FirefoxSetup.ini"
Now Deploy to your test computers, play with these setting, change what you donât like and keep the ones you do like
Pretty well all of the things that worked on 3.6.x work on 4.0 RC 1 & 2 so far.
I found that the exe you get from Mozilla is an sfx, so you can extract the files, apply your own customisations, and then re-pack the files into a Self Extracting exe file that calls ".\setup.exe". You can get it to call ".\setup.exe -ms" for silent deployment, or if you are cluey, you may be able to get it to pass the -ms flag. (I haven't got this to work for me yet though).
Step 1: Extract the <installEXE> file using a tool like 7zip.
Step 2: Apply any customisations (a few outlined below)
Step 3: Use 7zip or WinRAR (or other) to create an SFX self extractor. **Ensure that it calls ".\setup.exe" (or ".\setup.exe -ms" if you like).
Here are a few customisations I have used (thanks to those who initially found them):
**No Desktop Icon on install**
-Create a file called "nodesktop.ini" in the same folder as "setup.exe" with the contents:
[Install]
DesktopShortcut=false
**Disable the Import Bookmark Wizard**
- In the folder that contains "firefox.exe", create a file called "override.ini" with the contents:
[XRE]
EnableProfileMigrator=false
[/align]
**Management of firefox by Group Policy**
NOTE: ******You can do this for any extension*******
- I use a slightly modified version of the gpoFirefox extension for this. Just download and install the addon, then browse to %APPDATA%\Mozilla\Firefox\Profiles\#########.default\extensions, then copy the desired folder (for me this is gpofirefox@extensions.org) into the core\extensions folder.
**Change default prefs**
- Edit any of the *.js files that define any preferences you would like to change. I use this to define a few special prefs that are not normally defined in firefox, which means GPOFirefox can't manage them without first defining them.
**Default bookmarks / themes etc**
- In the core\defaults directory, make sure there is a folder called "profile", and you can add any default files you like for peoples profiles. We use this to deploy some workplace-specific bookmarks, personas, website pop-up exception rules, etc.
I wanted to deploy Firefox lockdowns WITHOUT using a GPO so this is how I got stuff to work.
ENSURE YOU HAVE WINZIP
ENSURE YOU KNOW ABOUT CFG FILES (if not then look here for information http://www.pcc-services.com/kixtart/firefox-lockdown.html)
1. Install Firefox 4 (using standard defaults)
2. Navigate to C:\Program Files\Mozilla Firefox
3. Right click the OMNI.JAR file and open with Winzip
4. Extract all files to a folder somewhere on the PC
5. Go to that extraction folder and you will see the files in their applicable folder structure.
6. Navigate to the defaults\profile\firefox.js
7. Add the following line to the end of that file
8. Save the file
9. Re-Zip all the files back into a file called OMNI.JAR
10. Replace the original OMNI.JAR file with the new one
11. Drop your mozilla.cfg file in the root of Program Files\Mozilla Firefox
12. Launch Firefox and see your lockdowns work
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
