As of October 20th, 2022 Cisco will no longer support script installation with static links to installers. These include the scripts Umbrella previously published for various Remote Monitoring and Management software. Going forward, Umbrella recommends other methods of initial distribution for the standalone Umbrella Roaming Client.
In the past, for ease of integration Cisco used to provide example scripts for various mass deployment tools which would automatically download the installer on Windows machines. To facilitate this, Cisco hosted a hardcoded link to a current installer. Cisco no longer believes hosting an installer at a static location is a best practice. As such, the following paths will be deactivated as of October 20th:
After October 20th, 2022, any scripts that still reference these locations will no longer function and will need to be discontinued or adjusted.
As a reminder, the standalone Umbrella Roaming Client automatically updates itself according to your release wave. The following should be only considered for original procurements.
Solution 1: Downloading current release ahead of distribution
The most straight forward alternative to is to download the current installer from our release notes and deploy it with your script. You can read more about this in our Mass Deployment KB.
Solution 2: Programmatically parse manifest
Some customers wish to automate releases further and choose to programmatically parse the following .json file for the current production installation filename:
You can then use this filename to download the latest production build using this URL format:
For Mac OSX, please adjust the URL to:
Umbrella Roaming Client Deployment Parameters for Mass Deployment (MSP)
Mass deployment best practices and common mistakes for Standalone Roaming Client