Here’s what’s happening:
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:
NOTE: You shouldn't need to perform these steps (any of them) if you want to dictate Chrome "forced installed" extensions on the COMPUTER side. On the COMPUTER side... when you force install extensions, PolicyPak Browser knows what to do and just adds in the correct Chrome Extension. This KB is only required if you are opting to dictate Chrome "forced installed" extensions on the USER side.
Then, the policy setting which must be applied to the computer side which is called PREVENT COMPUTER SIDED INSTALLATION OF CHROME EXTENSION
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.
Use this string found in this article:
For instance, an example string might look like …
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.)
Use the same string:
Which will manually install the PolicyPak Browser Router Chrome Extension alongside the optional extensions you wish for Chrome.
Again, the example extension ID above is just an example. Please use the correct one based upon your CSE.