Dave Ewart wrote:
> Haven't found any reference to it anywhere, but is anyone working on
> documentation regarding setting up Mozilla / Mozilla Firebird in a
> networked setting?
>
> I plan to do something like this soon, and will document the process if
> it would be considered useful.
>
> Main objectives of the 'corporate rollout' are:
>
> - Mozilla will be the default web browser on all desktops;
>
> - 'Roving Mozilla profiles' - i.e. profiles are stored in, e.g.
> NETWORKDRIVE:\mozilla and so Common Browsing Experience (TM) is
> available regardless of workstation that is used;
>
> - Mozilla binaries should be on network drive where they can be easily
> updated with new releases/patches/plugins;
>
> - Each user should start with a default profile which has reasonably
> sane defaults, not necessarily the same as the Mozilla defaults (i.e.
> our 'local' defaults - e.g. proxy server preconfigured for all users)
plan to Mozilla Deployment Guide
Objective
help network administrators on planning to deploy Mozilla or a
mozilla.org product in their network
1. Introduction
Give an introduction to Mozilla, the Mozilla Foundation, and the Mozilla
community (particularly supports available and other distributor
alternatives). The objective should give network administrator
confidence on Mozilla, e.g. that Mozilla is not going away anytime soon,
that there are support channels corporate customers.
2 Benifits
Explain the benefits of using Mozilla, emphasising the advantages of
Mozilla over other Internet clients. For example, "Mozilla is a
cross-platform application suite ideal for deployment in a heterogeneous
environment. Mozilla is open source and open standards. Furthermore
unlike other popular Internet clients such as Safari, Opera, and MSIE,
Mozilla has proven itself as a stable, flexible development platform.
Thus, whether you are just standardizing your users on Mozilla or
developing an Intranet, you will not have to worry about vendor lock-in..."
3 Planning for Deployment
Help administrators on creating a deployment plan.
3.1 Environoment Accessement
Start drawing a plan based on what your environment is and how you are
going to distribute Mozilla. Important information are: hardware and
operating system, user log-in and roaming access, and software already
being used (for migrating user data).
3.2 Choosing a Version
Help administrators deciding on a Mozilla version. Currently the
application suite has two stable branches: 1.0.x and 1.4.x. There are
also Netscape 7.0 and 7.1, Mozilla Firebird, Camino, and other
distributions such as Beonex.
Generally, adminstrators should use only *one* version because each
variation may be incompatible with one another.
Some considerations:
If roaming access will be enabled and Mozilla will be used, then all
local computers must standardize on either Mozilla 1.0.x or Mozilla
1.4.x. This is due to 1. problem w/ xul.mfl, which is fixed on 1.4 but
not on 1.0 and 2. localstore.rdf, which stores UI information (feel free
to correct me if they are non-issues)
Netscape and Mozilla should not be installed together.
Mozilla FIrebird use a different profile directory. So future version of
Mozilla Browser standalone may not be able to import data.
Mozilla 1.4 does not support Mac OS 9.
You can customize your own distributions. You can customize the
installer to automate the instllation process. You can also compile your
own distributions. If you do not know how, consider using the service of
the good folks at Beonex.
3.3 Standard Profile
Decide on the standard settings for new profiles, whether you want to
lock them or not, and whether you want to control them remotely.
Things you can customize are: bookmarks, junk filter, popup whitelist,
image blacklist, cookie black/whitelists, and Local Folder mail account,
most non-file-related preferences, such as the home page and mail home
page. Other things administrators might be interested in are hiding
certain panels in the form manager and password manager. Things you
cannot customize are: mail accounts (unless you can leave Local
Directory preference empty and let Mozilla guess the right location.
haven't tested this yet).
You can lock preferences using the config file, or control the
preferences remotely using autoconfig (ideal for updating proxy and mail
server info).
Notes:
* UI settings is stored in localstore.rdf and cannot be simply overriden
by preferences.
3.4 Migrating User Data
refer to my get-started guide :-)
3.5 Training
duh, we need a real tutorial (bug 74338, assigned to me :-) ), a 1.4
start page, and better Help files.
4. Installation
Provide information on Mozilla installation.
4.1 Customizing the Installer
5. Profiles
5.1 Profile loading
User files are overwritten when the settings are changed--meaning you
cannot have two users accessing the same profile at the same time. On
Linux system, a lock file prevents such scenario (and problems when a
crash occurs).
Describe preference loading sequence.
5.2 Changing the default profile
5.3 Config and Autoconfig
A config file is stored on local computer and allows for preference
locking. It's simply encoded to prevent user from modifying it. The
config file can be set up in all.js
An autoconfig file is stored remotely and can be used to update user
settings. Autoconfig can be set up to be reloaded at a specified
interval. The file is cached in case there is network problem. An
autoconfig file must be set up in the config file.
6 Roaming Access
Simply use the system's roaming access feature. On Windows enable
roaming for the User Profile (not to be confused with Mozilla user
profile). On MacOS X, put the user's home directory on the network.
7 Compatibility issues
