Gartner: Existing options for migrating from IE 6 are too pricey, risky

By | November 12, 2010, 11:59am PST

Gartner Inc. analysts have published a research note for their clients who are still stuck on Internet Explorer 6, offering guidance around “Solving the IE 6 Dilemma.” But none of options included are very palatable — at least not according to Gartner.

Gartner notes that a number of organizations still are supporting and/or standardizing on IE 6 — nine years after its introduction — because they’ve built up sizable installed bases of line-of-business applications that are IE 6-dependent (among other reasons). These organizations aren’t easily able to move to IE 8 or Windows 7 because of these dependencies, they said.

Gartner estimates that “organizations running IE6 report that up to 40% of homegrown browser applications fail to run properly with IE8.”

“Furthermore, many ISV applications, including complex ERP and CRM applications, with lengthy and expensive migration requirements, must be remediated before IE8 can be used,” Gartner officials said in the research note. “Through 2014, IE8 compatibility problems will cause at least 20% of organizations to run overtime or overbudget on their Windows 7 migration projects,” Gartner estimated.

The research outfit is advising these customers to “continue to fix or replace affected applications with ones that adhere to Internet standards by April 2014″ (the date XP SP3 support ends). But fixing apps is hard and time consuming, especially for those with hundreds or thousands of internally developed programs, Gartner acknowledged.

There are  some temporary solutions that IE6-burdened organizations can apply, but none of them are without problems, Gartner said. Microsoft offers customers a few possible workarounds, including terminal services and MED-V, its operating-system virtualization technology. Various other software vendors, including VMware, also offer virtualization technologies that can be  used to run IE 6 applications on top of Windows 7, the researchers noted.

The problem? Microsoft’s offerings are pricey (MED-V is available only to customers who purchase Microsoft’s Software Assurance licensing), Gartner said. And the third-party offerings are potentially fraught with legal complications, the Gartner analysts added.

Companies including InstallFree, VMware, Symantec and Spoon.Net are offering tools specifically for virtualizing older versions of IE for use on Windows 7, Gartner said. “They embed certain OS components with the IE ‘bubbles’ to allow IE6 or IE7 to run and provide compatibility. But this kind of virtualization may run afoul of Microsoft licensing, Gartner is warning its clients.

So what’s a customer stuck on IE 6 to do?

“A set of (IE 6 migration) tools from Microsoft would be nice,” said Gartner analyst Michael Silver, “But Microsoft seems to have decided not to help extend the life of IE 6 apps.” (A decision applauded by many, but not all,developers, partners and customers, I’d point out.)

Gartner is suggesting its customers request indemnification clauses be added to their contracts. From the list of recommendations in Gartner’s research note:

“Request Microsoft to grant specific contractual amendments to allow you to virtualize IE6 as a Windows 7 compatibility solution without fear of reprisal (but consider that Microsoft could still pursue your application virtualization vendor with legal action). Organizations in need of IE6 compatibility solutions that don’t have sufficient licenses to use Terminal Services and want to comply with Microsoft’s recommendation to avoid IE6 application virtualization should petition Microsoft for use of Windows 2003 Server software and associated Remote Desktop Services (RDS) client access licenses (CALs) for the sole use of accessing IE6 at no charge through 8 April 2014.”

“If Microsoft hates these (third-party) solutions, maybe they should improve terminal services or offer something lighter-weight than MED-V,” Silver opined.

I asked Microsoft officials for comment on Gartner’s report and was referred to a recent Microsoft blog posts on how to deploy various Microsoft virtualization licensing options as part of a migration to Windows 7. Microsoft execs had nothing specific to say about Gartner’s IE 6-focused recommendations.

Update: I did get an updated statement from Microsoft, however, after this post was published. The Softies emphasized other researchers have said the majority of business users are planning to move to Windows 7 and IE 8 in the next 24 months.  From a spokesperson:

“To help customers take advantage of the modern desktop Microsoft makes available a significant number of resources to help organizations with their migrations to Windows 7 and Internet Explorer 8 including: Webcasts, Prescriptive guidance, Whitepapers, Tools; and Temporary virtualization solutions.

“Extensive information on all of these resources is available to customers on our  Springboard, MSDN and Windows 7 Enterprise sites.”

Any business customers out there have other options they’re considering or implementing to wean your organization from IE 6?

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Mary Jo has covered the tech industry for more than 25 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Disclosure

Mary-Jo Foley

Freelance journalist/blogger Mary Jo Foley has nothing to disclose. WYSIWYG (what you see is what you get). I do not own Microsoft stock or stock in any of its partners or competitors. I have no business ventures that are sponsored by/funded by Microsoft or any of its partners or competitors.

Biography

Mary-Jo Foley

Mary Jo Foley has covered the tech industry for 25 years for a variety of publications, including ZDNet, eWeek and Baseline. She has kept close tabs on Microsoft strategy, products and technologies for the past 10 years. In the late 1990s, she penned the award-winning "At The Evil Empire" column for ZDNet, and more recently the Microsoft Watch blog for Ziff Davis.

Got a tip? Send her an email with your rants, rumors, tips and tattles. Confidentiality guaranteed.

60
Comments

Join the conversation!

Just In

RE: Gartner: Existing options for migrating from IE 6 are too pricey, risky
makrekdw73-24353635615163652143356448933213 Updated - 10th Nov
Fortunate enough we all identified , this phenomenal webpage, nflshop often makes distinct toward bookmark this item so i cheap Clay Matthews Jerseys can arise that will help in generacheap Aaron Rodgers Jerseys l.
0 Votes
+ -
People should be fired for this debacle.

If nothing else, you need to get away from Proprietary platforms. That includes just about anything Microsoft.
@itguy08 : Fanboi or Linux zealot? Can't tell. happy
@Gis Bun

Both, I'd say.
@Gis Bun: he still has a solid point. Any IT director or decision-maker who runs a company into this kind of expensive (and ultimately unsustainable) mess _should_ be fired.

Relying on vendor promises without alternative or option long-term is sheer incompetence on the IT decision-makers' part. IT is supposed to help a business profit, not become a money-sink.

This is frickin' IT management 101 FFS...
0 Votes
+ -
@Gis Bun and Lerianis10
Info-Dave 14th Nov 2010
It's your kind of myopic view of technology that got the corporate world saddled with these IE6 based applications in the first place. Microsoft completely abandon these ActiveX elements in IE7 and shows no sign of supporting them in the future (unless you count XP Mode as support).

Here's what you guys should do: Rewrite all your IE6 applications in Silverlight. It's a RIA tool that will let you develop applications that no other platform can touch. They will look so cool! You will remain tied to the hip with Microsoft and force another decade of job security. Silverlight is the next IE6.
@Info-Dave

Totally agree! Why any IT manager would touch Silverlight (or Flash for that matter) is completely beyond me. Totally agree with Random_walk as well: I am loving how much I get to say "I told you so" to all those people who wrote code for IE6. Be nice if MS offered to pay for code rewrites. wink
0 Votes
+ -
They never could understand the web.
@Gis Bun
0 Votes
+ -
And who's fault is that?
ahh so 16th Nov 2010
nine years after its introduction ? because they?ve built up sizable installed bases of line-of-business applications that are IE 6-dependent (among other reasons). These organizations aren?t easily able to move to IE 8 or Windows 7 because of these dependencies, they said.

Who created these dependencies in the first place?

One word.

Hint: It begins with an "M".
Most people are ALREADY using IE8 AT HOME.... no reason why there should need to be any retraining in order to use ATV from youth to kill somebody that you career from any company website is the best buy if you it.
0 Votes
+ -
I agree, they should be fired
Mister Spock 12th Nov 2010
for not building their applications with the ability to move forward with technology, or not updating their apps to current standards.

But why am I discussing this with you? You could never understand at the levels on which these discussion are held.
plain
@Mister Spock: That's the problem with vendor religion. It masks incompetence. If you cannot run an application on more than one browser type, or on more than one client type, then it is a bad solution.

That said, this mess show just how blinded, incompetent, and downright worshipful too many IT decision makers are when it comes to Microsoft. And Microsoft itself, like any vendor, obviously does _nothing_ to rectify the problem.
@Mister Spock

It all goes to tieing yourself to one solution. It's really simple.... Purchase from vendors that support multiple platforms. It's really simple.

Your business needs to be agile. That means with everything, including your IT systems.

Sadly way too many get locked into proprietary systems and that causes these pain points. If people were doing their jobs this would not be an issue.

It's unfortunate that most with these issues are tied to Microsoft but that's what you get for sleeping with the devil.
I can't agree with this Gartner note. It'd be a lot cheaper to just hire a few web developers to bring the code up to speed. Also maybe its time to update their web applications if they are still using it for 9 years. Bite the bullet and upgrade already.
@Loverock Davidson

Agreed. They should be able to keep backwards compatibility with the old 'databases' and other things.
0 Votes
+ -
Yep, it'd be cheaper...
fjpoblam Updated - 12th Nov 2010
@Loverock Davidson ...but sometimes these are mission-critical apps for large corporations with tight budgets, f*up bureacracies, impatient users, and time constraints. There'll be user training on new browsers, too, once the apps are upgraded. (These are often walled-garden shops, for the apps involved). You may have a payroll system, a personnel system, an equipment tracking system, a land mapping system, and all sorts of disparate systems, all on IE6, requiring expertise (coders) in a variety of areas. Ends up (including planning, training, etc.) no small task. Yes, the organization is to blame for not getting off their duffs sooner. But it is definitely pricey and risky.

My hospital uses IE6 for its patient tracking system (among other things, I'm sure). I certainly don't want to place the hospital patients in peril of IE8 testing problems. Risky.
@fjpoblam

If the user interface is THE SAME (and you should damned well be able to code an application so it was exactly the same as an OLD application, just compatible with IE8+).... there is no training that would need done.

Also, the browsers are MUCH simpler to use than IE6 today, so that whole 'retraining on different browser' is a LIE of the worst sort.
Most people are ALREADY using IE8 AT HOME.... no reason why there should need to be any retraining in order to use it.
@Lerianis

Except that in most cases it's not really about the interface... or training... or anything else that has to do with the end user. I bet that the app described in fjboblam's comment has some dependencies on application components (e.g. ActiveX controls, Java) that are simply not compatible with IE8 because of some system level changes Microsoft did in the browser (if you don't believe me, just go to www.netlabels.com and try to run their Print Labels application and see how that works in your IE8). This is not an issue of laziness, or unwillingness to modernize. It is an issue of conflicting priorities, time and budget... and it's good that enterprises have some solutions available to carry them through the transition.
@Loverock Davidson: You obviously have never worked in the enterprise. It is not "a lot cheaper" to overhaul an inherited ERP, CRM, or other internal mission-critical system that cost millions of dollars in the first place. This is doubly true when you consider that the stuff was likely written in deprecated and spaghetti-like MSFT-oriented code, with no regard for best practices.

The disruptions alone are expensive, let alone the cost of consultants, programmers, and the often cobbled-together off-the-shelf solutions that comprise that overhaul.

But sure - keep preaching your gospel from the passenger seat of that black-and-white VW Beetle you apparently work out of. wink
I think that those still using IE6 after over 4 years since IE8 came out have scr?wed themselves up. They could be paying dearly for pinning the development on an important application on a specific version [or browser]. Actually it's more like 5 years - add a year while IE7 was in beta and RC modes. Pure incompitence.

Management [well almost all] were smart enough to get away from Fortran and COBOL. I guess management's level of intelligence has dropped quite a bit.
@Gis Bun Sorry, FORTRAN and COBOL are still thriving. Maybe not in your world, but in real business, where thousands of transactions a second happen (think First Data and its processing of nearly every credit card transaction in the US) COBOL is still there. The current shipping versions of PeopleSoft ERP (not exactly a small player) also still have COBOL in them.

FORTRAN is still in use in the scientific communities, at least in petrochemicals.

Yes, in your world of start-ups running web apps that only need to serve a few, and a few bugs are OK, they might be gone, but in the world of billions of dollars moving about with no room for error, they are still around.
@grant@... Yep. Many, many cities are still using COBOL.
"I think that those still using IE6 after over 4 years since IE8 came out have scr?wed themselves up."
Why? are you saying that using MS technologies you must rebuild every 4 years? sound like vendors dream, but for clients is more like a nightmare.
Now is all Silverlight, it means in 4 years project would need to be rebuilded using the new technology/version they come up at that point?
I prefer LAMP/MAMP; I know my sites builded 8 years ago run fine & they will keep running fine in the foreseeable future. across platforms/browsers.
@theo_durcan

Big hyperbole, considering that IE6 came out almost 15 YEARS AGO! So... you ARE A LIAR, YES YOU ARE!d

The fact is that IE8 is better made to adhere to standards (not perfectly, but then again no browser does) so it is unlikely that you would have to rewrite until HTML5 came out and was widespread.
0 Votes
+ -
10 years, not 15
Lester Young 12th Nov 2010
@Lerianis10

But the IE-specific conventions are almost 15 years old. Not that that's going to stop the complaining.
@theo_durcan

"Why? are you saying that using MS technologies you must rebuild every 4 years? "

When using any technology you must prepare for future changes. If there's one constant with technology, it's change. And the longer you hold off keeping up with change, the more expensive it's gonna be to keep your company afloat. That's just a fact, plain and simple.
0 Votes
+ -
Can you even count...
zkiwi 13th Nov 2010
IE6 was released in 2001. It's 2010 now. IE7 was released in 2006. Things changed markedly between 2001 and 2010 and people who made Webapps specifically for IE6 have been hooked by it big time. Nothing new in that, expect perhaps the scale of the effect.
0 Votes
+ -
@CobraA1: When using any technology you must prepare for future changes. If there's one constant with technology, it's change. And the longer you hold off keeping up with change, the more expensive it's gonna be to keep your company afloat. That's just a fact, plain and simple.

IBM ensures their big iron systems run code, unmodified, from decades ago. Sun (Oracle) has a binary guarantee program that's existed since Solaris 2.6 released in mid 1997.

While I understand the complexities of writing software and certainly the problem with writing for IE 6 we should change our way of thinking so that we attempt to get longevity out of applications.
@CobraA1:

"When using any technology you must prepare for future changes"

Certainly - and one can start by sticking to vendor-neutral standards and practices, instead of relying on one proprietary vendor to solve your problems for you. With that one statement, you've given the best reason to avoid Microsoft-offered solutions that I've seen in this article... which I believe was Theo's point in the first place.
@theo_durcan "foreseeable future" is the issue. Maybe LAMP/MAMP will be around for the next 100 years. Who can be sure. Where I do some consulting, they still use 12 dBASE IV applications. These are absolutely required, but there is no employee time to work with developers to re-create them in a modern environment or funding.
0 Votes
+ -
Time to wake up.
Lester Young 12th Nov 2010
Seriously, the writing's been on the wall for years. The signs that IE6 and old Win32 technology are dying should have been too obvious to ignore. Hack developers and parsimonious IT managers have been hoping that the world will stop for them if they dig their heels in hard enough. Now the bills are falling due. They have nobody but themselves to blame.
@Lester Young:

"...parsimonious IT managers..."

I take it you've never had to fight for a budget before. Welcome to the rest of the world. Better yet, what's your planet like? I'm asking because it'd be nice to be able to get whatever I want for my org, y'know?
0 Votes
+ -
My point exactly.
Lester Young 14th Nov 2010
@Random_Walk

The can gets kicked down the road until the problem becomes a looming crisis. It's a management problem as much as a technical or financial one. Good management has foresight.
0 Votes
+ -
This is reality
Alon Yaffe 12th Nov 2010
The legacy applications we (InstallFree) are helping our customers migrate to Windows 7 are usually very complicated. They include stuff like Siebel CRM client, complex insurance claims applications, ERP clients, etc. It is true that the right long-term solution is to modernize the applications but these projects tend to cost millions of dollars and stretch over many, many years. The last thing these enterprise customers want is to create a dependency between their Windows 7 migration and their application modernization efforts. The solution we provide gives our customers enough breathing room to finish their migration, and does it at a fraction of the cost of alternative approaches.
Hopefully companies planning on developing applications with Silverlight will be smart enough to see the parallels.
@curph: As much as I agree with you, sadly, there are too many IT decision-makers who have adopted Microsoft's product line as a crutch to replace critical thinking.
Companies should stop listening to Gartner, Im sure Gartner had the opposite opinion 9 years ago. The companies that built or bought apps tied to IE6 might as well have built on DOS.

Unfortunately a lot of this garbage was not built in house, or if it was those IT shops are long since gone. Some vendors charged millions to build this junk. And they will charge millions to migrate it.

Corporate america is a bunch of fools for doing this to themselves and thats why selling them software (or down the river) is such a great business model. Just ask microsoft. In an ideal world corporations would not buy software, they would lease it. Then we wouldnt have to hear them constantly whine about shooting themselves in the foot.
0 Votes
+ -
Solution
itpro_z 12th Nov 2010
OK, I just don't see this as all that hard.

1) Microsoft (or someone else for that matter) could build an IE6 mode into IE9, either as a "Compatibility Mode" or as an Addon.

2) If Microsoft does not do it, then one of the other browser companies could offer an alternative. Opera, for example, could cook up an IE6 compatible browser and offer it for sale. Those companies desperate for a solution would be willing to pay for a modern browser that would run their legacy apps.

Why does this have to be so hard?
@itpro_z It would make too much sense to do that so obviously why would anyone want to do it then.
@itpro_z MS wants people to stop coding against IE6, adding IE6 compatibility to IE9 would twart that desire, and mean IE6 ways would live on for the life of Windows 7 and IE9, which nobody wants. Also it'd be another layer of standards to maintain, test against, patch, etc. It's better to make a clean break and go with HTML5.
0 Votes
+ -
Why don't . . .
JLHenry 13th Nov 2010
@itpro_z

You do it and offer it (for sale) to whomever wants it?

Main reason it doesn't exist is MS itself wants it to die. Even MS is moving to a web standard compliant browser. Granted they had to be dragged kicking and screaming to the table, but even they finally saw the light.

By promoting and continuing the IE6 trash dump, All these companies are doing is resigning themselves to historical oblivion. What they've done is ensure that their apps can't be used:

1) By anyone with a smartphone or tablet.

2) By anyone who doesn't have an older MS based machine (Mainly Mac, but Ubuntu and others are growing - not much, but they are growing in market share). And has anyone determined whether or not IE6 will even RUN in W7?

These companies decided to be lazy and write to SPECIFIC browser, and ignore the direction that tech is moving. Either they clean up their OWN mess, or they die.

It's as simple as that.
@itpro_z: Why should they? Microsoft considers the whole migration pain they caused as a profit driver for them.
0 Votes
+ -
IE 8 has a compatibility mode...
condelirios 15th Nov 2010
@itpro_z I have migrated several thousand apps to work with IE8 and it is really no effort. 99.9% of them work unchanged in IE8 compatibility mode. Kinda lost as to what all the fuss is about. I am talking about major enterprise web apps. The problem apps are those that were written for Microsoft Java and not the standard Sun Java. Those are difficult to migrate because Java is a pathetic excuse for a programming language and makes COBOL look modern. If we could outlaw all Java (not javascript...just Java) then we could speed up this process.
0 Votes
+ -
Nah, this isn't accurate...
Peter Perry 13th Nov 2010
IE 7 and 8 just shut some things off by default... If you turn those back on via Policy, it just works!

We have been through this at work already.
@Peter Perry
#1- IE7 was a POS. That is why you don't see it on any stats. Nobody is using it.
#2- Only people without a clue think that there is a working backwards compatibility feature in IE8. The feature you talk about is nothing but a "auto-fix bad HTML" feature. It does not provide any backwards compatibility with IE6 tech.
0 Votes
+ -
IE 8 compatibility mode works great...
condelirios 15th Nov 2010
@wackoae But there is no backward compatibility to Microsoft Java... which is a bigger issue.
0 Votes
+ -
Try a bullet diet
Rick_R Updated - 13th Nov 2010
"Any business customers out there have other options theyre considering or implementing to wean your organization from IE 6?"

Yeah -- the "bullet diet".

Sometimes ya just gotta bite the bullet!

Hey, imagine what would have happened in 2000 if all the companies worldwide had said, "We can't update our hardware and software to be Y2K compliant! ... We're tied in to existing equipment and it would be too expensive to upgrade!"

Same problem ... same thing the U.S. is now seeing with our 1950's-era interstate highway and power grid systems ... infrastructure just doesn't last forever. There is a ridiculous mentality in this country that once something is installed it should last forever or until it is convenient to upgrade. The computer industry became aware of the Y2K problem in 1970 when financial software handling calculations for 30-year U.S. Treasury Bills crashed. Instead of dealing with the problem over time, everyone just ignored it until it became critical.

The alternative to "bullet diet" is "bullet-riddled shoes" ... from "shooting yourself in the foot" repeatedly.
Think about it for a moment. Internet Explorer was supposed to be a browser. That's an application to render content and behavior based on Web standards. How comes we should have such a hard time migrating to another browser?

Incredible.
0 Votes
+ -
An internet browser is not a platform
daniel.pereznet Updated - 14th Nov 2010
Any application, especially one involving database access, can be implemented as a service running on a web server, such as Apache, with java server and client-end scripts or php-perl, and now html 4 elements. Some browser specific programming tasks can be simplified by standardizing on one internet browser. While tempting, this can prove to create daunting unsurmountable obstacles later.

For Application Development, an Internet Browser is not a platform. As UI, it can be "copied", but is not a good idea make it a requirement. A custom multi-document "browser-like" application that looks like an internet browser, can be built to serve as the UI.

Starting from a well-est. code base is good. Like C, C++. Especially, where there is an organization with a vast, stable, debugged API and is contractually obligated to support. Then you have a platform for Application Development.

Then main problem here is that by choosing IE6, many also choose specific Microsoft inventions that were "never" going to be outdated or unsupported. Now these various IE6 apps must be completely redesigned and core code base must be re-implemented along with a completely new UI. Good grief!

Even the API that IE6 was based on is now gone. Many systems running these applications cannot be patched to SP3, without some ramifications to consider.

This speaks volumes about how much has changed.
When moving from design to implementation, it is better to think along terms of cross-platform industry standards. No, Microsoft specific stuff does not count. May have thought so, but they were wrong and are now learning the hard way.

Even cross-platform languages have their life-cycle, if an application was written in 2001 for the java jre of that time, the many iterations and releases of new java jre since would have forced a serious re-write of key elements of code many times.

By using an industry standard code base ( like C++) and sticking to API provided by Microsoft or Apple, then design and implementation can be done with relative ease. Some re-write is inevitable. Technology moves fast. New standards are yet in the works.

Just keep one thing in mind, no matter how prevalent an Internet Browser (whether IE or Firefox or Safari or Opera or any other) should never be considered a platform for application development.

Even on smart-phones and tablets, whether Apples or Android or Blackberry, a platform specific API is provided. The internet browser on these devices serves it own purpose, and is not used as the sole UI for any of the applications installed on them.
@daniel.pereznet Dont use Java. Anything else will do.
0 Votes
+ -
agree
dcdavy 15th Nov 2010
@daniel.pereznet

the problem is that people tend to travel the easiest path at the moment. I guess a bunch of ActiveX controls looked as a kind of shortcut and a money saver back then. When you are an IT person who has to justify costs to people who got no clue about IT, then you realize how the corporate world works.
0 Votes
+ -
RE: Gartner: Existing options for migrating from IE 6 are too pricey, risky
makrekdw73-24353635615163652143356448933213 Updated - 10th Nov
Fortunate enough we all identified , this phenomenal webpage, nflshop often makes distinct toward bookmark this item so i cheap Clay Matthews Jerseys can arise that will help in generacheap Aaron Rodgers Jerseys l.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix