PolicyPak Browser Router removes other Chrome ‘force installed’ extensions. How can I work around this?

Here’s what’s happening:

  • PolicyPak Browser Router installs the PPBR forced extension plug in on the COMPUTER side at installation time.
  • When you use PolicyPak Application Settings Manager or Chrome’s ADMS to specifically dictate plugins PER-USER,
  • When there’s a conflict, Google doesn’t MERGE, it just uses COMPUTER.

RESULT: You only see PolicyPak Browser Router’s extension and NOT your desired user-side extensions for Chrome..

Workaround:

PolicyPak Provides ADMX settings to work around various items in PolicyPak On-Prem.

See this video to implement the ADMX:

http://www.policypak.com/video/policypak-troubleshooting-with-admx-files.html

Then, the policy setting which must be applied to the computer side which is called

PREVENT COMPUTER SIDED INSTALLATION OF CHROME EXTENSION

policypak-browser-router-removes-other-chrome-force-installed-extensions-how-can-i-work-around-this-0

Then… Using Chrome’s own ADMX setting named “Configure the list of force-installed apps and extensions” (seen below) to manually add the PolicyPak Browser Router using Chrome’s ADMX setting on USER or COMPUTER side.

policypak-browser-router-removes-other-chrome-force-installed-extensions-how-can-i-work-around-this-1

Use this string:

jdadlnndcplobhfcdfcfobnecakhmkhd;https://clients2.google.com/service/update2/crx

Which will manually install the PolicyPak Browser Router Chrome Extension. Or using PolicyPak Application Settings Manager and our Chrome Pak, you can use this field (user or computer side.)

policypak-browser-router-removes-other-chrome-force-installed-extensions-how-can-i-work-around-this-2

Use the same string:

jdadlnndcplobhfcdfcfobnecakhmkhd;https://clients2.google.com/service/update2/crx

Which will manually install the PolicyPak Browser Router Chrome Extension alongside the optional extensions you wish for Chrome.

Back