Slashdot Mirror


Firefox Struggling to Compete as Corporate Browser

ericatcw 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."

8 of 364 comments (clear)

  1. Mo money by ExE122 · · Score: 5, Insightful

    What Mozilla needs to do is create their own operating system and incorporate Firefox into it in such a way that it cannot be uninstalled =P

    Failing that, I think the ideas pointed out in the article are legitimate reasons that IE, albeit an inferior product in most reguards (or maybe all reguards), is dominating the corporate market. I think just the fact that it is a free product hurts them on some level. From my experience in the public sector, the brass always gets a little nervous when you start using the F-word of economics. They would rather dish out a couple grand to have a support and maintenance contract, if not only for the accountability aspect. I can't say that I've ever used FirefoxADM, but as a third party product, it looks like it suffers from the same lack of a guarantee for support and maintenance that the browser does.

    I think the application compatibility is becoming less of a problem. A lot of GUI developers have already been throwing in browser checks for years because of Netscape, so I don't see Firefox as being that big of an issue. I haven't used any webpage IDEs in a while, but I'm willing to bet they already have that integrated as well. I can't recall in the past couple years that I've had a problem loading a page in Firefox.

    Needless to say, I think Mozilla has their work cut out for them. Even if they do end up offering a superior enterprise class product, I think it's gonna be hard to get a lot of companies that have been partnered with M$ for years to move away from IE.

    --
    Capitalism: When it uses the carrot, it's called democracy. When it uses the stick, it's called fascism.
  2. Excellent reason FF is not deployed by smooth+wombat · · Score: 5, Informative
    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.

    The other reason is this narrow-minded mindset that some folks higher up the food chain than the IT department have about anything that isn't Microsoft. I know of one place where I worked that the CIO all but had an apoplectic seizure when she found FF was being used by some of the IT folks (fortunately, after I left). She then ordered that only IE will be used.

    I, and several others where I currently work, use FF. The only thing we have to do is make sure we keep up with the updates as per our Bureau head. In fact, the only time I use IE is when I am on our intranet. For external sites, it's FF all the way. Never had a problem, not even on Microsoft's site when pulling down patches or updates.

    If those two issues can be resolved, easy way to deploy and breaking of the mindset, you would see FF's usage climb. Granted, you'd still have to deal with people who don't know what a browser is but that's a whole other issue.

    --
    We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
  3. Re:dude... by keko_metal · · Score: 5, Insightful

    standards? when have we been there?

  4. Mozilla could do some things better by JShadow21 · · Score: 5, Informative

    I currently deploy Firefox to our corporate workstations, however there are definitely things that Mozilla could do to make Firefox more corporate friendly.

    1. No first part MSIs. The majority of our workstations here are Windows XP. Mozilla doesn't put out an MSI build. There are a few groups that do, such as Frontmotion, but there is always some delay for them to rebuild.

    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.

  5. Re:I would blame this on... by cexshun · · Score: 5, Informative

    Well, here's something that may help. We use this to deploy FF in our AD environment.

    FF Community Edition

    Allows you to install over AD and has a snap-in allowing certain settings to be controlled over AD. The packages are free, or you can have them make a custom package with specific extensions for a fee.
  6. Re:Authentication by zoward · · Score: 5, Informative

    There's a Firefox registry setting you can use to turn on automatic NTLM authentication.

    Type "about:config" into the address box in Firefox and the list of registry settings will appear.
    Then type "ntlm" into the filter box, and the list of settings will shrink to three. Choose:

    network.automatic-ntlm-auth.trusted.uris

    by right-clicking it, and choose Modify. Add to this string a list of URL's for sites that require NTLM authentication, separated by commas (eg, "http//intranet, http://wwwpost/"). URL's "below" the ones spoecified (such as "http://intranet/news") will inherit the authentication).

    Since it helps keep users from picking up malware, Firefox has been adopted as the Windows browser of choice at our 2000-employee computer firm.

    --
    "Can't you see that everyone is buying station wagons?"
  7. Re:dude... by Bert64 · · Score: 5, Interesting

    However there are similar situations which go the other way...
    I know of at least one company that didn't want to develop/test their internal apps for more than 1 browser, but they have a number of mac and solaris based workstations in the company... Their solution was to have firefox installed on every machine and make people use that. Several of their internal apps don't work with ie at all.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  8. Re:Authentication by thePowerOfGrayskull · · Score: 5, Interesting

    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.