Deployment:Deploying Firefox New

From MozillaWiki
Jump to: navigation, search

< Deployment

= temporary Preface/Background info - Work in Progress - all Help needed and

most parts if restarted documentation have currently moved to:

see also:

as well as:

"xxxx 2008-02-28 04:04:28 PDT

Created an attachment (id=306248) [details] WiX-based XULRunner msi/msm

With this patch, 'make installer' produces xulrunner.msm and a cfg file for it, which can be included in wix configuration for applications.

WIX_FLAGS and MSI_EXTRA makefile variables allow to add dependencies to application's main wix file. After building msm for xulrunner-1.9b3 with this patch, I was able to create msi packages for my application with one command per package: make -f installer make -f installer AB_CD=ru

Application configuration is available here:;f=installer/windows; "


open tasks

  • fix text errors: language and format
  • shrink sections/ sentences
  • research and review resources on the web, especially on:
    • official mozilla position
    • position of other companies, even if unstated but apparent from current/future products and plans.
    • articles in online media, blogs, magazines etc.

  • using the requirements list and scratched design of the toolkit:
    • research, review addons that provide required functions and add them to requirements list as well as the toolkit structure

tia, dwe

Deploying Firefox

Why is a 'new' article needed?

Though there are numerous sites about the deployment of firefox in a company, they mostly just scratch on the surface, are outdated/not verified to work with the actual version, pointing to extensions and tools mostly created for older firefox versions which were not developed further and are obsolete today.

There are Groups like the FireFox Enterprise Working Group, but i`m unable to find a site and project that focuses on the basics and provides reliable, verified information.

If someone has links etc. of actual project, please drop me a mail and/or add them here, preferable with a short description.

The group mentioned above has some interesting information, but the scope of the case studies are installations with thousends of pc`s and partly very highlevel requirements.

Corporate demands often result from the requirement to implement certain management systems or to comply with standards - even in the it department.

The increasing usage of it-management process-modells, with ITIL beeing one of the most widespread, forces more and more the companies to implement them, requiring software, configuration and processes to comply.

Currently just one single individual installations using the internet for updates and as source for the installation of updates simply bypasses and violates eg. the ITIL change-management process as well as security.

Microsoft internet explorer can be updated using a company operated wsus or softwaremanagement server, how can this be done with firefox and extensions?

With the browser evolving to the most important platform directly following the os, microsoft beeing in a strong position with the bundle of os and browser as well as providing all the tools and concepts to maintain ie installations in corporate networks, mozilla firefox is required to catch up - and do it fast.

large group of possible users left out due to missing tools

Ignoring the demands of users with influence and possible results

The browser is one of the most widespread, daily used, important/critical tool used at work as well as private in similar ways for similar or different tasks. It is expected 'to be aviable' and 'to just work' by the end-user.

But what about the people tasked with installation, management and support?

== loosing possible customers by the lot

The lack of tools and concepts to manage a distributed firefox installation, as well as a missing official position, makes it nearly impossible for an it-person to propose or support a decision to switch to firefox.

One might think: Ok ,who cares? That`s just a few people...

"dad, why don`t you use firefox? Everyone uses firefox!" 

"Well, son, it`s certainly a good browser, our company even thought about switching to it. Our it department then had a closer look and in their opinion it`s lacking professionality, so we stayed with IE. And since i don`t want to switch between different software for the same purpose but different functions, i`m going to stay with IE as well".

Next thing happening might be a windows homeserver, nicely integrating ie and a father telling his son:

"Look, our it-guys were right!" 


"Sorry, i can`t helop you with your firefox problem. 
I never had that one with ie. Why don`t you switch?"

Knowing or unknowingly the user influences the view the family and friends have on firefox - and this father won`t advocate firefox.

That`s it, case closed for a couple of users on family level.

Now, just assuming that the hypothetical father mentioned above belongs to a group of 50 users, and also assuming that just 10% of these actually influence a negative decision on firefox of two people in the family as well as one additional, this would mean 20 users lost to firefox.

possible effects on end-users by a corporate contra-firefox decision

A decision made by the corporation pro/contra a product can easely - form the personal impression and opinion

- stick

- last for a long time

- be an 'authorative', 'lead-example' for private decisions on similar matters

And will allways have influence on private decisions of employees on the same matter.

A normal user will rarely install a product at home his company has evaluated and found 'flawed' or 'risky' and 'unprofessional', even if the factors leading to these finds will never arise or be important in personal use, the corporate position will be normally unquestioned accepted.

No one will blame an user who decides to stick with IE following the advise of the corporate it (the same guys who eg. rescued his data in the past) which takes the position that firefox is a 'toy browser noone in a sane state of mind would ever set free on a company network'.

From the users view, the decision pro/contra firefox is normally made and supported by people with known and accepted authority. The fact that the results affect a personally, daily used and important application, that the user is personally 'involved' or at least 'affected' adds to the importance of the result.

buzzwords and phrases are sticky... 'professional use'

A decision might in broad explaine all the reasons, background etc, but the essential information transported is this:

'2008,june,evaluation, use of firefox in company network,NOGO, reasons: unprofessional,risky, flawed'

= excerpt: phrases to exchange of information and knowledge between parties with incompatible knwoledge systems =

Sometimes a fact can not be explained using synonyms but nevertheless has to be explained or stated in understandable way.

One reason can be that the information is the result of a process specifically for and defined in knowledge-system that is unique for a certain area. The knowledge required to assign a meaning to an information and it`s relations to other information already known on that area are defined in that knowledge system itself,

(certain area: any 'area' of interest that might have information: eg, sky as part of world, day etc. An area can consist of one or several fields of interest . A field of interest is one of more information interconnected with other information.

Information is interconnected between each other, the interconnection defined and agreed on by one or more parties.

The agreement is a denominator acting as Tag to mark interconnections and their connectionpoints.

The sum of all informations interconnected by a tag defines the primary area of information for this tag.

This sum is the first channel of information for that tag, and none, one or more other channels from other tags which can be combined in every possible way (eg.:supportive, adverse) and type (eg. qualities like: good, bad etc.)

and with the combination becoming a relevant 'focus' of the attention of one or more interested parties. :=)

Which in short contains all relevant information and uses phrases and/or buzzwords to translate information and it`s meanings into a term easely understandable by others.

The process converts an often complex information or knowledge (= minimal: information + context of subject, objects + meaning. ) from their own, field-specific 'information system' into a common term or phrase.

Each term has at least one common (plain-language) meaning, definition and examples to describe them, which can add additional information (eg, time, as well as qualities to them term.)

Common terms are the result of language and culture development, they normally change slowly, have many examples of which some are popular which describe the most common accepted definition and meaning.

The examples also transport additional information and qualities (eg. examples describing the 'borders' between terms and are commonly aggreed on: eg. when to use 'risk', 'danger' amd 'mortal danger': 'there might be a bear in that cave', 'seen that? there is a bear in the cave' and 'oh shit, there`s a bear running to us')and others..

The terms definitions, examples to describe it, and processes whose results.

but the inoffical

'fit for professional use' made by known people with accepted authority has a huge impact.

The opinion that 'not fit for corporate use' equals 'lack of profession' which results in 'use a SERIOUS tool, not a TOY' is widely spread.

Even in the 'home-office', the typical user want`s to work 'professional' using 'proffessinal' tools. (This is easely proven by the thousends copies of proffesional/enterprise software products like operating systems,office and other products eg. photoshop (enterprise/CS3 preferred, even if the other products will never be used). A re-evaluation will rarely happen: neither on private nor on corporate level.

- Corporate use = professional use

- Who want`s to use a toy browser at home?

- Be unable to ask colleguas or corporate it-staff on private it-problems?

- Have colleguas and/or friends making fun of one?

- Have to explain or even defend the private use of a product officially found unfit for corporate usage?

And this might happen (and acutally IS) right now, just because a simple thing like eg. a package - builder is missing and the corporate has not the time and capabilities to research and evaluate the existing extensions.


The largest group are: One of the in my opinion most important group of users appears to be left out: the sometimes self-learned, part- or even free-time working operators managing networks with roughly 5-20 systems up to administrators of networks with 50-500 systems or more.

These guys won`t do a custom build of firefox to meet the companies requirements ever. Typically they are also very reluctant of fiddling with a bunch of different tools.

Quite often these operators and admins already have had a hard time to explain to dubious superiors that 'It`s Opensource - we don`t pay licence fees - it`s free' as well as 'No we can`t buy a support contract from mozilla, but we won`t need one', often promised 'it`ll work like the other browser' and finally gotten a cautious approval with typically either none or a very small time budget, also beeing often expected to do unpaid overtime once the approved time budget is excessed.

Knowing they`ll be the one pointed at if something later breaks or just appears to be broken, they prefer to play it safe: minimal configuration and settings, none or just a few small extensions (eg. duplicate tab but avoiding Mozbackup), unwilling to search the web for non-standard tools and to read several tutorials on 'how to repackage firefox', they just want and need 'tools that work'.

With firefox lacking these 'official', easy to use tools to customize, reconfigure, repack and deploy via standard distribution methods as well as no means to remotely maintain already deployed configurations, extensions and their settings, these operators and admins have to choices:

  • leave it
  • go for it, despite the lacking tools

The later are those still eager to do almost everything to avoid the 'other' browser, and instead of giving up and cancelling the project (perhaps with a smirking superior commenting the apparent defizits of opensource software), they try to meet the company requirements, but are often forced by small or non-existing time-budgets to deploy firefox in a way that not only leads to diverging software revisions, patchlevels, installed extensions, settings and configuration settings, bus also sooner or later resuls in unmaintable setups which finally become security risks.

This group is especially in need of tools, reference / example solutions etc.

different positions: mozilla, users - comments


Excerpt posted on slashdot:

ricatcw brings us an article describing some of the obstacles Firefox is facing while competing with Internet Explorer for business use. Quoting Computerworld: "Now nearly three-and-a-half years old and nearing the release of Version 3, Firefox no longer can be accused of being callow. And while many IE-only apps remain, plenty of others have been overhauled to support Firefox as well. However, other obstacles to broader adoption have emerged. Mozilla thus far has neglected to develop tools to help IT departments deploy and manage Firefox, and it doesn't offer paid technical support services to risk-averse corporate users. Janco Associates Inc. in Park City, Utah, currently gives Firefox a 16% usage share among visitors to 17 business-to-business Web sites that it monitors. Janco puts IE's share at 67% while giving 9% to Netscape and 3% to Google Desktop

Mozilla position:

Kuo added that he doesn't think Mozilla will suddenly change its attitude and develop a browser deployment tool that could render FrontMotion obsolete. Mozilla "could create it themselves," he said. "But it's obviously not their priority."

User reponses /comments

That's great information; but at the same time it's actually a really good  example of lack of support contributing to so many corporations /not/ willing to use FF.

After all, it's not really practical for organizations that rely on NTLM for  multiple servers to manually configure several hundred or thousand firefox  installations to accept those specific servers -- never mind if the list of  servers changes. Too, it's even more unlikely that they'll be able to trust the  users to properly maintain and configure those settings themselves.

You've minimized the amount of testing you need to do for alternate browsers.  Just make the applications work with IE and you've satisfied almost all of your  users needs. Fewer browsers is actually a good thing for web developers--especially if they are targeting a limited niche of working in the real world of constrained budgets. The more browsers/configurations you need to develop and test for the more it will cost (or the less features you can include).

From the article :

    The big downside is the difficulty of managing Firefox, especially in comparison to administering IE, according to the CIO. For example, he said that the IT department can patch IE via automated central updates. On the other hand, "we have to send an e-mail and have users manually download Firefox updates, which is not ideal," he said.

Granted using an internal repository might be more rational in a large organisation (although that's presumably hackable) but from what I've seen Firefox just updates itself (In Windows and Mac OS at least IIRC).

IME medium and upwards sized firms are used to a certain way of working and if anything doesn't fit the model, it has zero chance of being used.

1. Is it secure? TICK 2. Does it work in our environment? TICK 3. Do they have guaranteed response times on support calls? CROSS OK, forget that one. Next?

Mozilla thus far has neglected to develop tools to help IT departments deploy and manage Firefox,

That, right there, is probably the number one reason more folks in the corporate world don't deploy FF. As far as I know, there is no easy way to push FF out to a desktop regardless if it's Windows, Mac or Linux. 
I currently deploy Firefox to our corporate workstations, however there are definitely things that Mozilla could do to make Firefox more corporate friendly.

2. Management through group policy, or some other way to lock it down. IE does this very well, Mozilla's default install really doesn't offer anything, Frontmotion's build has some options, but it's not as good.

3. Better support for restricted users and roaming profiles. We turn auto updates off, but our users still manage to try to run it occasionally. If they do Firefox downloads the update, fails to install due to lack of permissions, and then gives them an error until someone goes into the user's profile and deletes it. There can be some wackiness for people moving around between workstations as well.

Yet, the corporate adoption problem still remains. I am now a division manager over IT development and deployment for a 1,200-person department in a large County organization. Our official policy is "IE-Only." Do I run Firefox? Yes. Do I have staff which runs firefox? Yes. Are they officially allowed to run Firefox from the CIO? No. The problem is - Firefox doesn't come bundled with Windows XP/Vista and therefore isn't even on the minds of most non-IT folks in my organization. As it is, recent applications I've overseen are more Firefox-compliant, but still run "better" with IE or at least the IE-tab.

Corporate users (well me, anyway) want a tool to make it easy to deploy and I haven't found anything all-inclusive. Sad to say that a lot of hosted business apps run as active X controls or other BS that needs IE. What I need is a way to deploy firefox with specific settings, deploy ie tab with it, then have a list of sites that are always used for ietab. I need to configure this through group policy at least. I could have firefox on 500 machines tomorrow if I had this and I knew it worked perfectly. It should also be easy to deploy upgrades.

I have been tinkering with this myself but.. busybusy and I haven't made much progress.

However, in a posting on his personal blog last September, Kaply lamented that the number of participants on Firefox Enterprise Working Group conference calls had "dwindled." And in an earlier posting, he said that he thought most of the large companies that had adopted Firefox were using it "as a secondary browser" only.

Deploying Firefox - from original article

Many people are using Firefox at home, and many also want to use it at work or see it on public computers such as at libraries or Internet Cafes. This article provides links and references to issues that might come up when considering or executing a Firefox deployment plan. It describes a wide variety of tools and features available that can be to deploy Firefox and centrally manage and control the use of Firefox in enterprise, business, education, and a variety of large and small organizational settings.

The Rational for Deploying Firefox inside Organizations and Institutions - from original article

  • It is interesting to note that Firefox market share in corporate environments appears to be pretty closely tracking with the increased use of Firefox in the general internet population. Firefox use inside many organization often starts with IT, web development teams, and engineering departments and then spreads to other departments and individual users.
  • Concerns about security is a strategic reason some organizations move to Firefox exclusively, or set up support support for multiple browsers.
  • Many users choose Firefox when it is offered inside their organization, or go around IT policies because it makes these users more efficient and more productive in accessing information on the web. They take advantage of firefox features such as tab browsing, rss feeds, and integrated search to get more done, faster. With the amount of time that "knowledge workers" spend using a browser each day these productivity increases can add up to be significant to the bottom line and the competitiveness of a company.
  • Some organization also chose Firefox as a tool to assist in ensuring development of internal applications and documents comply with web standards, and that the organizations do not get locked into proprietarty document formats that could become difficult or costly to support. If your applications and content works in Firefox its highly likely they will work in other browsers, and open up possibilities that ensure your internal organizational content is searchable and useful with other applications that support standards.
  • International organizations, and organizations that support multiple Operating Systems also like Firefox because its a way to standardize the browser for all their users. If you have an organization where engineering teams might use Linux or Unix Systems, Design and Web Development Teams using Mac, and Business Teams using Windows Firefox is the one browser that can be used across the company, and its available in over 40 languages.
  • Firefox can also be customized and extended to meet specific needs of an organization by creating addon extensions or building on the Firefox platform.

Company vs. Enterprise - shared, different and opposite requirements

major differences and their influence on decision

Though the usage of firefox in corporations is generally labeled as 'enterprise usage', the group of corporate users is split into at least to parties with opposite positions and different requirements and priorities but sharing some basic requirements

Enterprise: 'Enterprise' is almost allways connected with large corporations having more than a couple of thousend employes, remote locations and usually a sophisticated it-infrastrukture neccessary to provide reliable it services to thousands of users.

Enterprise it-departments typically have the capability to develop applications, tools, interfaces and other kinds of software neccessary to integrate applications into the company infrastructure as well as ensure that requirements are met.

Company: Even a a small shop with eg. 10 employes and 5 pc is a company, needing the same access to common it services and products like an enterprise though on a much smaller scale. Depending on the type of business, they also might have to comply with laws, current jurisdiction as well as be required to implement standard business-processes at least for some processes (eg. the requirement to implement risk-management system etc.).

Companies of these sizes typically have very small to medium sized it-departments, sometimes backuped up by external consultants, with the admin often performing additional duties or working on a half-time base.

ultimate factors which influence "GO/NOGO - decision"

In the end,it all boils down to one simple, ultimate decision factor:

"the amount of human resources aviable in terms of time and capabilities aviable "

- for the project itself

- for lifecycle management and user support of the productive solution

- to gain knowledge on operational issues to manage normal, daily tasks

        - to build up backgropund knowledge with a broader scope to manage administrative tasks, develop new addons etc.

= "amount of time aviable" and "capabilities aviable

(slow - time: suddenly or known time slots aviable for background tasks like reasearch, documentation etc. as soon The amount of time aviable in combination with the amount of 'slow time' aviable for knowledge-building, usually defines areas and fields, depth and broadth, type, etc. of internal knowledge - and finally defines or at influences the amount, kind, quality , generell orientation etc. of in-house aviable it - capabilities.

(for an even more honest calculation, skipp every second or third hour of aviable slow - time per week...)

The simple question of amount and quality of aviable time and knowledge results in opposite positions and capabilities:

enterprises: - are able to throw much manpower and have aviable knowledge onto a problem

- have a longer project runtime

- use process-modells

- often have an actively followed corporate policy/mentality to buy required resources not aviable in-house (eg: second opinion) in a short time and often from longtime partners, seldom on the pen market market

- use tools for software distribution and management -- customizion, repackaging are already common tasks

- are used to central configuration of distributed applications -- not expecting to have one single tool suitable to manage all distributed aplications, administrative 'means to manage' are expected. Either as administrative interfaces to common management solutions or by administration and management tools provided by the application itself the vendor is expected.

companies - the same problem can be the one unsolvable blocking problem orleading to cancellation the (pre)evaluation for smaller companies because of missing knowledge and/or, pressing time

- especially for smaller companies (->100 Pc) the amount of time and/or knowledge required for daily operational taks might deemed too high, resulting in a negative decision and/or reviews and cancellation of existing solutions.

- central management solutions are rare, if they exists, then mostly isolated for just some applications. -- a seamless integration/support of existing solution is not expected.

- rely on tools the application provides itself for tasks like deployment, management etc. as well as those resulting from its use. -- If problems/needs arise from using the application, the application is expected and even required to provide a solution since others don`t exist. (fiddling with adm - integration can be a NOGO, ticking a checkbox and providing common details to enable it on all installations is not.)

list of requirements

general aggreement

on: - interface definition for functions every module and ff-extension in a corporate network should support to allow: - unified acls defining access to addon function groups or single items (eg. user may run some addon - function, and can see but is not allowed to make changes, eg. a the lue of a backup-path. possible approach: labeling of functions or gui elements/functions with security permissions and/or unique identifier (something like a sec-guid) as pointer to permission definitions stored in a sqlite database (what is official mozdev approach?

- support global security and configuration policys

common mandatory requirements

  • operational tasks completely aviable via interface/console
  • predictable amount of time required for operational tasks for calculation of the time required in productive use
  • customziation and redeployment of customized package
  • silent installation, upgrade and removal of the package using common software management tools.

(the 'big picture'...)

  • preconfiguration of settings at install time, such as update- and addon-source, security settings and configaritions like custom CA`S and certificates, default profile, etc.
  • protection of basic application settings against changes on at least two levels: global se, affecting all firefox users on a machine and per-profile settings.
  • controlled deployment of updates, using a company-owned update source,

( Change-management anyone?... we`d whack the whole process if we allowed the installation of updates from a website, not knowing/caring wether it was successfull or not, without tests and verification in the company software environment and without an informed decision to deploy the update at a certain time or to delay it...)

  • reporting success and failure of all post-installation changes that are not controlled by common software management systems made to the package itself, addons as well as configuration settings, to a central collection point, acting as source to feed other management or monitoring systems.

(It does not help to know just the release number - we need to know wether eg. custom certificates were properly installed, a certain addon is installed, the configuration is protected etc. of each installation)

common optional requirements

Either extending existing requirements or new ones:

  • granular protection of settings 'per - item'
  • whiteliste of sites allowed to install updates and addons
  • requiring a custom certificate for updates and installation of addons

+ split -configuration: global, and user

  • concept for loading /storing configuration via https, webdavs etc. a
  • concept how settings& configurations of addons can be maintained the same way as the firefox configs.
  • generic, operatingsystem independent, interface to enforce configurations via policys. connectors to the different systems like MS ads-based grouppolicys as well as linux, mac-os specific ones - not everyone has an ads running, policyfiles loaded from a share would make life a lot easier.
  • best-practice, cookbook, real-world examples

typical enterprise requirements

common roles: operator, administrator, developer

Enterprise requirements for applications typically are:

- deployment and update/upgrade management possible with the existing software management systems

- configuration settings controllable on a per-item level

- configuration at deep level, settings hidden or not accessable by default firefox configuration interfaces

- support and maintenance contract covering the application lifecycle

- security and access conrolled via interface with MS group - policies

typical small to medium sized demands

common roles: operator, administrator

A small to medium sized company might have the following requirements:

- easy customization (eg freeze of existing installation and use as base as well as profiles, creation of custom package, easy deployment

- centralized management interface for: firefox + addons lifecycle and to all items additionally required .

- secure access amd usage, integrated into firefox, error checking/input validation, logical strucure of functions and application behaviour,

- wizards for common tasks

Which all are related to the management of firefox itself, do not exist, are in high demand and therefore a reasonable developer task :)

the list of questions

Apparent and usefull points to think about and questions to answer on 'how to make employees use and get used to it as common tool which is daily and actively used. are.

Functions and features probable or already known to be needed and/or demanded currently or in the near future:

feature and functions - questions to define the general corporate requirements

- what functions/features expects a corporate user as: 
-- usefull for daily work or tasks
-- easely aviable
-- in common use 

- what are the expectations on aviability, interface ergonomy, even look, design and style. 

- what are functions which could be grouped/combined/replaced and how are they currently provided

-what are functions officilly known as missing, wished, in need for improvement, logical when eplained etc. 
- needed: how are the existing features connected to business processes as well as other applications

- how would these functions/features be expected/or aggreed on to be provided on application level? 

- what features may be required in the near time resulting from general development or projects?

initial research and evaluation of possible solutions and suppliers - checklist

- what are current, competing and future solution concepts and are there alternatives?

- when searched: how are the results rated, how many referenced by other sources, etc.

Qustions on aviable solutions - are there commercial products already providing all or parts of the functions, if so, how ?

Opensource - are there opensource products and projects providing all or parts of the functions, if so, how?

Opensource Projects: - are there dying or dead produkts or projects, with the last change of site more than 1 and 2 years ago, - if so: what were the reasons? - What where the major points of trouble, what the smaller ones? - Do current solutions for the problems of earlier projects exist, have concepts, approaches changed?

License /patents/lockouts - Are there concecpts covering or related to the functions/features etc. currently locked by patents or other ipo, - Are there patents already filed and pending, - Are the patents for sale, been recently traded, been recently discussed on the internet and/or in common media? - if patents/ipo: when filed, who is the holder, his position on oss, what is planned to do with the patents, reason for patent if known? - What already known proposed or developed alternate concepts do exists and are these also in danger?

Platform - Provider: Mozilla, mozdev etc. - what is the official mozilla point of view, declared position, current or announced or expectable interest? - what the inofficial one of core developers as well as moziilla and firefox core related communities, are there discussions, is it actual in the community or group? - what specs, actual need/demand, expectations/requirements, concepts, approaches and discussion already exist? - what other interested parties that might or already demands the feature and function?

actual situation: firefox and corporate use : what a possible customer searching the web currently sees

From the position of a company considering deployment and use of firefox, for everyone starting a research on "firefox" combined with "corporate network" or their sysnonyms.

Searches like these are used to verify the project, backup/ support decision process as well as to select candidates for further evaluation from exisitng projects, vendpors,. suplpliers.

general 'knock-out' indicators are:

first class: - no dedicated website provided by project, supplier, vendor - no current, outdated or irrelevant information (like the previous text here - see obsolete section) - no current development and releases covering at least firefox 1,5 -2.x - no current downloads, site hits - no identifiable userbase or size of actuall installations unknown or very low - no mailinglists, forums etc. or not returned by results - no active community of users and developers - no active community support - no active bug-tracking - concept proven as not practical, logical approch or obsoleted by current different ones

second class: - no or bad online and/or common media coverage - current unfixed security problems - solution provided as oss is part of larger, commercial application

The decision wether the project itself is reasonable as well wether a vendor or supplier is a candidate is made quickly, not showing up in a general query on the projects target mostly results in not beeing pre-evaluated and therefore not beeing considered as solution provider.

Overall picture based on results

Using google as 'eyes', the results returned were linked to resources with felt ~90% of the checked ones having the following general problems:

- to old / obsolete: the date last changed is more than 1 or 2 years - unaccessable/unaviable - documentation etc. - downloads unaviable - sourcecode was unaviable

- development stopped: no active developmend planned, no plan published, active bug-management. - no new users: project has had no new users (downloads, comments, reviews) - no current information, active, dedicated community or a board or even current related thread, - few or no interlinking between projects, not mentioned in current, related results, no reviews.

After a surge in interest and many corporate use related projects on tools, functions etc. in 2004, 2005 and 2006, most projects were closed or died after an average time of 1-1,5 years existence for mostly unknwon, not offically stated reasons.

There are very few related projects which can mostly be found only by references in other documents. These are also not showing up in google.

Blogs, articles etc. covering the field mostly show concern about the neglectance of this theme and/or link to old/obsolete resources.

Conclusions baesd on actual situation =

An it - staff/employee asked today to check "wether it would be reasonable and responsible to switch the whole company to firefox." based on search engine results would almost certainly decide that he never would bear the risk.

Main reasons are:

There is no common definition all interested parties aggree on for: -one or more usage scenarios -list of requirements resulting from usage scenario

There seems to be no red thread for future development, no or few articipients etc. - groups with equal or related interests are not connected with each other - commonly expected 'community' of people interested in the matter

Corporate usage of firefox does not seem to be of much general interest. The need is only seen by several, mostly not-connected groups and individual people but not by mozilla itself.

There is an opensource/commercial product with strucutre and functions as well as modules drsigned similar to the concept described here, but the user base exstimated from teh number of regisered users in theor forum appears to be small, but at least their community lives...

Media coverage is low, with current articles mostly pointing out, again and again the need for corporate specific concepts and functions. Older articles mostly relate to the sudden rise of corporate installation around 2004-2006.

There are several groups and projects with objectives related to this field of interest, but theire scope is quite different: from just single tool oriented (package builder), some (mostly dead and/or without a first release) enterprise focused general projects.

There are a couple tools aviable to at least build an xpi - package

There are already aviable addons providing most features/functions on the user side, but without the requirements of corporate use.

Some functions in the current default settings violate management and security standards.

Possible 'way out?' =

With the upstream disributor not interested and only little public attention to the matter at hand, no big fish having announced to claim that area, the time should be ideal to combine efforts.

The several interested parties should define/aggree on:

a) a framework that provides unified, cvontrolled access to features/functions neccessary in corporate networks rpovided by firefox or extensions.

b) definiton of common corporate functions required,like software management, access controll, protection against changes etc. and reference implementations

c) definition of an interface to extensions, plugins, applications to enforce corporate wide policies for access, configuration settings, default values etc. on a per-addon as well as per-addon-per-item level.

c) gain argumtative weight by the combined support of cinterested groups and users

To aid collaboration things missing are: - a central, dedicated and living website providing initial information, faq, existing solutions, similar or related projects - said website rated within the first 5-10 results returned by queries like the ones decribed here. - a definition of corporate use and the resulting requirements - possible concepts - corporate usage scenarios - resources

´software evaluation - first quick glance` - method, results and ratings in detail

This method is focused on the scenario 'corporate software project` and meant to be used for for initial eveluation of of aviable sources and possible candidates and selecting candidates and suppliers for further evaluation, as well as meta-information providing static ratings based on the results of this process..


Using one or two popular searchengines to crawl the web for a list of questions to ask, facts to check, points to consider, this first evaluation gives, apart from the mere technical facts, am impression and feelingm especially wether software is fit for production usage and the vemdor is reliable, even before having a further look at the other information and spending an average of 5- 15 minutes on each query, questions answered by results average total: eg. 10 comp / -5std.

When using limited time for each query to check results, select a candidate, do the checks and documents results as well for the whole process makes for predictable use of time - resources.

Should be done simoultanously by two or more individual testers to reduce personal views of testers on results.

Questions can be implemented with webbased query systems, even on the free ones existing.

Ratingmodell, queried facts and their rating, querylevel are templated and provided as lists. Typical range would be 1-5, 5-10 targets for evalution using this method.

Questions and the categories they belong to are those deemed to be typical and/or required The decision wether to further evaluate or to skip a product is often based on this first impression and the feeling, especiall if the search has the additional purpose to check the general prakticability of the proposal.

Now, let`s try that with queries combining "firefox" without version number with the words "customize" and "company" as well as their most common synonyms like "corporate" instead of "company".

initial evaluation: using firefox as corporate browser - googled results

"firefox 3 customization corporate usage" comes up with just one or two links from the year 2004 one of wich leads to an disabled account-

"firefox custom company" as well as "firefox custom company version" come up without exact or even related matches

"firefox customize company use" at least results in linking the CCK - Extension - grave as well as a todo - list and some archived conversations at the end of the page.

CCK - Extension via Last comment was added in 2005, this is also the last time something changed. Searching for firefox and/or company,enterprise or similar keywords Typical non-related results were a lot of links on 'toolbar customization".

Replacing firefox with internet explorer also results in few hits, but "internet explorer customization corporate usage" results in the ie administration kit showing up at third position.

Overall impression: A couple years ago the distribution of customized firefox packages in a company was a high-level theme to which numerous projects were created to provide the neccessary tools.

Current relevant information is nearly nonexistant.

design sketch: a 'Corporate Firefox' Toolkit

design sketch: Toolkit module - Firefox and addon lifecylce management

The solution should provide functions for the following typical, reoccurring management tasks:

Monitor: - monitor firefox and addon releases and aviable updates - detect and report installations with missing or still pending updates or errors,

Manage: - Enable, disable, update, upgrade, remove or replace an application or addons based on policy or all managed installations.

Update: - download updates from the original source, apply signature, redistribute them based on per-packet lock/free switch

- state of lock/free switch depends on wether the preliminary required verification-process was completed and confirmed as successfull.

- wizard to run the per-package verification - process: check the QA - policy assigned t, check changelogs, run tests and document results, finally sign the update package and make it aviable via an corporate run server. (this will be a common demand...)

- create and provide notification for the user on the update, the reason, relevant changes and possible issues or use automatic notification for normal, small updates - this information can be provided by the verification-process.

Rollback: - roll-back of any changes made to software, eg. switch down to a previous version.

- document using an audit-trail: -- all actions and changes made by the user -- all changes made to configuration settings -- all changes made to a software package and provide a per-package history

-- provide a datasource for reports

- research the reason for errors from relations between errors, a raising application error rate,installed addons, last changes, with per-installation logdata made aviable by the distributed installations (flat files, eg. via webdav, smb etc.).

A feature to provide information on current security threats for the applicaton as well as addons is missing.

Ok, there is a tutorial on a custom update server, but nothing that covers the other demands.


--- multiple users providing high quality

existance and non-existance of 'official' administration tools

possible design of a toolkit providing life-cycle management for distributed firefox installations in corporate or similar networks

Since requirements can be bit abstract, the following sketch design describes possible structure based on expected and/or required configuration and management tools

Functions and features are grouped into hypothetical packages or products, one would/could expect to find when searching for something like "Corporate firefox toolkit" or "corporate framework for firefox".

The primary demand defined as conditio sine qqua non:

The product can be installed, managed and used

with only minor changes neccessary to be expected on the existing it infrastructure.

Such a product could consist of eg.:

- corporate firefox manager tookit: -- run as ff addon or xul app -- plugin interface and structure, plugins are addons -- access to main app, app manger and subtrees as well as moduls based on acl - common access controll lists providing typical acl - settings like 'per remote ip/net etc.' -

provide functions and and interfaces: - required for lifecycle management of the main package, compliant with ITIL - to act as framework for other addons

Possible category structure for modules: - configuration and settings: - policy - apply configuration settings to firefox installations assigned to groups, define and distribute mandatory settings, lockdown of user - read/write access to all or parts of the configuration - profile manager: manage firefox profils, backup/restore etc. policies etc - addons and addon - settings: policy controlled install/update addons, access addon - software manager: install, update, removal - distribution : - manage install/update/upgrade as well as rollback for firefox, addons - is primary (only) uodate and addonserver for all ff installations

A 'security' page and other common functions of a function or feature could be provided by the main package but use settings provided by the addon they`re configured for.

possible structure and functions of a manager application:

- corporate firefox manager:

- manager - provide and manage distribution of: - configuration: - global, per group/user configurations and settings - global, per user/group policys for configuration and settings - profile: - per - user profile and per user settings, inheriting global configs and settings - profile backup/restore

- distributor: - structure, security settings and the content of directories exported via ftp, ftps, smb, http, etc. - updates, provides addons and custom software - package builder:

design sketch: possible corporate user-level applications using the tookit as management framework

functions and features possibly usefull in corporate networks

The following describes a possible solution to provide

- functions/features neccessary or helpfull for the corporaton and it`s employees work. - interfaces and usage easely accepted by users

in a corporate network, using

the application provided for the enduser as well as aviable source-code and documentation of existing, designed, planed for: - firefox - addons - firefox - based applications as well as webpages

and the framework of the previously described network toolkit

The functions and features in this list are grouped into packages one would/could expect or agree to find and use , when searching for something like a "corporate community server" product containing:

- bookmark server: with user, group, global lists, change monitor, fuzzy-able search for near matches, bookmark-list-sharing with public, custom group, user security definitions, also backup, import/export,loadbalancing and/or ha master-slave config for replication/syncing/backup/failover-hotstandby, bookmark lists between different bookmark servers,

existing software:

- contact /phonebook server corporate phonebook, per - department, categories, groups, functions

- central notice/info/alert - tool, to inform users of works like maintanance,

(RSS, very simple one), aviable via undeletable button, a tray icon, displayed once at starttime,  and a tray icon indicating new/unread info, alert after x min unread once brwoser  was started as well as x numbers the brwoser was restarted within a specified time range.  

- corporate info tool: information about new documents etc. as well as categorie, audience, scope, desc. (RSS, very simple one), aviable via undeletable button as well as at starttime and a tray icon indicating new/unread info

- corporate community server/client per user current status/info, out-of-house, vacancy etc. as well as links to alternate user, online chat -client supporting jabber, irc etc. chat-servers for dev.: jabber, irc protected streams groups, rooms etc.

server: 1) corporate community a) web tree, firefox acls, provides xul based chat client, default, b) runs locally installed chat client

2) corporate chat server a) in-house run chat server, external sw. required, jabber, irc, icq support, defaults to jabber, configuration package for linux provided, b) links to remote chat server

Resources on the web

competing commercial products

FrontMotion, half-commercial, package building billed,


actual news and discussions


Slahdotdiscussion following the article: - from people who "don’t really understand enterprise requirements."


=== 'firefox in corporate networks': background and meta information ===

==== projects and other resources ====


==== mikes musings: enterprise section ====

- Collection of other random thoughts, press, and other articles on Firefox Deployments in Enterprise and Large Organizations

- - - - - - - - - -


package management: concepts and existing tools


to customize, repack and build custom distribution releases

existing solutions (opensource)
CCK - Toolkit


Latest release: CCK Wizard 1.1 - October 20, 2006 by Michael Kaply Release notes:

Description: The CCK Wizard can be used to create an extension that customizes Firefox. To access it, after installation, select Tools->CCK Wizard...

estimated vitality: revived


Download current release/addon:


Others resources:



Last release: Version 1.4 - 23-Feb-2006

estimated vitality: dead, bitrot




Support:Best Practices for Support Documents

common development tools

basic technologies, methods and concepts, etc.




development methods:


build - environment:


extension development tools


X509 certficates

silent install:

Mozilla Firefox Corporate Rollout Mini-HOWTO -

custom installer:

Access and security

Customitzation, configuration and settings

Examples / reference / scratch designs and corporate usage scenarios

refernce design: corporate scenario (Dwe 20:57, 23 June 2008 (PDT) just detected, matches the scenario this article covers, but in a very high - level: the avaerasge -> 100+ systems admin wo`t have the time...

=== historic, unverified, oboslete ===#,289142,sid39_gci956309,00.html

projects and addons covering required functions, xul, 1.2a Mozilla/5.0 and JRE v1.3.1 i, xul, 1.x, lc: 2005 "first off you should use a pretty recent version of Firefox (at least version 1.02, previous versions have a bug), and open this current page with the browser. Don't have an updated version?"


needfull things: update notifier: app + add,

rss - reader,

reminder fox: erinnerungen - alarme: