Rolling Out Mozilla in an Organization?
jdclucidly asks: "I am a network administrator for a small non-profit (about 50 employees). I would like to roll Mozilla 1.2.1 out to all of our desktops. We don't have a single ghost image because the computers on site are too varied. Yes, I did my Googling. The source for the installer is just huge and mind boggling. Is there something like a Mozilla Administration Kit that will generate custom Mozilla installers? If not, would people on Slashdot be interested in starting a new project to make such a kit?" 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?
I installed Mozilla on my machine using the stub installer and had it save all of the .XPI components to a folder. I went in and extracted the .XPI's and examined them. It seems possible to do these things but not without learning XUL, JavaScript, XML and Mozilla.org's own stuffings -- not to mention setting up a Visual C++/Cygwin compiling farm for every next Mozilla release. Can I:
"Here's what I want to do:
- Install everything but Quality Feedback Agent
- Set Mozilla as the default browser
- Disable 'Open Unrequested Windows' (kill pop-ups)
- Install Elveraldo's Crystal-Classic theme as default
- Set Google as the default search engine
- Set 'Georgia' as the default Serif font for Western and Unicode
- Enable HTTP Pipelining
- Enable FIPS internal cryptography
- Set toolbar to 'Pictures only'
- Set Home Page to my organization's intranet site
- Set start page to 'Blank page'
- Disable 'Hide the tab bar'
- Enable Middle-click for new tab
- Enable control+enter for new tab
- Default downloads to 'open a progress dialog'
- Disable Javascript and Plugins for Mail & News
- Enable quicklaunch
- Create an additional shortcut on the desktop and in quicklaunch that uses chrome/icons/mailnew.ico as it's source and points to 'mozilla.exe -mail'
I installed Mozilla on my machine using the stub installer and had it save all of the .XPI components to a folder. I went in and extracted the .XPI's and examined them. It seems possible to do these things but not without learning XUL, JavaScript, XML and Mozilla.org's own stuffings -- not to mention setting up a Visual C++/Cygwin compiling farm for every next Mozilla release. Can I:
- Directly modify the defaults/prefs/all.js file to incorporate my preference defaults above and then recompress the .XPI?
- Add to the installer Crystal-Classic.jar somehow? Where are those changes made?
- Make the installer NOT allow the user to change any of this?
- Make the installer create the above mentioned shortcut?"
You really want to lock your users from making any changes to the browser? I seriously doubt you will be able to do this (and even if you could, what would be the point?)
just copy the directory, mozilla doesn't need registry entries.. it stores all its settings in some whacky xml files
IMHO of course.
transmission_err
Guy asks for info on how to *autoinstall* Mozilla on 50 machines. Somebody replies saying use Phoenix instead, *without* giving any input on autoinstalling. Is it that obvious how to autoinstall Phoenix?
What's the point of forcing all the employees to set their user preferences to settings that are based soley on your own personal opinions?
I would expect the liability (not necessarily legal liability, but personal liability) would be far to great to standardize on IE. Would you install IE on 50 desktops if you knew your job was riding on IE's security and reliability.
Also, for the poster, I'd just have someone do it. Burn all the installer files for whatever platforms you're supporting to a cd and carry it from station to stations. Or share it on a network and do a network install. You'd be surprised how fast you can do them all after you've got the first ten or so done. Seriously, a good tech could do this in an afternoon, or a day at most. Plus it's good for the soul.
-dameron
Real websites are built to standards, not on browsers that occasionally take liberties with those standards.
Why not? A site that works fine in $BROWSER_X but is a mess in $BROWSER_Y is a pretty sh*tty website. I'm not claiming that a site will render identically between two browsers...compare Mozilla for Win32 and Mozilla for Linux (the latter tends to choose font sizes that are too small). However, identical rendering isn't even the stated goal of HTML. (It's somewhat addressed by CSS, but even there you should expect some variability.) It is not at all unreasonable to expect a website to be functional when accessed with any browser. The path you'd take would only lead to further balkanization of the Web.
20 January 2017: the End of an Error.
Knee, meet Jerk. Jerk, meet Knee. Apparently neither Vallon nor his 3 or 4 moderators bothered to read the freaking question. The IT guy specifically wants to use the mail client as well as the browser, and probably NNTP too.
Just because Phoenix is small and 1337 doesn't mean it's the answer to world peace, minty fresh breath, or every question that contains the word "Mozilla".
No other reasons are given.
The FACT that applying the constant flow of security patches for IE is way harder and time consuming than using Mozilla doesn't seem important for you. IE is from Microsoft, go with IE. That's all what seems to matter to you.
Also IE being integrated in Windows is kinda problematic. IE updates may affect the rest of the system - Mozilla is independent from Windows, therefore much better to control and maintain. On top of that, you can EASILY have as many different Mozilla installations on your PC. (which can be useful on upgrading - if you don't want to take any risks just add the new version instead of replacing the old version). Also you can also downgrade Mozilla, but last time I checked, the only way to downgrade IE is to reinstall Windows... Mozilla is easier to integrate and support than IE and upgrading is much safer.
And most importantly, Mozilla does not chain you to a vendor. Microsoft may raise license prices anytime - again. It happened before, it can happen again.
As an employee, it's not "your computer". It's the property of the company. I wish more end users would remember that. "Why are you messing with *my* computer? I've got it just the way I like it!" Sorry. Pink fonts in Monotype Corsiva on a light blue background makes it tough for me to troubleshoot. Don't put your kid's picture up as wallpaper (less of a gripe, I don't really care, but give an inch...). Don't install the "little program" you brought from home.
Those machines are also not there for the IT staff to use for some kind of power trip. Those machines are there to provide value to the company, which they presumably do when the users are working on them, not you. If the customizations they do make them work more effectively (translation: more motivated), that is good for the company. Certainly if they install viruses and stuff that creates trouble you need to take action, but the whining about text and background images is pathetic.
Somehow I thought that kind of tayloristic management (your desktop will show in 0.04 seconds faster if you don't have a background image) became almost extinct long ago. If you treat people like machines, they also react very cynical - and do as little work as possible without getting fired. Since there's an economic downturn I guess people will stick around - but if all your best men leave when it starts going up, I can't say I'm surprised. I wouldn't want to stick around at least...
Kjella
Live today, because you never know what tomorrow brings
-
Stability for a production environment, which Moz 1.2.1 has. Phoenix is still alpha, and not very actively developed at the moment. Seems the developers have other things on their minds (safaris, schools
...) -
He has a mixed environment. He may have architectures which Phoenix does not support (it is MS Windows and Linux/Intel only.)
-
All components, in particular Mail & News. Phoenix is browser only.
Mozilla 1.2.1 seems a good choice to me, maybe 1.3a or a carefully chosen nightly could be considered.If all your users use Windows then why do you need to switch them? I am using mozilla to type this and its a great browser but alot of websites send my "connection refused" errors because I do not use IE. It takes alot of man hours and hassle to upgrade all the users not to mention can cause complaints if your users recieve the same error messages that I do on a few sites.
I know Microsoft is a bully and want to prevent users from switching since IE is free and comes standard with every computer, but there really is inertia that locks people in.
You have to ask yourself time is it really worth it to switch them? And also what benefits will it bring to your organization.
http://saveie6.com/
Fuck you.
Not all of us have systems with 512 MB of RAM and >= 1 GHz processor... and for those of us that are in that particular boat, Phoenix is a godsend. Mozilla is just too damned SLOW to run on a P3/450 with 128 MB of RAM. Phoenix is NOT.
The question has interesting aspects where it relates to software management on the desktop. But it falls terribly short on reason. Why would you replace the user's prefered browser with your idea of what is right? Some may already have Moz on the desk, but I bet most will hate you for replacing IE. Have you nothing better to do than push out a browser (and IMHO a bad one) to the desktop? Surely there are more pressing issues for your IT shop to address.
www.jmagar.com
-
This is pretty typical: in order to get even the simplest task done on Windows, the usual answer is: get another software package.
the money you spend will save you $$$ in man-hours trying
First, you are going to spend many man hours getting your manager to approve the purchase and order the applications. Then you are going to spend many more man hours installing them. Then you are going to spend many man hours trying to figure them out. Then you are going to spend even more man hours fiddling around with them trying to package up Mozilla. Then, you still need to figure out how to get the packages themselves or the client packages for those packages onto the clients. Then, if everything goes really well, you may be ready to install the software.
And when some major software upgrade comes from Microsoft or these vendors, you can start pretty much from square one.
That's of course assuming that those packages are completely bug free. More than likely, they will interact in some unknown way with some other software package and mess up something or other.
hackneyed, crappy homebrew solution in the long run
Professional chefs use a couple of knives to get the job done: they are reliable, predictable, simple, and efficient. Amateurs run out and buy every kitchen appliance under the sun, hoping to compensate with appliances for skills that they lack. It's no different with system management: if you don't know what you are doing, your answer is going to be: "oh, just buy another piece of software".
Windows, unfortunately, doesn't ship with any knives, but with Cygwin and Perl, you can get by. System management on Windows still like preparing a banquet in a kitchenette, but you don't need to make the effort even harder by stuffing the kitchenette full with useless junk.
An admin will develop a sort of possessiveness with their network. You may feel that you as a user spend more time with the computer than an admin, or in most cases recently, "the admin". Most users have no idea and can't comprehend the time that we actually spend working on the computers and networks.
... and many other IT people you DON'T see) don't usually get thanks. Users tend to grumble that though they need help, the admin is causing them an inconvenience by showing up to help!
Even if we aren't working over night rolling out a new hosting server. If we are not cabling the building over the weekend. We still vigilantly carry a pager or some other device that gets computer and network monitoring alerts.
You'd be shocked to know what some of the most inept computer doods know and can do.
And one other thing, they (Systems Administrators, Database Administrators, Datacenter Techs, NOC Monitors
Not our computers!? Well no, we don't own the company. Or do we!? We control every little tid-bit of data, if we don't than we are not doing our jobs. Its not just a job its a passion, and we do it well or we wouldn't still be helping our clients the users.
Companies like our bodies don't function correctly if something is missing. In this analogy the sales department are the hands extending out. Marketing would be the mouth showing our perly whites. R&D obviously the brain.
But where should we put IT, (using IT as an all encompassing term) I would have to say that IT makes up the nervous system (and spread the term back out as you see fit). I guess it's natural to have a few free radicals running around messing with your settings on your corporate workstation. And we haven't even mentioned the user/security issues.
Perhaps you'd like to take a field day (cross matrix training thingie) and be a SysAdmins sounding board. He can ask you questions and you can give him the answers to all his problems!?
My rant for the evening.
Have you thanked your Systems Administrator lately!?
:-( --- argh. Despair, I owe again.