In this article
Roaming Client Chrome Extension Notice
For complete functionality, this Chrome extension must be deployed to managed G Suite users using Chromebooks. A managed G Suite domain and access to the Google Admin Dashboard is required.
This guide is for troubleshooting any issues associated with the Chrome extension Roaming Client.
Troubleshooting steps
- Open the Extensions page by clicking the ellipsis More Tools > Extensions
- Enable Developer Mode by clicking the toggle in the top-right corner
- Next, click on** Background page **on the DNSFilter Chrome Extension card
- The Chrome debugger will open, select the Console tab and take a screenshot
- Send the screenshot to our Support team to review. Include any other relevant information in the ticket
[blank] device name in the dashboard
DNSFilter updated our Chrome Extension Roaming Client in March 2024 to no longer send information from unmanaged machines to the DNSFilter dashboard. Previously these unmanaged requests would register on the dashboard as [blank] devices.
There are a few reasons why devices are named [blank] in the DNSFilter dashboard:
-
The device is not provisioned
-
The hostname template is not set. This can be done by following Google’s guide:
Supported on Chrome version 65 and later
Allows you to specify the host name that is passed to the DHCP server with DHCP requests.
If this policy is set to a nonempty string, that string will be used as the device host name during the DHCP request.
The string can contain the ${ASSET_ID}, ${SERIAL_NUM}, and ${MAC_ADDR} variables. These variables will be replaced with values found on the device. The resulting substitution should be a valid host name per RFC 1035, section 3.1.
If this policy is not set or if the value after substitution is not a valid host name, no host name will be used in the DHCP request.
Comments
0 comments
Please sign in to leave a comment.