Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Internet Explorer Businesses Microsoft

Corporate IT Just Won't Let IE6 Die 479

alphadogg writes "Security experts, industry analysts, and even Microsoft recommend that IT departments upgrade Internet Explorer 6, yet new research shows that while there may have recently been a mock funeral for the aging browser, IE6 is still around and doing well, especially during standard business hours." The article says that they are seeing 6-13% peaking during business hours. Around here we see less than 1.5% IE6, but since we see only 10% IE in general, I imagine we're just lucky.
This discussion has been archived. No new comments can be posted.

Corporate IT Just Won't Let IE6 Die

Comments Filter:
  • Well... (Score:5, Insightful)

    by drolli ( 522659 ) on Tuesday April 27, 2010 @09:58AM (#31998838) Journal
    Once the crappy internal web applications for managing some forms have been duct-taped together by a student worker, nodody dares to touch a single thing. You can only get burned.
  • by fieldstone ( 985598 ) on Tuesday April 27, 2010 @10:00AM (#31998868)
    But... isn't using IE6 in a corporate environment the equivalent of saying, "Yes, please infect my computers with malware without warning!"? That's not even to touch matters of compatibility... Doesn't security mean anything? And wouldn't most IE6 web apps work in IE8 under its compatibility mode... or am I being overly optimistic about said compatibility mode?
  • by Renegade Lisp ( 315687 ) * on Tuesday April 27, 2010 @10:02AM (#31998896)

    but I'm working on it! The only way to get Corporate/Management off of IE6 is to fix any web apps you have in your organization that won't work on anything but that.

    At the same time, more and more important sites out there need to stop supporting IE6. Where I work now, we are forced to use IE6 because it is "company standard", but it is accepted, at the same time, that we need to look up stuff on external web sites all the time. If those sites no longer support our browser, that would be an increasingly urgent reason to upgrade.

    Once that decision is taken, it would probably only take between 4 and 6 years to actually get the project implemented...

  • by Anonymous Coward on Tuesday April 27, 2010 @10:03AM (#31998918)

    Most IT departments have their hands tied for a majority of their projects. Be it, homegrown app compatibility, budget, balancing higher priority projects, upper management or what have you. I'm not surprised by this at all. Just because a piece of software is "retired" doesn't mean everything that relies on it is. IE6 is not going away completely for a LONG time.

  • Re:Legacy apps (Score:2, Insightful)

    by Anonymous Coward on Tuesday April 27, 2010 @10:07AM (#31998970)

    Oh, the millions of dollars excuse again. You can keep IE6 for accessing internal applications, just deploy a modern browser for using the web and b2b web applications. It can't cost more to support than the cost of cleaning up a malware'd network. If it costs millions of company dollars to install and maintain a web browser, that is incompetence.

  • by nosfucious ( 157958 ) on Tuesday April 27, 2010 @10:25AM (#31999208)

    Go poke the CIO instead. That's where the buck stops.

    An IT department can make all the technical cases it want to. However, until the equation of $$$StandStill is less than $$$Moveforward, $$$StandStill is where you'll be.

    And no, the CIO is almost never a technical weenie. It's just another seat on the board, with fat shareholder priviledges.

  • by amplt1337 ( 707922 ) on Tuesday April 27, 2010 @10:28AM (#31999254) Journal

    No, it's equivalent to saying "We need to run mission-critical software that won't run on higher versions of IE."

    I've actually had to go around uninstalling IE 7 and 8 from user machines and re-installing IE 6 because the users have to run IE6-only software, or the vendor's IE7 installer doesn't work, or there are bugs in the IE 7 version, etc. etc. Sure, I'd love to get rid of the vendor -- you think that's easy?

    Of course, I also encourage people to do any *ahem* personal browsing in Firefox anyway, but IE6 isn't going to go away until we don't need it. If the web-designer artistes out there want to complain about cross-browser compatibility, they can either bite me, or come down and do my users' jobs for them.

  • by causality ( 777677 ) on Tuesday April 27, 2010 @10:31AM (#31999294)

    It's because of familiarity, I'm pretty sure. I've had clients absolutely refuse to use anything else, even IE8, because it "felt" (in other words, looked) different from what they were used to. My solution to this is usually one of the Firefox themes that makes Firefox look like IE. The IE6 one is pretty flawless.

    If a client cares about that more than all of the problems with IE6, then they should not have a position in their company that allows them to make IT-related decisions.

  • Re:Legacy apps (Score:5, Insightful)

    by DrgnDancer ( 137700 ) on Tuesday April 27, 2010 @10:35AM (#31999342) Homepage

    I realize this probably wasn't your fault in the first place, but it *is* your company's own fault. Eventually, Microsoft *will* stop supporting IE6 (XP is supposed to go out of support in a few years, and there's no IE6 for Vista or 7). Those millions of dollars *will* have to be spent. Why not start working on it now and spread the pain out. All of this "but it will cost us million of dollars to make our stuff work like it should have in the first place!" whinging by various corporate managers kind of ridiculous. You (not you personally, but generically "you IT managers") know they won't support this stuff forever, you could fix this over time and spend very little quarter by quarter, but you'd rather cry about the million of dollars it will cost all at once when you eventually HAVE to deal with it.

  • by Anonymous Coward on Tuesday April 27, 2010 @10:43AM (#31999452)

    I don't understand why you just don't treat IE6 as a specialized internal apps platform and use something else, like Firefox, as a web browser.

    Developers could then code new apps to modern standards and those apps could use Firefox as the apps platform.

  • Re:Well... (Score:5, Insightful)

    by gstoddart ( 321705 ) on Tuesday April 27, 2010 @10:45AM (#31999482) Homepage

    Call in a consulting team, get a quote for reworking it. Doesnt that neatly solve the problem?

    I think you're grossly mis-underestimating the size of the organizations which are still mandating IE 6 as a corporate standard.

    For instance, the government of Canada, I believe, still uses IE 6 as a standard -- that represents something like 200,000+ users.

    The scope of the project to re-certify that much software isn't a small consulting team, and it's sure as hell not a "Rent-A-Coder" fix as suggested in a sibling post. You're talking about vast quantities of commercial software which are already deployed to a large user base.

    The problem becomes that IE 6 is deeply entrenched, and involved in a lot of tasks organizations aren't really willing to have too much down-time with. So, the status quo tends to become a factor.

  • by Anonymous Coward on Tuesday April 27, 2010 @10:46AM (#31999498)

    no, no and no.
    you fix firefox so that ACTIVEX and shit like that WORKS!!!

    i (and probably everyone else) cannot 'fix' the builtin web interface in (expensive) hardware

  • by eln ( 21727 ) on Tuesday April 27, 2010 @10:47AM (#31999520)
    Exactly. Anyone who's had to deal with trying to get an internal development organization to update anything knows how painful it can be. Absent a clear and urgent need expressed from corporate executive management, they'll put your concerns on the back burner forever, especially if they also develop for external paying clients. So, if you have a tool that's only used internally, updates to that tool can take many months or even years to get done. Meanwhile, the poor downtrodden IT guys have to support the ancient monstrosity the whole company depends on but no one wants to spend the time or money updating because it doesn't immediately generate revenue. Thus, we get stuck with IE6 years beyond when it should have been retired.
  • by The Angry Mick ( 632931 ) on Tuesday April 27, 2010 @10:51AM (#31999560) Homepage

    So if you want to kill IE6, that means dropping support for IE6, or if you have paying customers, charge them more if they're using IE6, and tell them that.

    Unfortunately, not all the people using IE6 are customers trying to access shopping sites.

    The non-profit I work receives a pile of grant money from several state and local governments, and because of this, we are required to submit grant activity data back to the sources. Guess which browser their reporting sites demand?

    One of the state agencies actually has a couple of sites that we're required to use, and both are developed on the same floor in the same building by two guys who sit less than twelve feet apart. One guy's site will run run in IE8 and Firefox without problems, the other guy's will only run in IE6.

  • by Ltap ( 1572175 ) on Tuesday April 27, 2010 @10:54AM (#31999612) Homepage
    One part resistance to change, two parts stupidity, three parts laziness, one part cheapness (don't want to dedicate time to testing and rolling out a major upgrade), and three parts apathy on the part of everyone.
  • by Tridus ( 79566 ) on Tuesday April 27, 2010 @10:57AM (#31999644) Homepage

    Now that's a good idea. You should post your infected image code, I'm sure people would love to do the same thing internally.

  • Why are you browsing from a VM like that anyway?
    If those machines exist so you can test your products in antiquated browsers, don't use them for anything else...

  • by DdJ ( 10790 ) on Tuesday April 27, 2010 @11:06AM (#31999770) Homepage Journal

    Doesn't security mean anything?

    Yes! It simply doesn't meaneverything.

    A perfectly secure system that doesn't do anything is useless. But an insecure system that malfunctions and loses $5 with a 50% chance time you press a button is still worth using if it earns $11 when it doesn't malfunction.

    There's a cost/benefit analysis going on. For a lot of businesses, even with the insecurities and incompatibilities, the result of that cost/benefit analysis is "keep running IE6". The solution really is to take those business functions that only work on IE6 and update them so they work with newer browsers... as long as the cost savings of moving to a newer browser exceeds the cost of that mitigation effort.

    When it doesn't, you end up deciding to keep running IE6. On purpose. Without being wrong.

  • by natehoy ( 1608657 ) on Tuesday April 27, 2010 @11:14AM (#31999872) Journal

    I just HOPE that in the future, development teams will fucking stick to standards!

    Microsoft sold senior management on a series of rapid application development tools that allowed developers to write very effective applications very quickly. Rational companies use the most effective tool to solve a business problem, and in a lot of heavy-Microsoft shops those tools were FrontPage, SQL Server, Visual(insert language here), and the rest of the Microsoft development suite that was almost free once you drank the whole glass of kool-aid, Cherry Redmond flavor.

    I don't think in all fairness that anyone could have predicted that Microsoft would not only break compatibility with other browsers, but also break compatibility with their own. The fact remains that a lot of software written with Microsoft toolkits from the IE6 era will only run on IE6. There is no IE6 compatibility mode in any meaningful sense of the term, and there is no "take the source code, shove it into this tool, recompile, now you're IE7+ compatible!" magic bullet, even when you have the original source code and the latest Microsoft tools. It requires recoding. Long, tedious, manual recoding.

    As far as external vendor software goes, hell, "follows Web standards" isn't even on the RFP checklist at many companies now, and it certainly wasn't back then. The "standard" was Microsoft, because that's what everyone ran. If you could write your software more cheaply by using an ActiveX widget, so be it. That's what you did. And Microsoft will always support this stuff, because that's what they do, right?

    The business shops around for the software that best solves the problem they have at the lowest price they can get away with. IT might get involved to make sure it works with the back-end systems, but very few people care too deeply about the desktop.

    Tons and tons of companies used those tools to write applications for their internal use and also for sale to other companies. Then Microsoft came out with IE7 and basically told all of those developers that their applications would need to be almost completely rewritten.

    Development teams will fucking stick to standards, but they are the standards of the company they work for, and last I checked IEEE doesn't run most companies unless I missed the global memo about the planetary business reorganization.

    I'm just glad I never got into desktop application development. Writing useful programming is a whole lot easier on the midrange field, because my apps run on a single box, and I don't give a rat's ass what version of telnet you use to access my apps as long as it supports the 5250 function keys. I'm free to think about functionality, performance, security, and stability. I don't deal with desktop compatibility and what shade of cerulean the "Accept" button needs to be.

  • by causality ( 777677 ) on Tuesday April 27, 2010 @11:14AM (#31999876)

    It's mostly due to the relationship between the IT staff and the regular employees. In some situations, IT can dictate quite a bit and is left to make their own decisions about security, but in most situations they are essentially the servants of the employees - someone to clean malware off of their computers and be whined at. If the employee(s) doesn't/don't want IE6, then it's harder for IT to make a case to management (since they could otherwise claim that the employees also want an upgrade) to justify upgrading, and most just won't bother unless there's lots of user demand. If the users are against it, it takes either a somewhat reckless IT dept. or a tech-savvy manager to realize that this stuff needs to get done.

    A hypothetical: if my doctor told me that there was a very good medical reason for me to do something, I would follow his advice. I guess you could say that doing what he tells me I should do makes me a "servant" except that he doesn't have a way to force me to do anything. I can realize on my own that it's in my interests to follow the advice he gives me and that I probably don't have the expertise it would take to seriously dispute him.

    Or I could ignore my doctor's hypothetical advice. Since I am paying/hiring him, I can think of him as my "servant" and insist that he never tell me anything I don't want to hear, especially those things that would suggest I should change my lifestyle or otherwise adapt to something new. I can freely ignore any such advice and take the attitude of "what does he care, he got paid." I could do that, but ignoring the sound advice of an expert in his field who is trying to look out for you is generally unwise.

    On the one hand, if you expect users to understand and be able to follow basic procedures without making silly errors they tell you things like "but I'm not a computer expert, I just want it to work!" On the other hand, when you present them with a real computer expert they will ignore his advice the second it means they might lose a pretty icon or a shiny button. So they are like my second hypothetical situation. They neither wish to become experts nor listen to existing experts.

    Name one other profession or trade or area of expertise where expert advice is so routinely ignored for such trivial reasons. It doesn't happen with doctors, lawyers, plumbers, electricians, auto mechanics or insurance agents. "If the users are against it" their ability to understand the full implications of their decision and their background in IT should be considered first and foremost. If not, why don't we have such "mob rule" in all the other departments of major corporations? I'm sure most users would like a $300k/yr raise too, so does that mean Accounting is obligated to accommodate them?

  • by MagikSlinger ( 259969 ) on Tuesday April 27, 2010 @11:39AM (#32000240) Homepage Journal
    The upgrade process is a pain, but it's starting to hurt the company's ability to buy NEW software. We've already face a problem at work where IT now has to allow IE7 on some desktops or Citrix servers. IE6 was such an evil product that Microsoft unleashed on the world, and even Microsoft, I think, realises they're getting hurt by it too. What I wish was there was a painless way of installing IE6 as a separate special browser while the default browser is something better. Oh, funny addendum: the Software Standards & Licensing nazis sent out a sniffer to figure out what people had installed in their desktops, and tried to get us web developers to uninstall Firefox and stick to IE6. HAHA! We develop web apps facing the outside world, as we explained to them. Unless you want 80% of your traffic to stop working, we're keeping Firefox. Then, just to make it more interesting, the corporate web czar sent a note out to all us web developers to start installing and testing against other browsers like Opera and Safari. X-D Left hand, meet the Right hand.
  • by catmistake ( 814204 ) on Tuesday April 27, 2010 @12:01PM (#32000584) Journal
    I think everyone is being overly optimistic about the advantages of upgrading Windows. What I see is eye candy and a few nice features (that we've all envied on other systems, that we —want— but aren't essential) that is distracting everyone away from the fact that all of the official and notorious "Windows headaches" are alive and well in the new version. So... the status quo sucks but it's working somewhat... it's a level of Hell we know well, and the marketing pressure is to ... give it all up for a prettier Hell, that isn't as familiar to us (and the millions that we rely on for support). I'm surprised that not more corporate IT has decided to hunker down, harden/strip/customize/(virtualize?) a Corp standard XP desktop w/ all client/serverapps tweaked, supported by netindustrialzed/superhardened 2003 server(s)... and isolate and freeze that paradigm in carbonite... and begin building layers insulating the environment from possible future headaches with MS or Semantec or whatever breaking it from the outside.

    Before it's said, so what if IE6 doesn't work on the web anymore? Either sandbox everything or keep IE6 for internal webapps alone, prevent it from ever going wan, and just give the diligent users another browser for surfing the web or youtube during the other 6 hours of their work day. Build in the systems breaking as part of the maintenance cycle... and with a lot of hands doing the same well documented things to keep it going, you have a system that can stand the 20 years or so it will take for a solution that advances the feature set enough that the migration pains are worth an actual, attainable benefit.

    so ... really the question isn't why are some corps dragging their feet on migrating to Windows 7... the question is why are so many corporations blowing money money on upgrading (when it's not *necessary*)? (Why should any corporation upgrade to Windows 7?)
  • by delinear ( 991444 ) on Tuesday April 27, 2010 @12:08PM (#32000702)
    Can you not give them a VM for the mission critical stuff? Sooner or later it will become an issue, when MS stop supporting IE6 completely you can't continue to run a browser that's notoriously bad security-wise and is no longer even receiving patches, surely. Best to start the movement now as it will be more painful later, if users need IE6 for mission critical applications or sites, give them a VM. Blacklist everything apart from those sites/apps so they can't use the VM for all their browsing purposes and point out that the best resolution is for them to find alternatives for those mission critical apps. See how long it takes before they're insisting you ditch IE6.
  • by gcmd ( 894557 ) on Tuesday April 27, 2010 @12:10PM (#32000738)
    I beg to differ. I give out medical advice all day, things that are PROVEN to improve your life, decrease your risk of death, and people blissfully ignore it all the time. Stop smoking, get more exercise, watch your diet are just a few of the most popularly ignored pieces of advice. So if people can ignore advice designed to save their lives, why are we surprized that they ignore advice to save their computers?
  • by Arancaytar ( 966377 ) <arancaytar.ilyaran@gmail.com> on Tuesday April 27, 2010 @12:28PM (#32001028) Homepage

    There is a cost to upgrading the corporate intranet, and there is a cost to being owned by industrial spies and spam botnets.

    Executives will upgrade when the cost of the one exceeds the cost of the other. Or otherwise, the company will eventually lose enough money and die.

  • by amicusNYCL ( 1538833 ) on Tuesday April 27, 2010 @12:32PM (#32001084)

    Only fix absolute brokens.

    You ever hear the phrase "if we're not moving forward, we're standing still?" You're advocating using a 9 year old browser which is quite literally orders of magnitude slower with modern web applications, and you think it's a good idea to stick with that plan?

  • But do they care? No -- they bill it back to the business side, while they collect bonuses year to year about how great a job they did that ONE year. It's not about ROI, it's about one year results that you can pin a medal to.

    There is something wrong with that short-term mentality too, but that is a different but related matter.

  • by Anonymous Coward on Tuesday April 27, 2010 @12:43PM (#32001294)

    And people wonder why Apple want's so much control over the iPhone platform. When you support too much legacy stuff, people come to expect it and don't keep their software up-to-date.

  • by HockeyPuck ( 141947 ) on Tuesday April 27, 2010 @12:52PM (#32001416)

    Name one other profession or trade or area of expertise where expert advice is so routinely ignored for such trivial reasons.

    Parents.

  • by vtcodger ( 957785 ) on Tuesday April 27, 2010 @01:53PM (#32002288)

    ***(Why should any corporation upgrade to Windows 7?)***

    You are suggesting that good enough is good enough? My God man are you trying to shut down the money machine and actually have IT provide cost savings? Or better yet fade away like Marx's idea of the fate of the ideal communist state?

    Do you have the slightest idea what your weird ideas will do to the economy?

  • by amicusNYCL ( 1538833 ) on Tuesday April 27, 2010 @02:27PM (#32002710)

    thousands of people defending smoking as "mostly harmless", and second hand smoke as completely inoffensive

    Can you provide even a single reference for that? The reason people smoke is not because they believe it's "mostly harmless". They understand the danger, they just don't care. This is not the attitude that should be taken by any competent IT department. This quote from TFA is interesting:

    "It almost looks like individual Internet users are more tech-advanced at home than the IT departments where they work," said Alden DoRosario, Chitika's CTO, in a statement. "It's crazy to think that people whose job description revolves around employees having secure ways to browse the Web would keep IE6 alive, while these same employees go home to more secure browsers."

So you think that money is the root of all evil. Have you ever asked what is the root of money? -- Ayn Rand

Working...