Eliminate Conflicts & Ease Migration - Virtualizing Internet Explorer
For many businesses, despite the number of alternatives available (Firefox, Chrome, Opera) Microsoft Internet Explorer (IE) is still the standard for browsers. The standard version of IE may vary from company to company, and even from computer to computer, depending on update frequency and application dependencies.
Though each upgraded version of IE is different than its predecessor, the basic building blocks that make IE a functional browser don't change; only features, design, and support do. Software applications (in-house, specialty, legacy, and client-server) at times may be dependent on specific versions of IE, making it difficult to upgrade to the latest Internet Explorer version included with a new OS.
The Internet Explorer dependency can impact both the company's ability to migrate to either the new Internet Explorer and the new Operating System if it does not support older versions of the browser or if for example XP Mode is not an option due to interoperability, hardware or other requirements from the user or application.
Increased mobility, employee owned PCs, extended enterprises with outsourcers/partners, and regulations for the smaller businesses requiring patching - has created out of band requirements for turning on Windows Update Service for those client PCs. IT has to struggle with balancing the patching requirements mandated to protect their infrastructure from Malware attacks and ensuring that the automatic updates do not automatically upgrade the end user to a service pack or upgrade that can cause compatibility issues with the legacy applications or browser environments.
One option for supporting legacy browser dependant applications while keeping your OS compliant with security mandates is to virtualize Internet Explorer and the dependant application components. Doing this isolates the browser from the underlying Operating System, specific middleware dependencies (Java, .Net), and other applications.
Once virtualized, the older version of IE can be associated with specific programs, or even specific URLs. The redirection is instantaneous; if an IE 6 specific URL or legacy program is accessed, the virtualized IE 6 will open based on policy set in InstallFree's management console and any other program or URL will open in the latest version of IE. Both versions of IE can run simultaneously, which both simplifies and enhances the user experience.
Other benefits realized from virtualizing internet explorer:
• Reduced Regression and User Acceptance Testing - Each update to IE requires extensive regression testing to ensure compatibility with all programs used. Running multiple versions of IE dramatically reduces the need for this, saving time and money.
• Optimize Application Lifecycle with Modular Components - In addition to requiring specific version of IE, applications may require certain versions of middleware, such as .NET and Java. Specific versions of these components can be isolated, encapsulated, and dynamically bound with the virtual or native IE depending on the application being used. This level of flexibility is paramount in providing a consistent user experience while saving time and money.
The building blocks of IE are what make it such a successful and widely used browser - those won't change. Running a stable, virtualized, older version for applications that depend on it side by side with the latest feature rich version is a benefit made possible through virtualization.
References:
http://www.emaildiscussions.com/showthread.php?t=25556
[ New service packs breaking critical dependiencies ]
http://www.microsoft.com/technet/security/Bulletin/MS09-061.mspx
http://www.microsoft.com/technet/security/Bulletin/ms09-052.mspx
[ Microsoft Knowledge Base Articles ]