Management Console 2.4.0 Release Notes¶
PCoIP Management Console 2.4 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 introduces features over PCoIP Management Console 2.3.0.
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.
These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
IT administrators will be able to manage newer classes of PCoIP Zero Clients as they become available.
Devices that are deleted from PCoIP Management Console will now have all management settings cleared and set back to a default state. This will make it easier for IT administrators to dynamically remove devices (prior to physically collecting them), and not have the devices re-enroll in management with out active or automatic discovery.
- This release of PCoIP Management Console is only intended for use in managing PCoIP 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 administrators’ 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 may not be in 2.x. The enterprise trial or standard edition can be used to evaluate feature availability.
- Teradici PCoIP® Management Console 2.4 Administrators’ Guide ()
- Tera2 PCoIP® Zero Client Administrators’ Guide ()
- Tera2 PCoIP Zero Client Firmware 5.3.0
|2.4||December 2016||Release with new features and improvements|
|Enterprise Edition||Standard Edition||Tera2 PCoIP Zero Clients|
|This release of the PCoIP Management Console has been tested with Tera2 PCoIP 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.||✔||✔|
Database backups and restores fail
The database can grow too large due to the nature of action and property information being stored. This can result in the backup of the database being corrupt without warning, or the restore taking too long and ultimately failing. (68605)
Workaround: See KB 3243 for instructions on cleaning the database prior to backup. Ultimately consider upgrading to the latest release of PCoIP Management Console.
Profile fails to apply if it contains certain Imprivata OneSign settings
When a profile contains either the Pre-Session Reader Beep seting or the Restrict Proximity Cards settings, which are visible when the profile's Session Connection Type is View Connection Server + Imprivata OneSign, the profile will always fail to apply. (59363)
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.4.0 preventing the upload of any version of PCoIP firmware below 5.0.0. Workaround: use the AWI to manually downgrade the firmware. (58464)
The ‘Refresh’ button can only be used once on the Endpoints page after having performed a search. In order to use it again, the ‘Search’ function must be cleared first. (56086)
If the start date is set for a schedule, but the start time is not set, then a change to the ‘Enable’ function in the schedule edit or creation page may not be saved. (55912)
Workaround: Ensure your schedule has a start time in addition to a start date.
The ‘more schedules’ text in the Dashboard section for Upcoming Schedules always states ‘(1) more schedules’ regardless of how many schedules are upcoming but do not fit in the view. (55636)
If there is an entry error in the DNS Name, IP Address, or Server URI fields in a device profile, the PCoIP Management Console will not alert to that error at the time of entry. Any errors will be displayed on the profile after it has been saved. (55568)
Workaround: Save the profile, and review the profile to verify correctness.
The profile editor does not accept a port number in a broker address when the broker address is a FQDN. ‘https://broker.domain.com:4430‘ is rejected. (54569)
Workaround: Use the IP address for the broker, or configure the broker to use a port that does not require explicit entry, for example, ‘https://broker.domain.com‘.
The endpoint details page will report a device as having a profile mismatch if the profile settings for the profile applied to the device has Peripherals > Authorized Devices set to Any Device Class, Any Sub Class, or Any Protocol. (54060)
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.