Rolling Out Mozilla Across an Organization

Monday January 20th, 2003

alanjstr writes: "Slashdot discussed how to roll out Mozilla across an organization: 'If you were going to deploy a "branded" version of Mozilla, company-wide, how would you do it, especially if you had to worry about a mixed OS environment?'"

#9 Re: I submitted the question to Slashdot...

by astrosmash

Monday January 20th, 2003 5:23 PM

You are replying to this message

One thing you can do is create a default user profile, with the settings of you choice, in a location you assume may exist on all machines you wish to install to (say C:\program files\mozilla\userdata), then zip up profile directory (along with registry.dat). For installation you need only unzip this profile to the known location along with a vanilla distribution, and copy your custom registry.dat to %USERPROFILE%\Application Data\Mozilla.

I'm forced to do some of my work on public terminals, now that I've gone back to school, so I do this type of mozilla installation on a daily basis. It works well.

The benefits: it actually works, it's (relatively) easy to set up, and you can upgrade to newer versions of without affecting the rest of your install process.

The drawbacks: it relies on a hard coded paths in registry.dat and prefs.js, and it only works for one user per machine -- if a new user logs on to the machine the Mozilla profile created for them will be's profile, not yours.