Upgrade Connect¶
Tip
Download links and package manager instructions are available on the download page
In order to benefit from new features and enhancements, we recommend upgrading Connect whenever a new release is available.
Tip
We recommend rebooting the machine after Connect is installed and configured, or upgraded.
Points to note when upgrading¶
Any existing installation will be replaced by the new version.
It's possible to upgrade a Connect Endpoint, even when connecting remotely to it using Connect.
There will be a short loss of TAN connectivity while the upgrade is in progress.
Warning
Do not attempt to upgrade Connect from an installer package hosted on storage accessed via Connect.
For example, attempting to run the installer from a Samba drive mapped over Connect will fail, since the file will become inaccessible during the upgrade.
Upgrading the client on Windows¶
Download and run the installer executable as per the instructions in Install Connect on Windows.
The new version of Connect will automatically start and use the existing credentials.
Automated update¶
Version 3.5.0 of the Connect client introduced an auto-updater. When an update is available, a dialog is displayed to the user:
Click Get update to download and install the latest version.
Note
The automated update for CyberHive Connect on Windows is for users who installed the client themselves. For users where CyberHive Connect was installed by a system administrator, the auto-update is not available.
Upgrading the client on Linux¶
The installation instructions explain how to add a repository for both Debian- and RPM-based distributions.
Debian¶
Tip
apt install is preferred here, since unlike apt upgrade, it allows you
to limit the packages which are upgraded.
If you want to upgrade all packages on your system, use apt upgrade.
It's also possible to install .deb packages directly, in which case use
dpkg -i to install the new version.
RPM¶
Tip
This will only upgrade cyberhive-connect.
If you want to upgrade all packages on your system, use yum upgrade instead.
Restart the service¶
Restart the service, as the package manager does not do this.
For systemd: