Management Console 2.3.0 Release Notes¶
PCoIP Management Console 2.3 introduces new features, enhancements, and updates to the PCoIP Management Console. It is compatible with Tera2 Zero Clients on Firmware 5.0 or later. This release builds off of version 2.2 of the PCoIP Management Console, and includes a patch for Linux CVE-2016-5195 'Dirty COW'.
Note: After the 60-day trial expires, return the license and the Enterprise version will revert to Standard Edition, where only Standard Edition features will be available.
This article provides a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
PCoIP Management Console has been updated to provide improved support for large deployments. This results in faster interface interactions, improved database database and disk space usage, and ability for the daemon to recover from errors.
Some device profile settings that were available in PCoIP Management Console 1.10 but were unavailable in previous PCoIP Management Console 2.x releases are added:
- Auto-Connect Mode (under View Connection Server + Auto-Logon, View Connection Server + Kiosk, View Connection Server + Imprivata, and Auto-Detect)
- Use OSD Logo for Login Banner (under View Connection Server + Auto-Logon, View Connection Server + Kiosk, View Connection Server + Imprivata)
- Use Custom Session SNI (under View Connection Server + Kiosk, View Connection Server + Imprivata)
- Use Connection Server Cache Mode (Under Auto-Detect)
- Clear Trusted View Connection Server Cache (under View Connection Server, View Connection Server + Auto-Logon, View Connection Server + Kiosk, and View Connection Server + Imprivata)
- Broker Address Cache (under View Connection Server, PCoIP Connection Manager, and Auto-Detect)
- RDS Application Access
- Unified Communications Enable
- View Connection Server + Imprivata Advanced Configurations (Direct to View Address, Invert Wiegand Data, Restrict Proximity Cards)
Administrator initiated profile applications are now given a higher priority over scheduled activities. This results in a faster response to immediate actions from the administrator.
An endpoint’s settings and information can be updated to ensure it is current by using the REFRESH button from the Endpoint Details page. The refresh may take upwards of a couple of minutes. During the refresh, the button for that device will be disabled and labelled REFRESHING…
Profile properties Management Protocol Security Level and Management Protocol Discovery Mode have been added to enable devices to be configured by the PCoIP Management Console for a specific management security level and management server discovery method.
Passwords set in device profile properties are by default hidden. They can be made visible by clicking the eye icon next to the field. This increases security by preventing password leakage due to over-the-shoulder viewing.
The device details now shows both the last time the settings for the device were updated in the PCoIP Management Console and the result of the last attempted settings update, regardless of if it was successful or failed.
Administrators are now notified of reasons for any profiles that cannot be migrated from PCoIP Management Console 1.10 to PCoIP Management Console 2.x.
The CentOS operating system has been upgraded to release 6.8.
- This release of PCoIP Management Console is only intended for use in managing PCoIP Tera2 Zero Clients from within a secured corporate network.
- This release of PCoIP Management Console must not be accessible from unsecured networks, such as the open Internet. Making this release of PCoIP Management Console accessible from the open Internet is an unsupported use of the product and will void any warranty.
- This release of PCoIP Management Console requires an accessible Internet connection for enterprise licenses to be activated.
- PCoIP Management Console 2.x cannot import databases from versions of PCoIP Management Console before 2.0. However, migration instructions are available through the user guide for moving your deployment from earlier versions of PCoIP Management Console to PCoIP Management Console 2.x, and for importing profiles from earlier versions to version 2.x.
- PCoIP Management Console 2.x is not based on PCoIP Management Console 1.x. As a result, some features of PCoIP Management Console 1.x have not yet been implemented in this release. These features include:
- Management of Workstation Access Cards
- Auto Config rules using DHCP options
- SCEP provisioning
- Persistent Auto Config (replaced in 2.0 with recurring schedules)
- Export of profiles
- PCoIP® Management Console 2 Administrators’ Guide ()
- PCoIP® Zero Client Administrators’ Guide ()
- PCoIP Zero Client Firmware 5.3
- Open-source and third-party components
|2.3||October 2016||Release with new features and improvements|
|Enterprise Edition||Standard Edition||Tera2 Zero Clients|
|Deployments using the PCoIP Management Console to manage Tera2 Zero Clients on Zero Client Firmware 5.0 or higher must use PCoIP Management Console release 2.0 or higher. Tera1 devices and Remote Workstation Cards are not compatible with this release of PCoIP Management Console. Teradici recommends using the latest release of the PCoIP Management Console.||✔||✔||✔|
|This release of the PCoIP Management Console has been tested with Zero Client Firmware release 5.3.0.||✔||✔||✔|
|The OVA package for this release of PCoIP Management Console has been qualified against VMware ESXi versions 5.5 and 6.0.||✔||✔|
|Teradici is currently working on providing the official Amazon Machine Image (AMI) for use with Amazon Web Services. However, users are able evaluate Amazon EC2 installation by creating their own AMI through the use of AWS provided conversion tools or by other means. Teradici does not provide technical support for the PCoIP Management Console AMI produced through conversion tools, or on the conversion tools themselves.||✔||✔|
Migrations may fail
Migrating PCoIP Management Console deployments to PCoIP Management Console 2.5.1 or 3.0.0 may fail with a corrupted database due to the database restore taking too long. This issue stems from a known issue (68605) in older releases (2.4 and earlier), which results in excessively large or corrupted database backups. (68452)
Workaround: See KB 3243 for instructions on cleaning the database prior to backup.
Endpoint cannot be downgraded below firmware 5.0.0 using this release of the Management Console
There is an outstanding bug reported against Management Console 2.3.0 preventing the upload of any version of PCoIP firmware below 5.0.0. Workaround: use the AWI to manually downgrade the firmware. (58646)
Endpoint details incorrectly show the profile as having an empty certificate store and profile value not set even though the certificate for PCoIP Management Console and View Connection Server is uploaded in profile. (52083)
Some web browsers consider previous releases of PCoIP Management Console cache content as valid. Hence, features from the new version of PCoIP Management Console disappears when using FQDN instead of IP address. (51732)
Workaround: Clear the web browser’s cache.
Devices that are displayed in the Ungrouped endpoints table will have their online or session status column data listed as blank if the device is offline and/or out of session. Both of these values should be displayed as false in those cases. (48320)
When applying a profile to a group from the Endpoints page, the application is not recorded in the Schedule > History page and the power reset assignment for the profile is in the ‘Failed’ state when it should be skipped. (48169)
The delete function does not work when a filter is applied to the endpoints table. (44508)
Workaround: Remove the filter, then find the device(s) to delete.
Profile properties under the ‘Time’ category cause the zero client to restart when the profile is applied. (43903)
Exporting endpoints on Firefox downloads a file with unexpected filename and without ‘.csv’ file extension
Exporting the endpoints on Firefox downloads a file with an unexpected filename and without ‘.csv’ file extension. Following this, the ‘Endpoints’ page briefly displays a ‘Server not responding’ message and jumps to the dashboard. (43864)
Workaround: At the time of saving, rename the file.
When time changes between daylight savings and standard time, recurring schedules are not updated to remain at the same hour of day. (43174)
Applying filters for Session Status ‘In Session’ or ‘Out of Session’ does not display devices in the endpoints table. (39456)
When a group is deleted, all auto-configuration rules assigned to that group will also be removed without any notification. (38229)
User cannot disable Enhanced logging mode on a zero client using a PCoIP Management Console profile. (37600)
Workaround: Consider setting the Enhanced mode to one that is not applicable to your environment, such as ONESIGN or UNIFIED COMMUNICATIONS.
When a profile without a configured Certificate Store is applied to a zero client, the PCoIP Management Console shows that zero client does not match the profile. The Endpoints page shows a profile mismatch while the Endpoint Details page shows a Certificate Store mismatch. (35075)
Workaround: Configure a Certificate Store in the profile.
To give zero clients with auto configuration a Primary Group Name and/or Deepest Sub-group Name, go to Settings > Naming and select moved between grouped and ungrouped rule in the Rename Endpoints when tab. (34756)
The Display Suspend Timeout and OSD Screensaver timeout profile properties range does not match that of the zero client. In the PCoIP Management Console, the Display Suspend Timeout property can be configured with a value between 60 and 28,800 seconds. The PCoIP Zero Client AWI allows a range of 10 to 14,400 seconds. Similarly, the PCoIP Management Console Profile editor allows the OSD Screensaver Timeout property to be configured with a value between 10 and 9,999 seconds. The PCoIP Zero Client AWI allows a range of 10 to 65,535 seconds. (34474)
The PCoIP Management Console Profile editor does not enforce the requirement that Bandwidth Floor ≤ Bandwidth Target ≤ Bandwidth Limit. Profile content that does not meet this requirement will fail to apply to a zero client. (32527)
Workaround: Ensure that the profile content meets the requirements. Consider setting all three values in the profile to ensure this.
In the Change Profile dialog accessed from the Endpoints page, the Schedule Start Date value appears as ‘NaN-NaN-NaN 12: AM’. (32524)
Zero clients that have the underscore character ‘_’ at the start and/or end of the label are not properly displayed in the PCoIP Management Console. Blank fields are shown instead of endpoint data. (32398)
Workaround: Avoid underscores at the start and end of zero client labels.
The Endpoint Log dialog accessed from the Endpoint Details page takes up to ten seconds to be populated with event log messages retrieved from the zero client. (29846)
Daily recurring schedules may occur one additional time after the End Date and Time set in the schedule. (27959)
PCoIP Management Console profiles that set Local USB Audio Driver to Enable must also set HD Audio to Enable. Otherwise, the profile will fail to apply to zero clients that have HD Audio disabled. (27823)
The ‘Soft Power-off only’ and ‘Soft and Hard Power-Off’ options under the Remote Host Power Control profile should not be visible as they are not applicable to zero clients. Only the options ‘Hard Power Off only’ and ‘Power-off not permitted’ apply to zero clients. (27704)
Profiles attached to a group cannot be deleted, even though a dialog will prompt for the user to Delete or Cancel the delete action. (25358)
Workaround: Ensure the profile is not attached to any group prior to attempting to delete it. Groups using the profile can be viewed from the profile page using the widget on the right-hand side of the screen.
Time zone selection on pages Profile > Edit > OTHER and Settings > USERS > Edit now shows the offsets in standard time only. (53281)
Profile having ‘Dual’ and ‘Quad’ endpoint types now shows the correct Endpoint Version profile values under Endpoint Details page in PCoIP Management Console 2.3.0. (53221)
Time stamp of ‘Last Polling Status’ on Endpoint Details page is now displayed in the time zone of logged-in user. (53089)
Resolved an issue where PCoIP Management Console was unable to discover zero clients in recovery mode. When discovered, the software version number will be reported as 1.x. (51944)
Database imports no longer fails on a newly installed PCoIP Management Console, or where network settings have been changed on the PCoIP Management Console. (51855)
Successfully completed schedules can now be deleted from PCoIP Management Console. (48119)
Applying filters on ‘Session Status’ and ‘Online Status’ in the Endpoints table will now display the correct endpoints. (47210)
Previously, after applying profile to an endpoint, the status of the profile did not get updated on the Endpoint Details page. This issue is now fixed. (44041)
Database can now be restored when 127.0.0.1 is missing from the /etc/hosts file. If the backup cannot restored due to database corruption, an error message ‘Cannot load database archive. The backup archive is corrupt:’ will be presented. (42091)
Previously, a user might need to restart console to get the dashboard and endpoint screens correctly populated. This issue is now fixed. (40488)
ProfileMismatch column is updated when the profile changes, group moves under other group, endpoints move from one group to another, and profile is assigned/unassigned to a group. (30140)