Topic
This article explains how to use the Agent Updates feature in ControlOne to manage when and how agents receive version updates and override agent release channels for each device.
Environment
- Cytracom ControlOne
Description
With Agent Updates, you decide when and how your ControlOne agents get updated. You can choose to test new builds early, stay on the stable release, or stick with a long-term version that changes only when absolutely necessary.
Note: The minimum supported version is v2.7.1. Installed Agents running 2.7.0 or prior must be updated directly. Once upgraded to 2.7.1 or higher, they will be eligible for Automatic Upgrades. See Agent Upgrades for more information.
This feature gives you:
Flexibility: Pick the update track that fits your environment.
Visibility: See which version stream your agents are running (Beta, GA, or LTS).
Control: Manage upgrades safely with staged rollouts and clear version tracking.
How to manage Agent Updates
Accessing the Feature
Once logged into ControlOne portal, a banner appears at the bottom of the ControlOne portal.The banner introduces the feature and provides navigation shortcuts:
Here’s what each option does:
More Information : Explains what happens if no channel is selected (agents will automatically join the recommended one).
Read More: Opens this Knowledge Base article for full details.
View Setting: Takes you straight to Admin Settings → Agent Updates so you can make your selection.
Selecting an Agent Release Channel
In Admin Settings, you’ll now see an option labeled Agent Updates. From here, you can pick which update track your agents will follow. Once you save your selection, it immediately updates the target version for all agents in your tenant.
Release Channel options for your Agents
You'll see the following 3 options in the dropdown below that you can chose from
Channel |
What It Means for You |
Beta |
Get early access to new features or fixes before release. Best if you like to test updates first. |
General Availability (GA) |
The default stable channel. Fully validated, production-ready builds recommended for most environments. |
Long-Term Support (LTS) |
The slowest-moving channel. Updates are limited to critical or security fixes only; ideal for high-stability environments. |
How Agent Updates Work
Agents can update in two ways:
Manual updates: You can trigger updates anytime using Update All Agent Versions on the Devices page.This button reflects the version associated with the selected channel in the Admin -> Settings -> Agent Updates section.
Automatic updates: ControlOne automatically updates agents when certain conditions are met.
The default upgrade strategy is, agents auto-update:
When restarted, or
During your scheduled maintenance window
What You’ll Notice
When new versions become available:
The version number next to your agents will update according to the selected channel (e.g., Beta 2.8, GA 2.7, LTS 2.6).
The Devices will show which version your channel is tracking.
How Support Manages Rollouts and Exceptions
While you control which release channel your agents follow, our Support team also has tools on the backend to help ensure updates roll out safely and predictably. These configuration options are not exposed in the ControlOne UI at this time.
Per-Agent Overrides
If you’re working with Support on troubleshooting or testing a specific scenario, they can temporarily keep one or more agents on a specific version (for example, version 2.7.1) while the rest of your environment continues to follow the General Availability (GA) channel. This allows you to validate fixes or isolate issues without affecting production devices.
Paused Channels
In special cases, Support can place your entire tenant on a Paused channel. When this happens, automatic updates stop completely, giving you time to test, stabilize, or complete internal maintenance before resuming updates.
Gradual Rollouts
To reduce risk during major version releases, updates may be rolled out gradually over several days.
Support sets a start and end date and a defined percentage of agents are updated each day.
Here’s a typical rollout example:
Day 1: ≈ 25 % of agents updated
Day 2: ≈ 15–20 %
Days 3-5: Remaining agents updated gradually
If any issue is detected, the rollout can be paused or canceled immediately, so only a small portion of agents are affected.
What This Means for You
These backend controls are designed to protect your production environments and provide flexibility when you need special handling.If you ever want to coordinate a phased rollout or temporarily pause agent updates, just reach out to ControlOne Support, and they can adjust your settings accordingly.
Advanced Agent Settings - Release Channels Override
Overview
Change a client device’s release channel to control which updates it receives. Use this when you need to override the default release channel for a specific device.
Use Case: Apply a different update channel to a single client device.
Who Should Use This: MSP Administrators
How to Override a Device Release Channel
Step 1: Open the Admin section
Open the Admin section from the sidebar to access advanced network management settings.
Where to find it: Left sidebar navigation.
What you'll see: The Admin section view with advanced settings.
Step 2: Open Client Devices
Navigate to Client Devices to view and manage devices connected to your network.
Where to find it: Within the Admin section menu.
What you'll see: A list of client devices.
Step 3: Select the target device
Select the device you want to update.
Where to find it: In the client devices list.
What you'll see: A device details panel for the selected device.
Step 4: Review the advanced setting notice
Review the Advanced setting notice before making changes.
Where to find it: At the top of the device details panel.
What you'll see: A warning that this is an Advanced setting and should be changed only if needed.
Step 5: Review the info section
Review the explanation in the info section to understand the impact of changing the release channel.
Where to find it: In the device details panel info section.
What you'll see: An explanation of release channel override effects.
Step 6: Open the Release Channel Override dropdown
Open the Release Channel Override dropdown to view available update channels.
Where to find it: In the device details panel.
What you'll see: A dropdown list of release channel options.
Step 7: Select a release channel
Choose a release channel for the selected device.
Where to find it: In the Release Channel Override dropdown list.
What you'll see: The selected channel displayed in the dropdown.
Step 8: Apply the update
Click Update Release Channel to confirm and apply your selection.
Where to find it: In the device details panel, below the dropdown.
What you'll see: The button activates and the update is submitted.
Step 9: Confirm the update notification
Review the notification that confirms the device’s release channel has been updated.
Where to find it: Notification area.
What you'll see: A success message indicating the channel was updated.
Step 10: Use the copy icon (optional)
Click the copy icon to copy the fields, if needed.
Where to find it: In the device details panel next to copyable fields.
What you'll see: The copy icon highlights or indicates the action is available.
Step 11: Confirm the copy notification
Review the notification that confirms the content has been copied to the clipboard.
Where to find it: Notification area.
What you'll see: A success message confirming the copy action.
Step 12: Close the device details panel
Close the device details panel to return to the main client devices list.
Where to find it: At the top or corner of the device details panel.
What you'll see: The main client devices list.
Expected Result
The selected device is assigned to the chosen release channel, and a confirmation notification appears.
You'll know it worked when: You see a success notification confirming the release channel update.
Still have questions? Click here to learn how to contact Cytracom Technical Support or open a ticket.