The following is an overview of how to deploy the Cisco Umbrella roaming client using your RMM tool. Cisco does not provide comprehensive support for Continuum. For more information about Continuum, see Continuum documentation.
Note: This document is specific to deploying the Umbrella roaming client on Windows client operating systems; for example, Windows 8 or 10. We do not support the installation of the Umbrella roaming client on Windows Server operating systems. For more information about prerequisites, see Prerequisites. This document assumes you've read these prerequisites 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 instructions to configure a template to deploy the Umbrella 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% Umbrella Client Deployment. This allows for easy deployment to future customers and allows for the scheduling of installations.
You must enter all customer internal domains before deploying the Umbrella roaming client. Failure to do so results in problems with accessing internal resources. In the Umbrella dashboard, navigate to Deployments > Configuration > Internal Domains and enter domains as required. For more information, see Appendix D – Internal Domains.
- Search or browse to the option Create own application.
- Select Create own application and then click Create a Script From This Template.
- In the MSP console, navigate to Customer Management, expand a customer, and scroll to the Deployment Parameters section, expand Show install command and copy the Deployment Parameters string beginning with
The install string uses three parameters to register the roaming client to the correct Umbrella dashboard: ORG_ID, FINGERPRINT, and USER_ID. For more information, see Umbrella Roaming Client Deployment Parameters for Mass Deployment (MSP).
Note: The msiexec /i Setup.msi portion of the install string is not necessary, and will cause the script to fail.
- Update the following:
- Script Name—%Customer Name% Umbrella Roaming Client Deployment
- Description—Installation script for the Umbrella Roaming Client for %Customer Name%
Note: This URL does not work in a browser unless you apend
Setup.msito the end of the URL. The file name is case sensitive.
- Type of Application—MSI Package
- Package/Exe name—Setup.msi (Note that this is case-sensitive.)
- Installation Parameter—Deployment parameters copied in step 4
Note: If you want a visible installation, you can change the HIDE_UI and HIDE_ARP to 0 instead of 1. For more information, see Umbrella Roaming Client Deployment Parameters for Mass Deployment (MSP).
- MD5 Checksum—Leave this blank.
- Install under user account—Leave this unchecked.
- Execution Mode—Set to Install.
- Click Update or Save.
You are returned to your list of partner applications.
Create a job using this template to deploy the Umbrella roaming client. We recommend 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 and then, click Add Job.
- Set the Job Name (1).
- Click the radio button next to Script (2).
- Click 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.
- Optionally, configure email alerts from Continuum with summary information about the Job you have scheduled.
- Choose 'Sites,' 'Desktops' and the location you are deploying to.
- Choose the scheduled time to run the script, or execute immediately.
- In the MSP console, navigate to Customer Management, and click a customer name to open the Umbrella dashboard.
- Navigate to Deployments > Core Identities > Roaming Computers
- 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.
Updated about a year ago