Legacy Browser Support for Windows
1) Legacy Browser Support
This article is intended for IT administrators with Chrome users on corporate-managed Windows computers.
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. You can also use your organization’s existing Internet Explorer site list to control whether URLs open in Chrome itself or Internet Explorer. If you do both, then the URLs you specify in the policy take precedence over the Internet Explorer site list. Use Legacy Browser Support (LBS) with the latest stable release of Chrome.
Additionally, install the Legacy Browser Support - native host add-on for your users. Without this package the Extension will not be able to open the alternative browser. LBS will open links your users click on in IE that don't depend on legacy software in Chrome. With this native host add-on installed, Chrome and IE will switch to the best browser, depending on which website or app is being accessed.
This add-on works with Internet Explorer 6, 7, 8, 9, 10, and 11. Note that Enhanced Protected Mode in Windows needs to be off for LBS to work.
- You need to install the native host application in order for Legacy Browser Support to work correctly. Previously, this add-on was optional, but is now required in LBS v3.0+.
- To test new versions of Legacy Browser Support before they're released to the stable channel, you can set up test machines on the LBS test channel.
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 3.
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).
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.
Create a homepage for IE that showcases the websites your users can access using IE.
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.