Introduction
This document describes how to stage access for Cisco Umbrella Roaming Client updates.
Overview
Cisco Umbrella's roaming client has a feature that allows you to put roaming client devices on the "stage" track (otherwise known as a "beta" or "pre-release" track) in advance of mainline releases.
Where possible, Umbrella encourages you to have two orgs: one for standard production, and one for acceptance testing and beta testing new features.
The "stage control" enables you to have two "tracks" for a subset of machines to encourage quicker adoption of the new releases after passing your internal QA/acceptance testing.
Methodology
The official method to do internal testing of client updates is to have certain devices on Umbrella's staging track. You can do this for some devices in your org, or create a separate org for testing.
First, and most importantly, subscribe to updates on Umbrella's release notes page on the Cisco Community. Umbrella posts all roaming client release notes there as soon as they hit the "stage" track. This lets you know when a new version is available for testing to machines on the stage track.
If you observe any incompatibility issues or regressions while the build is in staging, Umbrella can prioritize investigating it and can usually halt the release process until such time that the issue can be addressed.
To learn more about early updates and automated beta testing, see this knowledge base article.
If you need exact instructions, require help with any questions, or need more information, please contact Cisco Umbrella Support.
Feedback