Firefox:2.0 Institutional Deployment: Difference between revisions

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.
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 my 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 ==
== Useful Tools ==
2

edits