Firefox:2.0 Institutional Deployment: Difference between revisions
| Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
This document describes the feature requirements for corporate/enterprise deployment which includes large businesses (>10,000 users), small business, colleges and universities, etc. | This document describes the feature requirements for corporate/enterprise deployment which includes large businesses (>10,000 users), small business, colleges and universities, etc. | ||
The next section assumes you're running in a windows environment: | |||
Deploying the software is easy:<br> | Deploying the software is easy:<br> | ||
[http://www.frontmotion.com/Firefox/ | either through re-imaging, or<br> | ||
[http://www.frontmotion.com/Firefox/ push this .msi file]<br> | |||
via Active Directory GPO<br> | |||
or scripts, landesk etc... | |||
Things that you will run into are: | Things that you will run into are: | ||
* deployment of | * deployment of options for Firefox | ||
* deployment of extensions/themes | * deployment of extensions/themes | ||
* deployment of settings for extensions | * deployment of settings for extensions | ||
* locking down all/some of the settings. | * locking down all/some of the settings | ||
Different configurations of your network can be: | |||
* no roaming profiles | |||
Firefox's default behavior is sticking the extensions/preferences into the local users profile with a unique identifier. What is needed is a way to control/lock down the options at the server (via AD). | |||
== Requirements == | == Requirements == | ||
Revision as of 19:38, 4 April 2005
Introduction
This document describes the feature requirements for corporate/enterprise deployment which includes large businesses (>10,000 users), small business, colleges and universities, etc.
The next section assumes you're running in a windows environment:
Deploying the software is easy:
either through re-imaging, or
push this .msi file
via Active Directory GPO
or scripts, landesk etc...
Things that you will run into are:
- deployment of options for Firefox
- deployment of extensions/themes
- deployment of settings for extensions
- locking down all/some of the settings
Different configurations of your network can be:
- no roaming profiles
Firefox's default behavior is sticking the extensions/preferences into the local users profile with a unique identifier. What is needed is a way to control/lock down the options at the server (via AD).
Requirements
Suggestions
- Target audience is IT
- This tool requires an Active Directory environment
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 the blog
for the zip file :
Download link
Functional Capability & Usability
| Focus Area & Work Items | Release | Priority |
|---|---|---|
| Places (An Updated Approach to Bookmarks & History) | ||
Firefox:Places:Scratch Pad |
2.0 | P2 |
| Tabbed Browsing | ||