Skip to content

Migrating PCoIP Management Console to a Newer Release Using OVA

Note: DNS Records

Ensure your PCoIP Management Console has a correctly configured A record and PTR record on your DNS server. It is important to maintain the IP address and DNS hostname of your currently deployed PCoIP Management Console when migrating to a newer release. This enables a seamless transition to the new PCoIP Management Console and eliminates unnecessary PCoIP endpoint configuration as each endpoint is configured to report to the previous PCoIP Management Console IP address.

Tip: Disable Auto-Config and Scheduling

Consider turning off Auto-Config and Scheduling prior to doing a database backup. Performing this step ensures both features will be off when you restore the database preventing unexpected schedules from running and preventing new devices from suddenly appearing in the PCoIP Management Consoleduring the migration process. After confirming a successful database restore consider re-enabling Auto-Config and Scheduling.

These instructions explain how to migrate PCoIP Management Console 2.x or later to a more current PCoIP Management Console release.

At the end of this section you will find instructions that will allow the new Management Console OVA format to work in an IPv6 environment.

To migrate PCoIP Management Console to a newer release:

  1. Connect to your PCoIP Management Console virtual machine console that you wish to migrate from and log in using the admin account and password. See Accessing the PCoIP Management Console Virtual Machine Console.

    • If migrating from PCoIP Management Console 2.x go to step 2.
    • If migrating from PCoIP Management Console 3.x, 19.x or higher go to step 3.

  2. PCoIP Management Console 2 users. Perform the following steps to record the IP address, netmask, and default gateway:

    1. Type sudo system-config-network to launch the network configuration tool.
    2. From the main menu, select Device configuration.
    3. In the next screen, select eth0 (eth0) - vmxnet3.
    4. Make a note of PCoIP Management Console 2's static IP address, netmask, default gateway, and DNS server. If no IP information is displayed, it is because the PCoIP Management Console 2 is configured to use DHCP which is not recommended. See Assigning a Static IP Address.
    5. Select Ok.
    6. In the next screen, select Cancel.

    7. In the next screen, select Quit.

      Recommendation

      Support does not recommend changing the PCoIP Management Console DNS configuration.

  3. PCoIP Management Console 3 and higher users. Perform the following steps to record the IP address, netmask, and default gateway:

    1. Type sudo nmtui to launch NetworkManager TUI.
    2. From the main menu, select Edit a connection.
    3. In the next screen, select eth0, and press Enter.
    4. Make a note of PCoIP Management Console 3's static IP address, netmask, default gateway DNS servers, and domains (if configured). If no IP information is displayed, it is because the PCoIP Management Console is configured to use DHCP which is not recommended. See Assigning a Static IP Address.
    5. Select < OK > or < Cancel > and press Enter.

    6. Select < Back > to return to the main screen.

      Recommendation

      Support does not recommend changing the PCoIP Management Console hostname using this tool.

    7. In the next screen, select Quit.

  4. Manage your PCoIP Management Console certificate:

    Management Console default certificate expiry date

    The default Management Console certificate used in versions 23.06 or older expired on October 15, 2023.

    If you are managing endpoints using the default Management Console certificate from Management Console 23.06 or older, you will no longer be able to manage new endpoints. Existing endpoints will be lost if they lose communication to Management Console (i.e. network or power loss). You will need to upload a valid certificate to your existing endpoints and Management Console.

    Management Console 23.08 and newer has an updated default certificate.

    • To use the updated 23.08+ default Management Console certificate, first you will need to update your endpoint profiles to include the new default Management Console certificate and push the profile out to every endpoint, including any ungrouped endpoints, before deploying the new console. If necessary, use each individual endpoint’s AWI to upload the new default Management Console certificate to the endpoint. See Managing Profiles.

      Important: Update endpoint profile's new certificate before deploying the upgrade

      Ensure that you roll out the new certificate to the endpoints prior to deploying the new PCoIP Management Console; that is, update your profile certificates using the original console. Otherwise, you will lose the management of the endpoint.

    • If you plan to use your custom PCoIP Management Console certificate after upgrading, our support team recommends that you copy it to a safe location where you can retrieve it to use with the new PCoIP Management Console. See Managing PCoIP Management Console Certificates.

    • If you plan to use a new custom PCoIP Management Console certificate after upgrading, first you will need to update your endpoint profiles to include the new PCoIP Management Console certificate (or its issuer) and push the profile out to every endpoint, including any ungrouped endpoints, before deploying the new console. If necessary, use each individual endpoint’s AWI to upload the new PCoIP Management Console certificate (or its issuer) to the endpoint. See Managing PCoIP Management Console Certificates.

  5. Back up and download the current PCoIP Management Console database archive file to an external location before beginning the upgrade:

    1. Log in to the PCoIP Management Console web interface.
    2. From SETTINGS > DATABASE, select BACK UP.
    3. Enter a description for the backup and click BACK UP.
    4. When the backup completes, select the file in the database table, click DOWNLOAD, and then save the archive file. You will need to retrieve this file later.

    Important: Database upgrades when migrating from PCoIP Management Console 2.4 or older

    Upgrades when migrating from PCoIP Management Console 2.4 or older can generate large databases that can cause issues during upgrades. See knowledge base article 1029 for workarounds.

  6. If you are using PCoIP Management Console Enterprise, record the following licensing information by viewing installed licenses for online installations or viewing installed licenses for offline installations.

    • Fulfillment ID
    • Entitlement ID (activation code)

  7. If you are using PCoIP Management Console Enterprise, deactivate the PCoIP Management Console Enterprise license from the SETTINGS > LICENSE page.

  8. Shut down the PCoIP Management Console virtual appliance.

  9. Follow Installing PCoIP Management Console using vSphere to deploy the new PCoIP Management Console release.

  10. Connect to your PCoIP Management Console virtual machine console. See Logging in to the PCoIP Management Console OVA Virtual Machine Console.

  11. Log in as admin using the default password (ManagementConsole2015) and change the admin user password. See Accessing the PCoIP Management Console Virtual Machine Console.

  12. Use the same network settings as the previous PCoIP Management Console release.

    Note: Reserve IP address against the new virtual machine if using DHCP reservation

    If you are using DHCP reservation, reserve the IP address against the new PCoIP Management Console virtual machine. Otherwise, see Assigning a Static IP Address for instructions.

  13. Restart the PCoIP Management Console and ensure it has the correct addressing information.

  14. If you are using PCoIP Management Console Enterprise, activate its license from the SETTINGS > LICENSE page.

  15. Log in to the PCoIP Management Console web interface using the following default user account:

    • User name: admin
    • Password: password

  16. If you are using a custom PCoIP Management Console certificate (either the custom certificate from the previous PCoIP Management Console release or a new custom certificate), upload the certificate to the new PCoIP Management Console. For more information creating and uploading your own certificate, see Managing PCoIP Management Console Certificates.

    Note: Skip this step if using the default signed certificate

    If you are using the default self-signed PCoIP Management Console certificate, skip this step.

  17. Upload the database archive file you saved in step 5, and then restore the database. See Managing PCoIP Management Console Databases.

    This step reverts user accounts and passwords to previous PCoIP Management Console release

    This step replaces all users on the system with the user accounts and passwords that existed on the previous PCoIP Management Console. If you changed the default web UI password for the admin account, it will not be the standard default password. If necessary, you can revert the admin account password to its default value and then reset the password. To revert the password, see Reverting the PCoIP Management Console Web Interface Default Password.

  18. Log in again using your standard user account.

  19. Check the Management Console Health field on the DASHBOARD page to ensure the PCoIP Management Console status is GOOD. See Understanding the PCoIP Management Console Dashboard.

  20. From the ENDPOINTS page, click REFRESH to see endpoints begin contacting the new PCoIP Management Console. You can also verify groups, profiles, schedules, and auto configuration rules at this time. See Managing Endpoints.

Migrating Management Console OVA format to IPv6

To migrate Management Console OVA format to IPv6, you must configure your network interface to IPv6 and then configure your firewall rules to remove IPv4 rules and allow IPv6 rules for Management Console communication. The firewall rules referenced below refer to firewalld.

  1. Perform the steps above. After performing the steps above, change the Management Console network configuration to IPv6 by performing the steps in Moving between IPv4 and IPv6

  2. Access Management Console Web UI via IPv6 address.

Time Settings

Ensure your Management Console time settings are correct by using the sudo hwclock --debug command. If there are issues, check your host computer time and date settings, BIOS and VM hardware settings.