Firefox:2.0 Institutional Deployment: Difference between revisions

← Older edit

Firefox:2.0 Institutional Deployment (view source)

Revision as of 01:15, 12 January 2007

2,317 bytes added , 12 January 2007

→‎Useful Tools: add alain.knaff.lu reference

Guanxi

2

edits

@@ Line 32: / Line 32: @@
 I'm documenting this as I'm doing it ... I'm trying to stick the extensions in the ALL Users section or the slightly worse Default user's section.
+== Needed Features ==
+The biggest pet peeve our users had was losing their Favorites in IE when getting a new computer or due to a harddrive failure.  It was tedious and often forgotten to back these up by the tech staff.  I easily remedied this using Active Directory to redirect the Favorites location to a network share in the form:  \\server\share\Favorites\%username%.
+At this point it's a showstopper for me to deploy Firefox in our enterprise without being able to redirect the bookmarks location.  With Firefox's additional features over IE, I can also see a need to redirect the add-ons location and search plugins location.
+I had thought about redirecting the entire profile folder to a new location, which is possible using the third-party tools below.  However, I believe since this will put a lock on the profile, firefox would only be allowed to open on one computer.  This is not desirable since I myself (and others) will often have my desktop computer and laptop logged on with Firefox open.
+In my opinion, once these shortcomings are met (preferably via an adm template), in addition to an msi install, then Firefox will make great inroads into the corporate environment.
 == Useful Tools ==
+* [http://varun21.blogspot.com Firefox:Corporate Deployment Guide] - A complete guide on how a Deployable Firefox Build was sucessfully created and deployed. Would let you
+# Deploy options for Firefox (prefs.js, userchrome.css, usercontent.css)
+# Deploy extensions/themes
+# Deploy settings for extensions (prefs.js)
+# Lock down some of the settings (updates to extensions/ app, uninstallation of extensions)
+# Deploy search-plugins (eg. a custom search-plugin for a Knowledgebase in your Org.)
+# Deploy bookmarks
+# Deploy user-interface customisations. (like toolbar settings)
+# A custom namespace icon (Windows only)
+# Customise the help page(s).
+# Name of your Org in the title bar.
 * [http://homepages.ed.ac.uk/mcs/FirefoxADM/Readme.htm FirefoxADM] - Mark Sammons has given to the world a tool to be used in Active Directory environments called FirefoxADM.  It allows Active Directory administrators to control Firefox Options in much the same way as you would IE.  For more information on FirefoxADM, see [http://spaces.msn.com/members/in-cider/ the blog]. For the ZIP file: [http://sourceforge.net/projects/firefoxadm Download Here]
@@ Line 39: / Line 60: @@
 * [http://wetdog.sourceforge.net WetDog] - Another utility that allows network administrators to easily lock down Firefox using Active Directory.  Downloads for this project can be found here: [http://sourceforge.net/projects/wetdog http://sourceforge.net/projects/wetdog]
+* [http://vindimy.dyndns.org/_dist/firefox/ vindimy] (sometimes offline) - Dmitriy V. has created an MSI package based on Frontmotion's MSI file that also includes 7 most popular extensions.
+* [http://www.alain.knaff.lu/howto/MozillaCustomization/index.html alain.knaff.lu] explains helpful features, including how to '''[http://www.alain.knaff.lu/howto/MozillaCustomization/locked.html lock down]''' settings using '''mozilla.cfg'''.
 == Related Links ==