PPBR: Troubleshooting routing between browsers.

This guide will help you troubleshoot problems routing from browser to browser. For instance, if you are inside Internet Explorer and expect Firefox or Chrome to automatically be opened, but it doesn’t, then this is the guide for you.

1. This troubleshooting guide assumes you have already performed the steps in this initial troubleshooting guide: http://www.policypak.com/support-sharing/browser-router-troubleshooting.html . This will demonstrate that you are:

  1. Getting the GPOs involved in PolicyPak Browser Router and
  2. Licensing is working for PolicyPak Browser Router
  3. PolicyPak Browser Router is set as the OS Default Browser for HTTP and HTTPS
  4. Routes are being created in ppBRResults.xml file in the user’s AppData.

If you haven’t pre-confirmed ALL of these aforementioned steps, then STOP.

ONLY continue if you see ppBRResults.xml and are sure PolicyPak Browser Router is correctly licensed.

2. First, test the PolicyPak Browser Router is routing “natural” links. Use WORDPAD (not notepad!) to create a simple document which will open up the browser based upon your rules (routes.)

img1

Does clicking on each link open the correct expected browser?

YES: Continue onward.

No: Stop, and update your GPO / routes / rules until you get the expected result.

3. Browser Router installs extensions inside of:

  • Internet Explorer
  • Firefox
  • Chrome

As of this writing (Feb, 2016) there is no support for routing Edge –> Other browsers EXCEPT to Internet Explorer.

Those helper applications will only install when:

  • The browser has already been opened before (this creates a profile for the browser inside the user’s profile)
  • The user has logged in after this or GPupdate has run

Therefore, if you have a brand new user profile, and FF, IE and Chrome have never ever been launched before, then PolicyPak Browser Router will not work immediately.

Again, the browser needs to be:

  • Launched and its first-time wizard complete
  • Closed
  • THEN running GPupdate (or logoff and back on)

…will install the PolicyPak Browser Router helper applications inside each browser on the endpoint.

So, some examples where PolicyPak Browser Router will not work instantly:

img2
img3

To ensure each browser is ready to route BETWEEN BROWSERS, you are looking for the following.

Inside IE: (Gear | Manage Add-ons)

img4

FF: Firefox doesn’t have a direct way to see that our helper app is installed. The way to verify that the helper application is installed would be to:

  1. Find the ppBRAgent.log inside \Users\{username}\AppData\Local\PolicyPak\PolicyPak Browser Router\
  2. Close Firefox.
  3. Delete the ppBRagent.log file.
  4. Run Filrefox.
  5. Go to any website at all.

Did the log ppBRAgent.log get re-generated and are there lines at the top like this demonstrating that Firefox is the “input source”? If yes, then the Firefox helper app is correctly installed.

img5

Chrome: (Gear | Extensions)

Chrome’s helper app is automatically installed over the Internet. So if routing from Chrome  Another Browser is not functioning, you need to ensure you have Internet connectivity (at least one time) to get the PolicyPak Browser Router Chrome Extension automatically downloaded and installed on your machine.

img6

If you don’t see the Extension listed, try:

  1. Closing Chrome.
  2. Verifying Internet connectivity.
  3. Try installing any Chrome extension manually (not outs, just one thru the webstore): https://chrome.google.com/webstore/category/extensions?hl=en-US
  4. Again; make sure you have SOME PolicyPak Browser Router policies.
  5. Run GPupdate /force
  6. Did our Chrome extension appear?

Back