Get off of Internet Explore version 6. Now.
However, in reality, the move is easier said than done. Here’s what I said in this research note on planning for and deploying the security features of Windows 7:
The most significant change in IE8 is not security-related — the new rendering engine is more standards-compliant. This introduces significant Web-based application compatibility issues for applications written to specific idiosyncrasies of IE6 (see “IE6 Apps Are Windows XP Apps, So Treat Them That Way in Migration Planning”). Although Microsoft includes IE5 and IE7 back-level rendering support, an IE6 rendering mode is not supported.
Some of your own in-house developed applications that use IE6-specific features will create problems during migration. But clients are telling us that some of their large enterprise application ISVs are the bigger problem. Some don’t officially support IE8 yet. Worse, some of the ISVs won’t support a newer browser unless you pay them money to upgrade to a newer version of their software. Issues with Cognos, Siebel and Peoplesoft are commonly called out as trouble areas in this regard.
Advice going forward: Make any web-enabled application vendor support multiple web-browsers and adhere to widely accepted rendering standards so that the chance of getting ‘locked in’ to a specific browser and version are minimized. Minimize the use of custom browser plug-ins to extend functionality (and that will hamper future migrations).
I don’t want us to have to go through this again when IE9 (or Firefox 4 for that matter) comes out.
Read Complimentary Relevant Research
Top Strategic Predictions for 2019 and Beyond: Practicality Exists Within Instability
Technology-based change is happening continuously, and most organizations struggle to see the change in advance. Continuous change can...
View Relevant Webinars
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.