Installing the PCoIP Management Console and Configuring Your System > Migrating from MC 1

Migrating from PCoIP Management Console 1

Please follow the steps outlined below to migrate the Management Console from PCoIP Management Console 1 to PCoIP Management Console 2.

Step 1: Install and configure PCoIP Management Console 2

  1. Install PCoIP Management Console 2 on your ESXi host.
  2. Log in to the PCoIP Management Console 2 VM console.
  3. Change the PCoIP Management Console VM console default admin password (required).
  4. Set the PCoIP Management Console 2 network properties.
  5. Activate your PCoIP Management Console 2 license (Enterprise Edition only).
  6. If you are using an auto discovery method, update your DHCP or DNS server with the new PCoIP Management Console 2 information:
  7. Log in to the PCoIP Management Console 2 web UI.
  8. Change the PCoIP Management Console 2 web UI admin user password (required).

    Note: You can also disable the web UI admin user and create a new PCoIP Management Console 2 administrative user (recommended).

  9. From the PCoIP Management Console 2 web UI, upload the desired 5.0+ firmware file for your endpoints.

    Note: At least one 5.0+ firmware image must be uploaded to PCoIP Management Console 2 before a profile can be created. When profiles are migrated from PCoIP Management Console 1, they will be assigned the highest firmware version that is present on PCoIP Management Console 2.

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

  1. Log in to your PCoIP Management Console 1 web UI and make a note of the names of the profiles you want to import.

    Note: Profile names are case and white space sensitive.

  2. Ensure that you can connect to your PCoIP Management Console 1 SSH server from your PCoIP Management Console 2 VM. To test:
    1. From the PCoIP Management Console 2 VM command line, type ssh teradici@<MC 1 IP address>.
    2. Enter your PCoIP Management Console 1 VM password.
    3. Type exit to close the session and return to PCoIP Management Console 2.
  3. Import profiles into your MPCoIP Management Console C 2.
  4. From the PCoIP Management Console 2 web UI, refresh the PROFILE page and check that your profiles have been moved over to PCoIP Management Console 2.

    Note: The profile import process will create a tab for both DUAL and QUAD zero clients. If you are only migrating one type of zero client, 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.

  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 PCoIP Management Console 2 profile.

    Note: The OSD logo is never imported. While you are in edit mode, you can manually add this logo to your PCoIP Management Console 2 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 Appendix B.

  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 PCoIP Management Console 2 ENDPOINTS page using the same group names.
  7. Associate the correct profile with each group in turn.

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

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

For each group of endpoints:

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

Running Different PCoIP Management Console Versions in Parallel

During the PCoIP Management Console migration process, you will need to run both PCoIP Management Console versions in parallel. You may also need to run two versions of the PCoIP Management Console if you have endpoints that cannot be updated to firmware version 5.0 yet.

It is important to test a small number of endpoints first before upgrading all the endpoints in your system. It is recommended that you place them in a test group in a segregated network. If you are using automatic discovery, this may require modifications to your DHCP options or DNS SRV records.

An endpoint can only be managed by one PCoIP Management Console at a time. If you are using DHCP options discovery and you plan to keep some of your endpoints managed by PCoIP Management Console 1, you can configure your DHCP server with the PCoIP Endpoint MC Address option on a scope-by-scope basis. See Adding the PCoIP Endpoint Vendor Class for details.

Important: If you are running PCoIP Management Console 1 in parallel with PCoIP Management Console 2, ensure the two versions of the PCoIP Management Console have different IP addresses.

Here are some interoperability issues to keep in mind if you run two PCoIP Management Console versions in parallel.

Table 3-4: PCoIP Management Console 2 and PCoIP Management Console 1 Interoperability

Endpoint firmware

  • PCoIP Management Console 2: Zero clients must run firmware 5.0+. The PCoIP Management Console 2 cannot discover and manage devices running previous versions of the firmware.
  • PCoIP Management Console 1: Zero clients must run a 4.x firmware version. PCoIP Management Console 1 cannot discover and manage devices running firmware 5.0+.

DHCP/DNS discovery

PCoIP Management Console 2 uses a different format for DHCP options and DNS SRV records from PCoIP Management Console 1.

Note: For information on DHCP and DNS discovery for PCoIP Management Console 1, please see “Teradici PCoIP® Management Console User Manual” (TER0812002) in the Teradici Support Documentation Center.

Management

  • PCoIP Management Console 2: Zero clients are managed by at most one PCoIP Management Console.
  • PCoIP Management Console 1: Zero clients allow multiple PCoIP Management Consoleto manage them simultaneously.

Database

The PCoIP Management Console 1 database cannot be imported into PCoIP Management Console 2 and vice versa. However, you can import 1.10.x profiles into PCoIP Management Console 2.

Communication

PCoIP Management Console 2 and PCoIP Management Console 1 do not communicate with each other.