Upgrading Intigua RPMs Todd Kirkland March 24, 2019 17:43 Updated Follow For RPM-based deployments, Intigua will provide one or more updated RPMs for upgrading Intigua when relevant. To upgrade Intigua: Run, in order: rpm -U <intigua-connector-ver> rpm -U <intigua-va-ver> rpm -U <intigua-web-ver> rpm -U <intigua-server-base-ver> rpm -U <intigua-server-ver> where <package(s)> are the upgrade packages you received from Intigua. * When using your own NGINX certificate: Backup the certificate file located in the /etc/nginx directory before the upgrade Copy back after the upgrade has completed In an existing Intigua deployment, if the update included a new version of the Intigua connector, you need to provision the updated connector to the endpoints: Create an Intigua connector management service with the new version of the services. Log into the Intigua Console as an Administrator, and go to the Servers tab. If some endpoints have already been updated, display the Intigua version column and filter the list to view only those with older versions. To avoid errors, filter the list by the Status column to view only endpoints with active connections. Remember that you'll need to update the others later. Click the uppermost checkbox to select all endpoints: If there are multiple pages, click to select all: Provision the new Intigua connector management service to the endpoints. In the Servers tab, select the endpoints, and click Server Actions > Manage Intigua on Server: Select Manage Intigua On Server, and under Configuration package, select an Intigua services management package: Click Apply. Upon provisioning the connector to an endpoint already running a version prior to 2.9.3, all managed agents are restarted. It may take some time for the action to be performed. Related articles Updating the Intigua Virtual Appliance JetAgent Supported Platforms JetPatch Supported Platforms Setting up Hardware specifications Installing Intigua 3.7 RPMs Comments 0 comments Please sign in to leave a comment.