Skip to content

Latest commit

 

History

History
 
 

Continuum

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

###Deploying OpenDNS Umbrella Roaming Client with Continuum

This guide is meant to be a basic overview of deploying the OpenDNS Umbrella Roaming Client using your RMM tool. OpenDNS is not able to provide comprehensive support for Continuum, but there is further documentation available related to Scripts in Continuum.

NOTE: This document is specific to deploying the OpenDNS Roaming Client on Windows client operating systems, such as Windows 8 or 10. OpenDNS does not support the installation of the Roaming Client on Windows Server operating systems. A complete list of prerequisites are available here. This document assumes you've read these prerequisistes and have opened the appropriate firewall ports

Continuum provides the ability to create script templates to deploy products that are not built-in to Continuum’s RMM tool. This document provides the instructions to configure a template to deploy the OpenDNS Roaming Client to your customer's computers. We recommend creating a deployment script for each individual customer with a naming convention such as %Client Name% OpenDNS Client Deployment. This will allow easy deployment to customers in the future and allow scheduling of installs.
Please note that all customer Internal Domains must be entered first before deploying the Roaming Client. Failure to do so will cause problems with accessing internal resources. This is done in the Dashboard by navigating to Configuration > System Settings > Internal Domains. For details about what needs to be in this list, please see this support article.

Once logged into your Continuum Portal, you will see the top navigation menu where you will select “Scripts” as shown below. On the left navigation column, click on “Essentials” and then choose “Templates” as shown in the image below.

Scripts -> Manage Scripts

Once in the Template section, you will need to search or browse to the option "Create own application." As shown below, click the radio button next to this option and then click the "Create a Script From This Template" button above.

Partner Application Installers

Here you can define your own installer which we’ll use to deploy the Umbrella Roaming Client. There is a specific install string that is required for the script to ensure that your roaming clients check in with the correct customer Dashboard.

You can find the install string in the OpenDNS MSP Console by expanding the Customer Management card and clicking "show install string" (circled below). Then, select the string beginning with ````/qn ORG_ID= ```` through the end.
Deployment Parameters

The install string uses three parameters to register the Roaming Client in the correct Dashboard. Those parameters are USER_ID, ORG_ID and ORG_FINGERPRINT (see screenshot above). Note that the msiexec /i Setup.msi portion of the install string is not necessary in Continuum, and will cause errors.

More detail about the parameters and their definitions can be found in this support article.


First, we’ll create the installer. To start, click “Create a Script From the Template.” You will see a screen similar to the one below:

New Application Installer Script

Make the following changes:

Script Name: %Customer Name% OpenDNS Roaming Client Deployment

Script Description: Installation script for the Umbrella Roaming Client for %Customer Name%

###“Download Details” Section Location:

http://shared.opendns.com/roaming/enterprise/release/win/production/

Note that this URL does not work in a browser unless you include the filename Setup.msiin the URL. This location tells Continuum where to look for the file, and below we'll be setting the filename. ###“Application Details” Section

Type of Application: MSI Package

Package/Exe name: Setup.msi (note this is case-sensitive)

Installation Parameter: Use string from Customer Management shown below

Deployment Parameters
NOTE: If you want a visible installation, you can change the HIDE_UI and HIDE_ARP to 0 instead of 1; more details about this and the other variables are available in this support article.

MD5 Checksum:

Leave this blank

Install under user account:

Leave this unchecked

Execution Mode:

Set this to Install

After you have completed the required section and any optional sections, click the Update or Save button to save the settings you have changed, and then you’ll be returned to your list of partner applications.


Now that you’ve created this script template, you can create a job using this template to deploy the Roaming Client. OpenDNS recommends testing your script on a single machine to verify it works as expected before deploying to a large group. In the Scripts Home, click Essentials > Jobs and Instances. Then, click Add Job. Set the "Job Name” (1). Click on the radio button next to "Script" (2). Click on the arrows (3) and start to type the name of the script you created in the "Filter" section then click on the script template you created, as in the image below:

Scripts -> Third Party Applications

You also have the option to receive an email alert from Continuum with summary information about the Job you have scheduled.

Scripts -> Third Party Applications

Use the drop down menus to choose 'Sites,' 'Desktops' and the location you are deploying to:

Install from Download Site

Then, choose the scheduled time to run the script, or execute immediately.

Script Parameters

To confirm the Roaming Client is checking in, log into your OpenDNS Dashboard and navigate to Configuration > Identities > Roaming Computers. Look for the customer where you ran the deployment script, and search for the individual host names where the script should have been run. If the computer is checking in properly, you’ll notice a green status icon as shown below:

Roaming Client in Dashboard

Computers without a green status icon are not checking in properly with OpenDNS. Please check this support article for more information on the status icons and troubleshooting.