Migrating from PCoIP Management Console 1

Follow the steps outlined here to migrate your PCoIP Management Console 1 to PCoIP Management Console version 2 or later.

PCoIP Management Console properties

Not all properties from PCoIP Management Console 1 have been migrated to the current release of PCoIP Management Console. For further details, see PCoIP Management Console 1 Profile Properties Renamed or Not Migrated

Step 1: Install and configure this version of PCoIP Management Console

Management Console formats

These instructions are for configurations using the OVA format of this release of Management Console. Different formats (AMI, RPM) will require similar steps.

To install and configure the current OVA version of PCoIP Management Console:

  1. To install PCoIP Management Console using vSphere Client:
  2. To log in to virtual machine console from vSphere Client:
  3. Changing the PCoIP Management Console Virtual Machine Default User Password
  4. Changing the Default Network Configuration.
  5. Managing Licenses Online (optional).
  6. If you are using an auto discovery method, update your DHCP or DNS server with the new PCoIP Management Console information:

  7. Using the Web Interface for the First Time.

  8. Changing the PCoIP Management Console Web Interface Default Password.
    Teradici recommends that you disable the web UI admin user and create a new PCoIP Management Console administrative user.
  9. From the PCoIP Management Console web UI, upload the desired 5.0 or later firmware file for your endpoints.
    At least one 5.0 or later firmware image must be uploaded before a profile can be created.

Step 2: Import profiles, create groups, and assign profiles to the groups

PCoIP Management Console provides a profile import script that enables you to import your PCoIP Management Console 1 profiles into newer releases of PCoIP Management Console.

Importing process creates tab for endpoints

The profile import process will create a tab for Tera2 Dual and Quad Zero Clients and Remote Workstation Cards. If you are only migrating one type of endpoint (quad or dual), it is recommended that you delete the tab for the other type to avoid accidentally configuring the wrong profile type. For example, if you are only migrating dual zero clients and you set properties in the QUAD tab, the profile will not be applied.

Migrated Profile Naming Rules

Migrated profiles are named according to the following rules:

  • If there is no profile in the new PCoIP Management Console with the PCoIP Management Console 1 profile name, then the migrated profile is called the same name as was used in PCoIP Management Console 1.

  • If there is a profile in the new PCoIP Management Console with the PCoIP Management Console 1 profile, then the migrated profile is called the PCoIP Management Console 1 name with imported appended to it. If that name is already taken, then the script appends #, where # is an integer that starts counting up from one until it finds a name that is not taken.

    Example

    If the new PCoIP Management Console does not have a 'My Profile' profile, importing this profile four times from PCoIP Management Console 1 would result in the following PCoIP Management Console profile names.

    Migrated Profile Naming Example

    # of Times Migrated PCoIP Management Console 1 Profile Name PCoIP Management Console Profile Name
    1 My Profile My Profile
    2 My Profile My Profile_imported
    3 My Profile My Profile_imported 1
    4 My Profile My Profile_imported 2

    Sort the DESCRIPTION column to show the last created profile

    If you are unsure what name the migrated profile is called, sort the profile table’s DESCRIPTION column by the last created description. The most recently created profile will be at the top. See Displaying Profile Information.

Before You Import Your Profiles

Before beginning, ensure the following prerequisites are in place:

  • For PCoIP Zero Clients and PCoIP Remote Workstation Cards, ensure you have uploaded the firmware version used in your profiles, otherwise migrated profiles will be assigned the latest firmware version that exists in PCoIP Management Console.

  • The import script requires the following firmware conditions be met, or the migration script will abort and provide an error message.

    Firmware applied in PCoIP Management Console 1 profile being migrated Firmware required to be preloaded to PCoIP Management Console 3 or later for migration script to run successfully
    No firmware applied to MC1 profile Client and Remote Workstation Card
    Client only Client
    Remote Workstation Card only Remote Workstation Card
    Client and Remote Workstation Card Client and Remote Workstation Card
  • You know your PCoIP Management Console 1 user password (that is, the password for the teradici administrative user) if it was changed. The default password is 4400Dominion.

  • You know the PCoIP Management Console 1 profile name(s).

    PCoIP Management Console 1

    Profile names are case and white space sensitive.

  • Both PCoIP Management Console 1 virtual appliance and the new PCoIP Management Console virtual appliance reside on the same network.

  • PCoIP Management Console virtual appliance is able to open an SSH tunnel to the PCoIP Management Console 1 virtual appliance over port 22.

    To test if the virtual appliance is able to open an SSH tunnel:

    1. From your PCoIP Management Console VM console, type ssh teradici@< PCoIP Management Console 1 IP address or domain name >.

    2. Enter your PCoIP Management Console 1 VM password.

    3. Type exit to close the session and return to your PCoIP Management Console.

  • On PCoIP Management Console 1.x, you perform the following steps:

    1. With root privileges, modify /etc/postgresql/9.1/main/postgresql.conf by replacing the line
      listen_addresses = 'localhost' with listen_addresses = '*'.

      Commented lines

      Note that any code preceded by the # symbol is a comment. The functioning line of code in this step is located at the bottom of the file.

    2. With root privileges, modify /etc/postgresql/9.1/main/pg_hba.conf by appending a new line host all all 0.0.0.0/0 md5 and saving the file.

    3. Reboot MC1 and make sure the changes were saved.

  • On PCoIP Management Console 3.x or newer releases, you perform the following step:

    1.Run the command sudo iptables -I INPUT 1 -p tcp -m state --state NEW --dport 5432 -j ACCEPT

Import Individual Profiles

To import profiles to PCoIP Management Console release 2 or later, run the migration script shown next for each profile that you want to import:

  1. Log in to your new PCoIP Management Console VM console. See Logging in to the VM Console on page 1.

  2. Change to the migration_script directory:
    cd /opt/teradici/database/legacy/migration_script

  3. Run the script (one or more times) to migrate one profile at a time using one of the following commands:

    • If you have not changed the PCoIP Management Console 1 user password:
      ./migrate_mc1_profile.sh -a <MC 1 address> -p <"profile name">

    • If you have changed the PCoIP Management Console 1 user password:
      ./migrate_mc1_profile.sh -a <MC 1 address> -p <"profile name"> -l <MC 1 user password>

    where <"profile name"> is the exact PCoIP Management Console 1 profile name enclosed in double quotes (for example, "My Profile").

    Profile Names in PCoIP Management Console 1

    Profile names are case and white space sensitive.

  4. Load (or reload) the newPCoIP Management Console PROFILE page to see the migrated profiles. See Managing Profiles.

  5. Select each profile and click EDIT to check that the profile settings are correct. For example, if your PCoIP Management Console 1 profile contained a certificate file, this file should also be present in your new PCoIP Management Console profile.

    Note: OSD logo is never imported

    The OSD logo is never imported. While you are in edit mode, you can manually add this logo to your PCoIP Management Console profile or modify the profile as desired. For details about other profile properties that are not migrated or that have been renamed by the profile import process, see PCoIP Management Console 1 Profile Properties Renamed or Not Migrated.

  6. From the PCoIP Management Console 1 web UI, make a note of the groups that contain the endpoints you want to migrate and then create the groups from the new ENDPOINTS page on the new PCoIP Management Console using the same group names.

  7. Associate the correct profile with each group in turn.

Troubleshooting the Profile Import Script

The profile import script is case and white space sensitive because PCoIP Management Console 1 profile names are case and white space sensitive. If the script is unable to find your 1.10.x profile, try copying the exact profile name from PCoIP Management Console 1.

To copy the exact profile name from PCoIP Management Console 1:

  1. In the PCoIP Management Console 1 PROFILES page, click the profile’s Edit link.

  2. In the Edit Profile dialog, select the entire content of the Name field and copy it.

  3. When you run the script, paste this name enclosed in double quotes as the < profile name > in the migration script instructions.

Step 3: Migrate each group of PCoIP Management Console 1 endpoints to this version of PCoIP Management Console

If you have a large deployment, Teradici recommends that you migrate your endpoints on a group-by-group basis, checking that the endpoints in each group have successfully migrated to the new PCoIP Management Console, before proceeding with the next group.

To migrate each group of endpoints:

  1. Create and enable an auto configuration rule.
  2. From PCoIP Management Console 1, upgrade Tera2 PCoIP endpoints to firmware 5.0 or later.
  3. If you are not using DHCP options or DNS service record discovery, perform a manual discovery from the new PCoIP Management Console to discover the endpoints.
  4. Refresh the new PCoIP Management Console ENDPOINTS page and check that the endpoints have been discovered and placed in the correct group with the correct associated profile.