Legacy Browser Support

1) Legacy Browser Support

This article is intended for IT administrators with Chrome users on corporate-managed Windows computers.

Legacy Browser Support icon

If your organization wants to take advantage of the Chrome browser, but your users still need to access older websites and apps that require Internet Explorer, you can use this feature to easily switch between browsers. The Chrome Legacy Browser Support extension allows users to switch automatically between Chrome and another browser. When your user clicks a link that requires a legacy browser to open (such as a site that requires ActiveX), the URL will automatically open in the legacy browser from Chrome. You can specify which URLs to launch into a second browser and deploy this Chrome policy for the organization. Legacy Browser Support (LBS) requires Chrome 31 or higher.

Additionally, install an Internet Explorer Legacy Browser Support add-on for your users. This will open links your users click on in IE that don't depend on legacy software in Chrome. With this Internet Explorer add-on installed, Chrome and IE will switch to the best browser, depending on which website or app is being accessed.

Updates for March, 2014: Step 3 is no longer optional. You need to install the IE add-on for Legacy Browser Support to work correctly. And you need to update to Chrome 31 or higher for Legacy Browser Support to work as intended.

You can alternatively set Internet Explorer as your default browser and Chrome as your secondary browser. For instructions on how to set up this configuration, see Step 4.

Step 1: Create a Chrome test group (optional)

Test Legacy Browser Support first with an early adopter group if you have users who aren’t familiar with Chrome (recommended for most large organizations).

  1. Inventory the applications and websites your users use in a legacy browser (such as those relying on ActiveX or Silverlight) to determine which websites and web apps need to be whitelisted for the older browser.

  2. Create a homepage for IE that showcases the websites your users can access using IE.

  3. Whitelist this IE homepage and other sites that require Internet Explorer to run in your Group Policy Editor on your domain controller.

Optional: For Chrome, you can create a new tab page featuring private Chrome bookmark apps that you make to launch the legacy websites and apps your users need in IE.