Contents

Introduction

Overview

Deleting Umbrella roaming clients from the dashboard when the software is installed locally

The Umbrella roaming client reappears in the Umbrella dashboard with a new registration

Introduction

This document describes how to delete an Umbrella roaming client from the Umbrella dashboard.

Overview

The procedure to use to remove a Cisco Umbrella roaming client from the dashboard depends on the scenario:

- Broken State—If the Umbrella roaming client is showing as being in a broken state, an offline state, or missing from the dashboard, re-install the Umbrella roaming client using a new download from the Umbrella dashboard. For the Windows OS, it must be uninstalled before reinstalling. This ensures that the Umbrella roaming client does not accidentally lose policy or interrupt the user.

- Remove Entirely—To remove the Umbrella roaming client from a computer, uninstall the Umbrella roaming client first.  When uninstalled, in the Umbrella dashboard, remove the Umbrella roaming client from the list by clicking the red X. Instructions to uninstall the Umbrella roaming client are here: https://www.cisco.com/c/en/us/support/docs/security/umbrella/224712-uninstall-the-umbrella-roaming-client.html

Deleting Umbrella roaming clients from the dashboard when the software is installed locally

When an Umbrella roaming client is still installed on a local machine and operating as normal, we do not recommend that you delete it from the Umbrella dashboard until after it has been removed from workstations. If you delete the Umbrella roaming client from the dashboard when that same Umbrella roaming client attempts to sync with our API it no longer has a policy or registration to sync with.

Windows clients automatically re-register at the next reboot of the machine or start of the service. Mac clients do the same beginning in our next release as of May 2019.

As a result:

- Data from the Umbrella roaming client is no longer synced with our API and logging does not occur

- Internal domains list contents continue to sync and apply. Internal domains access are persisted and maintained.

- Roaming client device policy is no longer applied and any destination lists or security blocks are no longer applied; effectively, the Umbrella roaming client acts as a plain encrypted DNS forwarder to 208.67.222.222.

The Umbrella roaming client reappears in the Umbrella dashboard with a new registration

Beginning with Windows 2.2.109 and Mac 2.1.29, roaming clients re-register automatically when deleted from the dashboard while the service is still installed. This occurs at the next restart of the service (most commonly a device reboot).

To verify if a machine is in a state where it was deleted from the dashboard, but before re-registration (note, verification would require the machine to be on an IP that is not registered to the dashboard), run the command:

nslookup -type=txt debug.opendns.com

In the results if the field "originid" is set to 0 is present, the Umbrella roaming client has been deleted from the dashboard (or is not in the dashboard in some other way). An example return from an Umbrella roaming client that has been deleted in the dashboard would be:

debug.opendns.com. 0 IN TXT "device 0101C3539CB8D7C8"

debug.opendns.com. 0 IN TXT "originid 0"