Client Lifecycle Management

Cato regularly releases new Client versions that support new features and also connectivity or performance enhancements. There are different upgrade options that you can select for your account to best meet the requirements of your organization.

Client Upgrade Options

The Client Upgrade Policy screen lets you defines how Clients for SDP users are upgraded to the new version. Admin permissions are not required to update the Client to a new version.

These are the upgrade options:

  • Automatic Silent Upgrade - The Client upgrade process is managed by Cato's upgrade service and the device automatically downloads and installs the update. The new version is gradually rolled out to the Clients in your account (see below Gradual Client Roll-out). When the Client is upgrading, a notification is shown to the user indicating that an upgrade is in process.

  • User Upgrade - The SDP users are responsible for deciding when to upgrade to the new Client version on the device. When a new version is available, the Client automatically shows a notification to users. They can choose when to click Update Now in the Client to download and install the new version.

  • Managed Upgrade - For organizations that used a third-party solution to manage installing and upgrading Clients, the admin decides when to push the new version to the devices.

For more information about the Client upgrade options, see Managing the Rollout of Client Versions.

Gradual Client Roll-out

For accounts that use the Automatic Silent Upgrade or User Upgrade option to upgrade Windows and macOS Clients in their account, the Cato upgrade service gradually rolls-out the new version to accounts. The goal of gradual roll-out is to provide the best end-user experience for remote devices. Cato continually monitors the new Client versions and can quickly stop deploying the new version, remediate any issues and then continue the roll-out with a new Client that includes the necessary fixes.

Cato has several roll-out phases which occur over the time period of a few weeks. Each phase includes a percentage of customer accounts, and within a phase, the new version is also gradually deployed. So the SDP users within an account are gradually upgraded to minimize an negative impacts of the Client upgrade.

End of Life Policy for Cato Clients

Cato supports multiple versions of the Client for each operating system (OS). At some point, new features and security updates for the newest Client may be incompatible with an older version and that version is declared as End of Life (EoL). When Cato announces that a Client version is EoL, we recommend that you upgrade those Clients in your organization to the newest version.

When a vendor announces that an operating system (OS) is declared EoL, for example Windows 7, Cato will announce when the hosts or devices that are still using that version are no longer supported for the Client.

Cato can't guarantee that end-users with a Client version or device OS that is EoL will be able to connect to the network.

For more about the EoL policy, see End of Life Policy for Cato Clients.

For more about the minimum supported device OS and version, see Installing the Cato Client.

Was this article helpful?

0 out of 0 found this helpful


Add your comment