Upgrade a CylanceHYBRID version 1.x to version 2.x

You cannot upgrade in place an installation of CylanceHYBRID version 1.x to a CylanceHYBRID version 2.x; architectural changes in the application prevent this type of upgrade.

Instead, you will need to install CylanceHYBRID version 2.x on a new server. For more information, see Installing the CylanceHYBRID application.

You can perform this upgrade with or without migrating the settings from the previous server to the new server. Regardless of the method chosen:

  • The new instance of CylanceHYBRID 2.x must have the same hostname as the original CylanceHYBRID 1.x server.
  • On each managed device, you must add the certificate for the CylanceHYBRID 2.x instance to the keystore so that the agent will trust the CA that issues the certificate.
Do one of the following:

Task

Steps

Install a new instance of CylanceHYBRID and migrate the settings from a previous instance.

You can migrate a configuration from an instance of CylanceHYBRID version 1.4.15 and later to a new instance of CylanceHYBRID version 2.x without having to re-register the Aurora Protect Desktop or Aurora Focus agents.

The option to migrate a configuration was not available prior to CylanceHYBRID version 1.4.15.

For more information, see Importing a CylanceHYBRID configuration.

Install a new instance of CylanceHYBRID without migrating the settings from a previous instance.

You can manually set up the a new instance of CylanceHYBRID version 2.x.

However, to ensure that this new instance will properly manage your current devices without having to re-install on each device the Aurora Protect Desktop agent, and (optionally) the Aurora Focus agent, you must configure the new server with the same settings, display name and installation key as the existing CylanceHYBRID 1.x server.