PCoIP Connection Manager 1.8.0 and PCoIP Security Gateway 1.14.0 are both components of the Teradici Cloud Access Platform.
These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
Update from RHEL 6 to RHEL 7
|1.8.0/1.14.0||July 2017||General availability release|
|Tera1 Zero Clients||Tera2 Zero Clients||PCoIP Software Clients (Win and Mac)||PCoIP Mobile Clients (iOS and Android)||PCoIP Chrome OS Client|
|PCoIP Connection Manager 1.8||?||?||?||?|
PCoIP Connection Manager does not use addresses from /etc/hosts
If the broker is configured to identify resources by host name, then DNS must be available and properly configured so that the host names are resolvable from the server hosting the PCoIP Connection Manager and from the machines from which PCoIP clients will connect. In particular, resources in Microsoft RDWA are typically configured using host names, so DNS must be used when deploying the PCoIP Connection Manager with RDSH. (42009)
PCoIP Connection Manager no longer supports MD5 certificates
When cm_setup.sh is used to install PCoIP Connection Manager, the latest version of JDK 1.8.0 is also installed. As of JDK 1.8.0_71, Java no longer supports certificates that include an MD5-based digital signature algorithm. Thus any PCoIP Connection Manager installations performed with cm_setup.sh after the release of JDK 1.8.0 (Jan 19, 2016) will not support certificates that include an MD5-based digital signature algorithm, even though installations performed before that date do support those certificates. (40774)
To allow certificates that include an MD5-based digital signature algorithm until new certificates can be obtained, perform the following steps:
PCoIP Connection Manager no longer supports certificates with RSA key lengths less than 1024 bits
If the broker or the PCoIP agent uses a certificate with an RSA key length less than 1024 bits, communication with the PCoIP Connection Manager will fail. (40237)
PCoIP Connection Manager does not work if PCoIP Security Gateway ExternalRoutableIP is not set
If /etc/SecurityGateway.conf is present but does not contain a setting for ExternalRoutableIP, the PCoIP Connection Manager may not work or clients may not be able to connect to the PCoIP Connection Manager, even if the connection manager is configured to not use the PCoIP Security Gateway. (39455)
Workaround: If the PCoIP Connection Manager is configured to use the PCoIP Security Gateway, ensure that the ExternalRoutableIP setting in /etc/SecurityGateway.conf is configured to an IP address that clients can reach.
If the PCoIP Connection Manager is not configured to use the PCoIP Security Gateway, remove or rename /etc/SecurityGateway.conf.
Client fails to connect when ExternalRoutableIP is not configured
If the ExternalRoutableIP setting is not configured in /etc/SecurityGateway.conf, both the PCoIP Security Gateway and PCoIP Connection Manager will start up and appear to operate normally, but clients will not be able to connect to launched sessions. (38140)
Workaround: Always ensure that the ExternalRoutableIP setting is properly configured in /etc/SecurityGateway.conf and ensure that it can be reached from the client network(s).
Administrator to perform or automate regular log file monitoring and cleanup
The PCoIP Connection Manager and Security Gateway do not provide a regular cleanup service for their log files. Log files can potentially fill all the storage space of the system if not monitored and cleaned up. (18701)
Configure the server to monitor the disk space usage and perform a regular clean-up. An example is provided on the PCoIP Connection Manager Reference VA at:
PCoIP Connection Manager does not support Internationalized Domain Names (IDNs)
The PCoIP Connection Manager does not support domain names that contain characters outside the standard ASCII subset defined by RFC 1035 and RFC 1123. (5513)