PCoIP Management Console version 3.0.1 resolves some issues identified in 3.0.0, and updates the VM to the latest CentOS release (7.4) to mitigate known vulnerabilities for Spectre (1, 2) and Meltdown.
These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
Note: After the 60-day trial expires, any installed licenses must be removed in order to run PCoIP Management Console - FREE.
New PCoIP Management Console 3.0.1 Amazon Machine Image (AMI)
In addition to the PCoIP Management Console OVA file format, Teradici provides a supported Management Console AMI for use with Amazon EC2. Starting from PCoIP Management Console 3.0.1, users now have the option of having an enterprise management tool in the cloud.
Database backup and restore improvements
This release has been updated to improve the performance of database migrations from earlier releases, and to reduce the size of the backed up databases going forward.
New database backups will no longer store endpoint properties. Endpoint properties will be repopulated after the endpoint has regained communication with PCoIP Management Console. This reduces the size of the database and reduces the likelihood of a database backup or restore failing due to it taking too long.
When restoring from a database that is prior to PCoIP Management Console 2.5.1, the endpoint properties will no longer be updated. They will be updated upon re-connection of the endpoint to PCoIP Management Console. This improves the performance of the database restore.
When migrating from a release of PCoIP Management Console prior to 2.5.1, Teradici recommends following the steps outlined in KB 3243 to prepare the database and decrease the odds of the backup or restore failing.
Updates due to Spectre (1,2) and Meltdown vulnerabilities
CentOS has been updated to have the latest updates from RedHat to mitigate Spectre (1,2) and Meltdown vulnerabilities.
The virtual appliance hardware version has been updated to version 10 based on VMware recommendations to address the Spectre 2 vulnerability. This updates makes ESXi 5.5 the minimum version compatible with PCoIP Management Console 3.0.1.
Additional future updates can be expected for CentOS which must be applied by the administrator. Verify all updates are applied prior to deploying into a production system.
|3.0.1||March 07, 2018||Added AMI official release info|
|3.0.1||February 09, 2018||Maintenance and security update|
|3.0.0||October 19, 2017||Release with new features and improvements|
|This version of the PCoIP Management Console has been tested with Tera2 PCoIP Zero Client Firmware release 6.0.||X||X|
The OVA package for this version of PCoIP Management Console has been qualified against VMware ESXi versions 5.5 and 6.0.
It is no longer compatible with releases of ESXi prior to 5.5.
New Amazon EC2 AMI available.
PCoIP Management Console is tested against the browser version available prior to release.
Internet Explorer 11 is no longer an officially supported web browser.
Changing the firmware version in the profile causes video port resolution to become unchecked (if they were checked as part of the profile). (69212)
Workaround: Verify the profile after changing firmware and re-check the video port resolution setting if necessary.
The following time zones are not being correctly mapped during the migration from PCoIP Management Console 1:
GMT+0 GMT -> UTC+0 Europe/London and GMT+6:30 Yangon -> UTC-11 Pacific Midway (68787)
Workaround: Review the migrated profiles that contain timezone settings and manually correct the time zone.
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.
If a profile in a previous release of Management Console was configured for firmware 5.x, is migrated to Management Console 3, and only firmware 6.0.0 or higher is installed, then when the profile is next applied, it will upgrade endpoints to the new firmware but fail to apply the profile settings with the status SKIPPED. (67932)
Workaround: Upload firmware 5.x into Management Console 3. Edit the profile with this problem. Change the profile to the 5.x firmware and save it. Change the profile back to firmware 6.x and save it.
The Authorized and Unauthorized USB tables in the Endpoints Details page sometimes show incorrect values. (67926)
When setting the Session Negotiation Cipher Suite for the endpoint, the Maximum Compatibility references TLS 1.0 and higher and should reference TLS 1.1 and higher, as TLS 1.0 is no longer supported as of firmware 6.0. (67752)
The predefined filters Endpoint Updates Pending, and Endpoints Waiting on Restart do not consistently display endpoints matching those states. (66993)
The APPLY menu item under the PROFILE menu in the ENDPOINTS page is displayed as being active even when there is no profile associated with the selected group or endpoints. (66972)
If more than two filters are active on the ENDPOINTS page, then hovering over the filter list will not reveal all of the active filters. (66971)
When using Internet Explorer 11, buttons that involve lists of groups do not always work. The impacted buttons are: Schedule > New Schedule > Groups Add button Auto Configuration > New Rule > Group Endpoints > Structure > Grouped > New Group (66762)
Workaround: Use Firefox, Chrome, or Edge.
When migrating from Management Console 2.x to 3.0, if there are profiles that contain zero client firmware 6.0.0, then the settings data of the endpoint will be dropped from the Management Console. The information will repopulate the next time the endpoint reports its current settings back to the Management Console. (66374)
Workaround: Remove firmware 6.0.0 from profiles prior to upgrading or wait for endpoints to report all their settings back in.
It is not possible to select thousands of rows of endpoints for the purpose of moving. (66369)
Workaround: When endpoints are grouped, move them based on the group to minimize the number of selected rows. If the endpoints are ungrouped, they will have to be moved in smaller chunks.
The Endpoint Details page may incorrectly report USB Product and Vendor IDs in the Preferred USB Device settings for the Profile Settings. (66181)
Profile settings permit values that are too long for the "Server URI" and "DNS Name or IP Address" settings result in failed profile applications. (66162)
Workaround: Ensure values for "Server URI" and "DNS Name or IP Address" are no more than 67 characters long.
Blank values for the profile setting "Pool Name to Select" are incorrectly shown as "Not Set" on the Endpoint Details page. (66161)
The Server URI setting for the View Connection Server session type is not always applied to the endpoint. (66133)
A new session type may not get applied to an endpoint if the profile setting is missing the server URL. (66127)
Blank values are not accepted for View Connection Server setting Custom Session SNI found in the advanced section. (66078)
When creating a new profile, if the OSD logo is set, the profile saved and then the firmware version changed, the OSD logo will not be in the profile. (66032)
Workaround: Save the profile. Exit the profile, and return to add the OSD Logo.
The comparison values of "is greater than" and "is not" are not producing results for the IP Address and MAC Address filters and may result in a "ValidationException" entry in the console log file. (65917)
The View Connection Server + Imprivata OneSign connection session type does not set when the profile is applied. (64076)
Workaround: Apply the same profile twice to set the View Connection Server + Imprivata OneSign connection type.
When selecting a group in the ENDPOINTS table, the ENDPOINTS -> DETAILS menu item is shown as active when it should be disabled. (64042)
Exporting the results of a search will show empty values in the Profile column. (63913)
Some endpoints that have not connected in a long time show as online. (63017)
Workaround: Use the IP address or rename the MC VA so that the FQDN does not contain the word 'console'.
The Endpoints page table incorrectly shows Profile Mismatch is True for some zero clients even though the Endpoint Details page does not show any mismatches. (61140)
Users are not able to log into the Management Console web interface when the DHCP server assigns a host name to the Management Console Virtual Appliance. The error shown on the login page is "Waiting for the server to start." (59280)
Workaround: Follow the steps described in knowledge base article KB 2760.
Disabling individual schedule does not work if the user selects only the date without a start time. (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)
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)
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.
When a profile is applied to a zero client it always gets rebooted even when the values modified on the zero client do not require a reboot to take effect. (43903)
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.
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)
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 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.
Schedule Start Date on Change Profile Confirmation dialog shows NaN-NaN-NaN 12: AM (32524)
Endpoints 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 endpoint 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 profile settings are no longer impacted after the firmware assigned to the profile is changed. (68809)
With Management Console 3.0.0, some endpoints would lose the ability to connect to the Management Console. Within the daemon logs would be the error: [mc-applyAssignmentResultHandler-thread-6]: ApplyAssignmentFromEndpointResultHandler - eid=AA-BB-CC-DD-EE-FF Encountered an exception while handling event [FAILED toString()]. This has been resolved. (68578)
The error: "DefaultService:213 - action=handle error, e.getMessage(): Cannot invoke method isInteger() on null object" was found to occur in log files with Management Console 3.0.0. This issue is now resolved. (68571)
The Management Console 3.0 VM settings are now correctly configured.