- #Teradici pcoip management console psql install#
- #Teradici pcoip management console psql update#
- #Teradici pcoip management console psql password#
Migrated Profile Naming Example # of Times Migrated 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. 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. 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 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. Migrated profiles are named according to the following rules: For example, if you are only migrating dual PCoIP Zero Clients and you set properties in the QUAD tab, the profile will not be applied. 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. The profile import process will create a tab for Tera2 Dual and Quad PCoIP Zero Clients and Remote Workstation Cards. Importing process creates tab for endpoints 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. Step 2: Import profiles, create groups, and assign profiles to the groups ¶ At least one 20.01 or later firmware image must be uploaded before a profile can be created. From the PCoIP Management Console web UI, upload the desired 20.01 or later firmware file for your endpoints.Teradici recommends that you disable the web UI admin user and create a new PCoIP Management Console administrative user. Changing the PCoIP Management Console Web Interface Default Password.Using the Web Interface for the First Time. Adding a DNS TXT Record (for DNS discovery).Adding the DNS SRV Record (for DNS discovery).Configuring DHCP Options (for DHCP discovery).
#Teradici pcoip management console psql update#
If you are using an autodiscovery method, update your DHCP or DNS server with the new PCoIP Management Console information:
Changing the Default Network Configuration.
#Teradici pcoip management console psql password#
#Teradici pcoip management console psql install#
PCoIP Management Console 1 Profile Properties Renamed or Not Migrated Updating Certificates after Endpoint Discoveryĭefault CentOS Configuration for PCoIP Management ConsoleĬhanging the Default Network ConfigurationĬonfiguring an Endpoint Manager Manually from an Endpoint Requesting Endpoint Certificates Using SCEP (Enterprise)Ĭonfiguring PCoIP Management Console Remote Management Upgrading Endpoints to Firmware 5.0 or LaterĬonfiguring DHCP for Endpoints that use Auto DiscoveryĬonfiguring DNS for Endpoints that use Autodiscoveryĭiscovering Endpoints Manually from PCoIP Management Console Step 3: Migrate each group of PCoIP Management Console 1 endpoints to this version of PCoIP Management Console Troubleshooting the Profile Import Script Step 2: Import profiles, create groups, and assign profiles to the groups Step 1: Install and configure this version of PCoIP Management Console Setting up Active Directory AuthenticationĬhanging the Virtual Machine Default Root Password Running Different Management Console Versions in Parallel PCoIP Management Console 22.04 Administrators Guide