Skip to content

Upgrading using RPM

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 OS developers. 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 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.

Note: Users of RHEL 7 and CentOS 7

If you are using MC in RHEL 7 or CentOS 7, we recommend to use RHEL 8 or Rocky Linux 8 and do a fresh installation then upload the Database backup.

Upgrading Management Console with Internet Access

RPM upgrades may require new certificates uploaded to your endpoints

If you are upgrading to Management Console 24.07.1 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 24.07.

Important: Upgrading on RHEL 8.8 in an IPV6 environment

If you are upgrading the Management Console in RHEL 8.8 with 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

  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 ensure they are 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 RHEL host operating system.

    Caution: Upgrading from MC 24.03 or previous Versions to 24.07.1

    If you are upgrading from MC 24.03 or previous versions to MC 24.07.1, follow the step 3. below before proceeding with the upgrade.

  3. Download the RHEL8 dependency file for this release from the support site and run below command from the directory where the dependency file is located.

    sudo sh ./teradicimc_<mc_version>_rhel8_mc_dependency.tar.gz

  4. Upgrade the Management Console from the directory where the rpm file is located.

    sudo dnf install teradicimc-<mc_version>.rpm

Note: Applying Profiles

If a profile was created in Management Console 23.12.1 or earlier with the Enable Audio property set to Disabled and FW 23.12.x version, 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 available RPM from the support site and ensure they are 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 RHEL host operating system.

    Caution: Upgrading from MC 24.03 or previous versions to 24.07.1

    If you are upgrading from MC 24.03 or previous versions to MC 24.07.1, follow step 3 below before proceeding with the upgrade.

  3. Download the RHEL8 dependency files for this release from the support site and run below command from the directory where the dependency file is located.

    sudo sh ./teradicimc_<mc_version>_rhel8_mc_dependency.tar.gz --disablerepo=*

  4. Upgrade the Management Console from the directory where the rpm file is located

    sudo dnf install teradicimc-<mc_version>.rpm --disablerepo=*