This article discusses best practices for managing Client upgrades for devices in your account.
We recommend that you use the Cato upgrade service to automatically upgrade Clients to the newest version, you can also choose to manually upgrade Clients using an MDM or similar solution.
Cato announces that a new Client version will soon be released in the Product Update's Release Notes. Cato follows industry best practices and gradually rolls out a new Client version to customers.
-
When the new version is available for your account, an announcement is shown in the Notifications area of the Cato Management Application
-
When the Client rollout starts for your account, the new Client version is available to download from the Client Rollout page (Access > Client Rollout)
-
2 - 4 weeks after the new version is announced in the Release Notes, the Cato upgrade service starts the gradual roll-out (see below). If you would like to receive the latest Client version sooner, open a Support ticket.
When an upcoming release is announced, here are steps that you can take to prepare:
-
Make sure that your account is using Cato's best practices for upgrading Clients:
-
To ensure your SDP Clients are running the latest version, set the Client Upgrade Policy to Automatic Silent Upgrade.
This policy uses the Cato upgrade service to automatically and seamlessly push new Client versions to devices.
-
To evaluate a new version with specific users before it is rolled out across your account, define the First Upgraded Users.
The First Upgraded Users receive the latest Client version before the rest of the users in your account. This lets you evaluate the new version on a subset of users, before it is rolled out across your account.
-
-
Monitor the First Upgraded Users for any potential issues. You can identify which users have the last version of the Client from the SDP Users Dashboard. For more information, see Using the Remote Users Dashboard.
For accounts that use the Cato upgrade service to upgrade Clients in their account, the Cato upgrade service manages the gradual roll-out to devices in the account. 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. SDP users are gradually upgraded to minimize any negative impacts of the Client upgrade.
-
Managing the Rollout of Client Versions (Client Upgrade Policy) (also describes First Upgraded Users)
0 comments
Please sign in to leave a comment.