The Cisco Umbrella roaming client can be deployed using RMM tools, such as Kaseya, by applying the correct deployment parameters as part of the install string.
Note: This document is specific to deploying the Umbrella roaming client on Windows client operating systems; for example, Windows 8 or 10. Cisco does 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.
You must enter all customer internal domains before deploying the Umbrella roaming client. Failure to do so will cause problems with accessing internal resources. To do this, in the Umbrella dashboard, navigate to Deployments > Configuration > Internal Domains and enter domains as required. For more information, see Appendix D – Internal Domains.
- Download the Umbrella roaming client script Umbrella_Roaming_Client.xml.
- In GitHub, click Raw.
- Copy and paste the displayed XML into your favorite text editor and save as an XML file.
- Import XML into Kaseya:
a. In Kaseya, navigate to Agent Procedures > Manage Procedures > Schedule / Create.
b. Select a folder in which to import the script, and then click Import Folder/Procedure.
c. Choose the file to upload, and click Save.
You should see the newly imported script in the selected folder.
When running the script, you are prompted to enter the parameters from in the Umbrella for MSP console. See step 7.
You have the option to hide the Add/Remove Programs entry and the System Tray icon by filling in the appropriate value.
- In the MSP console, navigate to Customer Management, expand a customer, and scroll to Deployment Parameters.
Umbrella lists the organization's Org ID, Fingerprint and User ID parameters as well as Umbrella's deployment script.
- In the MSP console, navigate to Customer Management, and click View 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 2 years ago