Upgrade Guides

This guide explains how CtrlOne components update and how to move a fleet forward without surprises.

The agent updates itself

The Windows agent can update silently in the background, so devices converge on a current build without a manual reinstall on each machine. The console's version reporting helps you see which devices are behind.

The desktop console updates separately

The desktop Agent Console is distributed as its own download and is not updated by re-running the agent installer. To move it forward, download and deploy the current desktop console build.

Upgrading a fleet safely

Let the agent self-update handle the fleet, and use the console's version view to confirm convergence.
When you need a manual bump, pilot the new build on a small group first.
Keep policies unchanged during an upgrade so you can attribute any behaviour change to the build, not the policy.

Frequently asked questions

Do I have to reinstall the agent to update it?

No - the agent can self-update silently. Reinstalls are only needed in special cases.

Why didn't my desktop console change after updating the agent?

They're separate. The desktop Agent Console ships as its own download and must be updated on its own.

See what changed

Check the release notes guide for how updates are communicated and where to find them.