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
Note: You can also disable the web UI admin user and create a new PCoIP Management Console 2 administrative user (recommended).
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
Note: Profile names are case and white space sensitive.
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.
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.
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:
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 |
|
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 |
|
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. |