Skip to content

Upgrading Management Console Using RPM

Update your software to the current release

From time to time, updates may be made available from support, or the developers of CentOS. While we recommend staying current on releases, it is also recommended that you test updates on a test system prior to upgrading your production system or back up a snapshot of the PCoIP Management Console before running the update.

Backup Your Database

Always ensure you have a working backup of your Management Console data when performing a Management Console removal, upgrade, or installation. Considerations should include:

  • having a current snapshot of your virtual machine

  • having a complete backup or clone of your Linux PC

  • having a current backup of your Management Console database.

There are two different scenarios that require slightly different steps when installing or upgrading Management Console using the RPM. One scenario has Management Console deployed on a site that has access to the Internet and the other scenario is having Management Console deployed on a dark site where there is no internet access.

Prior to performing a RPM upgrade, the default certificate should be uploaded to all endpoints either through a profile or directly from an endpoint AWI.

Upgrading Management Console with Internet Access

RPM upgrades may require new certificates uploaded to your endpoints

If you are upgrading to Management Console 23.12 from version 23.06 or earlier, and if you are not using custom certificates, you must upload the new Management Console certificate to your endpoints. For the new Management Console certificate SHA-256 & SHA-512 values, see the release notes.

For instructions on how to upload your certificate see Updating PCoIP Management Console Certificates after Endpoint Discovery

Prior to upgrading Management Console you can:

  • Clear the management state on all your endpoints before the upgrade and rediscover them after the upgrade.

  • Ensure that the new certificate is uploaded to your endpoints before you upgrade to Management Console 23.12.

Important: Upgrading on RHEL 8.8 in an IPV6 environment

If you are upgrading the Management Console and are using both RHEL 8.8 and IPV6, you must disable the local repository before starting the upgrade and then re-enable it after the upgrade is complete. Run the following commands:

  • Before upgrading, disable local repos: 

    subscription-manager config --rhsm.manage_repos=0

  • After upgrading is complete, re-enable local repos: 

    subscription-manager config --rhsm.manage_repos=1

If you are using a different RHEL version or are using IPV4, you do not need to take these steps.

  1. Upload the Management Console default self-signed certificate to all endpoints either through a profile or directly from an endpoint AWI if you are using the Management Console default certificate.

    1. Login to your existing Management Console, create a profile with the provided default certificate (cert.pem) file uploaded in the Certificate Store.

    2. Apply the profile to all the endpoints discovered in Management Console. Once the profile is applied successfully, the endpoint will have the new default certificate uploaded.

  2. Download the available RPM and applicable online dependency file for this release from the support site and ensure they are located on the Management Console Linux VM.

    You can use a third party tool such as WinSCP to copy and move files into the CentOS/RHEL host operating system.

  3. Upgrade Management Console dependencies using the online dependency package for your Linux deployment.

    • CentOS 7.9 and RHEL 7.9

      sudo sh ./teradicimc_<mc_verion>-online-dependency-centos-rhel7.9.tar.gz

    • RHEL 8.6, 8.8

      sudo sh ./teradicimc_<mc_verion>-online-dependency-rhel8.8.tar.gz

  4. Verify the PostgreSQL version is 14.8.

    psql -V

  5. Upgrade the Management Console from the directory where the RPM file is located.

    sudo yum install teradicimc-<version>.rpm

  6. Verify Java 8 version

    java -version

    Example:

    Java Version Output

Note: Applying Profiles

If a profile was created in Management Console 23.12.1 or earlier and FW version 23.12.x with the Enable Audio property set to "Disabled", and you intend to apply this profile in Management Console 23.12.2 or later, ensure that Enable Analog Audio Input is disabled before applying this profile.

Upgrading Management Console without Internet Access (Dark Site)

  1. Upload the Management Console default self-signed certificate to all endpoints either through a profile or directly from an endpoint AWI if you are using the Management Console default certificate.

    1. Login to your existing Management Console, create a profile with the provided default certificate (cert.pem) file uploaded in the Certificate Store.

    2. Apply the profile to all the endpoints discovered in Management Console. Once the profile is applied successfully, the endpoint will have the new default certificate uploaded.

  2. Download the dark site package, which includes PostgreSQL, Python 3 dependencies, Java 8 upgrade package, and the Management Console RPM, from the support site and ensure it is located in the <logged in user directory> on the Management Console Linux VM.

    You can use a third party tool such as WinSCP to copy and move files into the CentOS/RHEL host operating system.

  3. Use the dark site package to install or upgrade Management Console and all dependencies in your offline environment. Execute the commands where the dark site package file is located for your Linux environment.

    • CentOS 7.9 

      sudo sh ./teradicimc_<mc_version>-offline-centos7.9.tar.gz

    • RHEL 7.9 

      sudo sh ./teradicimc_<mc_version>-offline-rhel7.9.tar.gz

    • RHEL 8.6, 8.8 

      sudo sh ./teradicimc_<mc_version>-offline-rhel8.8.tar.gz --disablerepo=*

  4. Verify the PostgreSQL version is 14.8. 

    psql -V

  5. Verify the Java version is 1.8.0_372 or newer. 

    java -version