Control D can be setup by the end user quickly and easily.

Have dozens of hundreds of end-users and wish to deploy Control D on all their individual devices? We can already sense how NOT excited you are about doing this. Don't be sad, this is going to be surprisingly painless.


Admin Rights Required

To use this onboarding method, the end user must have admin rights on their machine. If they do not, please see Org: Mass Provisioning flow.

Create Device

When you create a Device, a unique set of DNS resolvers is issued for that Device. If you are the end-user, you can simply click "Help me configure this" button, which will kick off a setup tutorial for the chosen platform.

Get Link

If you are NOT the end user of the Device you just created, or simply want to set it up on a device that isn't logged in into the web control panel, click the Copy setup link button and send it to the end user (or yourself) via any method you want.


The end user clicks the link and follows the same setup process you would if you clicked the "Help me configure this" button, using step by step tutorials .They do not have to be logged in (or be a Control D user) to use the self-provisioning link.

Confirm End User Setup

When you view a list of your Devices, you will see them in one of two states:

  • Pending - A big purple button will be shown
  • Active - No purple button will be shown

Once a device flips from pending to active, that means the end user successfully configured the Device. The little gray orb next the the device icon will turn green when the Device is currently active (resolved something in the last 5 minutes) - only if you enable Analytics on the Device.

Mass Create Devices


Organizations Only

An Organization account is required to use this feature.

Too tedious to create hundreds of devices manually? No problem, simply use the Org: Add Multiple Devices flow. Once you do this, the following will happen:

  1. For each email, a device will be created with the username as the device name (ie. [email protected] -> bob-smith will be the device name)
  2. The end user will be sent an email with a setup link for them to self-provision.

If you have total control over the end-user devices (Group Policy or RMM), you can use the Command Line Daemon to do scripted deployments. See Org: Mass Provisioning for more details.