Chrome Extension Roaming Client Deployment Guide

Article author
Joshua Lamb
  • Updated

The Google Chrome Extension Roaming Client is a browser based endpoint agent that provides device specific and granular reporting and filtering. It is primarily used by managed Chromebooks to disallow any circumvention of software.

Roaming Client Chrome Extension Notice

Our Chrome extension is tested with G Suite deployments but could be deployed with other MDM platforms. We intend to document additional deployment options in the near future.

Benefits of Using the Roaming Client Chrome Extension

  • MDM Deployment - The Chrome extension can be deployed using common Chromebook-compatible MDM's to easily get filtering and protection started.
  • Granular Reporting - Per device filtering and reporting is possible with the Chrome extension, allowing administrators to view which device made what request, and more.
  • Roaming - Like our other Roaming clients, the Chrome extension allows off-network filtering. No matter which network the device is connected to, filtering will always remain active.
  • Tagging - Using the tagging feature, you can easily change policies for large groups of computers. Use cases include: teachers/students, corporate departments, public/private computers, etc.


The Google Chrome extension is primarily designed for Managed Chromebooks so to reliably avoid circumvention, if a device is not managed by an MDM the end-user can easily remove the extension.

Chrome Extension Roaming Client Installation & Deployment

Pre-deployment Note: In order to avoid a list of enrolled devices called "[blank]" in your DNSFilter Dashboard, it is important to ensure that you have set the Device Network Hostname Template for your enrolled devices.

Google provides a guide on how to set this here.

This ensures that the appropriate device name is sent along with the client registration and allows you to get accurate information for each of your clients.

We'll be using the Google Admin Dashboard for this example, but note that other MDM's are similar in setting up the extension.

  1. Login to and Navigate to Devices > Chrome Management > Apps & Extensions
  2. Select the OU of users you wish to deploy the DNSFilter Chrome Extension to.

    1. Click the + Button and select "Add Chrome Extension by ID".
    2. Select "From Custom URL" and enter the following:
      Extension ID: ahailcbfmbjeilfjapehbjlclkeffojh
      Custom URL:
  1. Click Save.
  2. Select the Installation Policy and set it to "Force Install".


  3. With the extension selected, enter the following JSON in the "Policy for Extensions" field (replace contents with your site key.
  4. Click Save.

When a User in that OU logs into a Chromebook, the extension will force-install and register with the site.


  • Yandex SafeSearch - When you enable SafeSearch on Yandex the search function will be blocked as it’s not possible to enforce filtered searches on the Yandex search engine through the Chrome extension.

Version Log

You can find the history of the Chrome Browser Roaming Client release notes on our public changelog.

Was this article helpful?

1 out of 9 found this helpful

Have more questions? Submit a request



Article is closed for comments.