How do I revert to "Legacy Browser Router Method & Features" if directed?
If you are having a problem with Netwrix Endpoint Policy Manager (formerly PolicyPak) Browser Router (PPBR) not working as expected, you may be asked by tech support to "Revert to Legacy Browser Router Method & Features".
First, be sure you are eligible to use this function by copying the latest Endpoint Policy Manager
ADMX files to your Central Store or using Endpoint Policy Manager Cloud.
Directions for Central Store: Troubleshooting with ADMX files
Directions for Endpoint Policy Manager Cloud (if they are not already pre-placed there):Endpoint Policy ManagerCloud: Upload and use your own ADMX files to Endpoint Policy Manager Cloud
Then, the setting you should use if directed by support is entitled:
Computer Configuration | Policies | Admin Templates | Endpoint Policy Manager ADMX Settings | Client-side Extensions | Browser Router | Revert to Legacy Browser Router Method & Features and set to enabled to return back to the legacy behavior.
What does "Revert to Legacy Browser Router Method & Features" mean?
As the product evolved, Browser Router changed what it did to make it better, faster. When interacting with some third-party software, Browser Router is prevented from performing some of its tasks that relied on the new method.
By establishing to use Legacy Browser Router Method & Features, Browser Router is returned to its original methods. What this essentially means is:
- Instead of immediate application of Browser Router settings, a re-login will be required.
- Browser Router will not route from external third-party applications (Skype, Slack, etc.) on non-domain joined devices without interaction. In Legacy mode, the user must set the Endpoint Policy Manager Browser Router agent as the default browser manually – e.g. If a browser such as Chrome and Firefox are set as default, the default cannot be updated VIA policy)
An example of the user required to manually specify Endpoint Policy Manager Browser Router can be seen here.
