PCoIP Management Console 3.1.1 Release Notes¶
PCoIP Management Console version 3.1.1 is an update over 3.0.1 and includes new features, as well as bug fixes and security updates.
These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
Note: Trial license expiry
After the 60-day trial expires, any installed licenses must be removed in order to run PCoIP Management Console - FREE.
What's New in This Release
Remote Workstation Card support
It is possible now to manage Tera2 Remote Workstation Card using Teradici Management Console 3.1.1 and newer, the key features are:
- Discovery and Management
- Profile application
- Stats on dashboard
- Migration support from Management Console 1.10.8
Remote Workstation Card and Zero Client peering (Enterprise)
Remote Workstation Cards and Zero Clients can now be peered from the Endpoint Details page under the ENDPOINT menu. This feature is available to Teradici All Access customers and enables zero clients to behave like an extension of the remote workstation card.
Zero clients will be able to wake the remote workstation card (provided they are on the same subnet) to power on prior to connection. The remote workstation card will reject connections from any other end point.
USB Profile Mismatch Calculations
Profile mismatch calculations related to USB lists (USB audio devices, authorized and unauthorized devices) has been improved to increase accuracy.
License activation and deactivation from web interface
It is now possible to use the web interface of the Management Console to activate or deactivate new licenses. This can be found in SETTINGS > LICENSE and requires the entry of the license activation code. This can be performed if the Management Console is behind a proxy or not. It may take upwards of five minutes for the Management Console to recognize the new license. These interfaces work with online licenses only. Offline licenses still require access to the command line interface.
Group only option for Auto Config rules (Enterprise)
Auto config rules can now be configured to only group the discovered endpoints and not apply profile or firmware to them. This permits endpoints to be discovered at any time, and profile application to be scheduled through the Management Console Schedule for a time that would be more convenient for a user.
OS and Library Updates
Operating system, applications and libraries that the PCoIP Management Console relies on have been updated.
Low Bandwidth Text Codec (LBTC) can now be managed
Low Bandwidth Text Codec (LBTC) can now be managed from a Management Console profile.
Endpoints that have skipped rebooting are tracked on the dashboard
The dashboard now has a quick link to "Endpoints Requiring Reboot". This links to the endpoint table and lists those devices that had profile or firmware applied to them but were not or could not be rebooted, or that the reboot status was in "skipped".
Profile mismatch calculation occurs after more events
To achieve more accurate profile and endpoint settings matching/mismatch information, the Management Console now updates the profile mismatch column in the endpoint table shortly after the following events have occurred:
- the endpoint changes the group.
- group changes the structure (gets assigned to a different group) and the endpoint now is under a different profile (as per hierarchy rules), than before.
- the profile that the endpoint is associated with is updated.
- a new profile is assigned to the group.
Endpoint session and online statuses have been consolidated
The endpoint session status and online status have been consolidated into a single status column and filter on the endpoints table. The available statuses are:
- Out of Session (online)
- In Session (online)
- In Recovery (online)
Important Notes and Requirements
- This release of PCoIP Management Console is only intended to be deployed in a secured environment. Any management exposure to unsecured endpoints should be performed through a reverse proxy.
- 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.
- PCoIP Management Console version 3.1 cannot import databases from versions of PCoIP Management Console before version 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 version 3.1, and for importing profiles from earlier versions to version 3.1.
- OVA: PCoIP Management Console 3.1.1
- AMI: PCoIP Management Console 3.1.1 ami-dde096a5 US West-2 (Oregon)
Related Documents and Software
- Teradici PCoIP® Management Console 3.1 Administrators' Guide
- Tera2 PCoIP® Zero Client Firmware 6.0 Administrators' Guide
- Tera2 Zero Client Firmware 6.0.0 Release Notes
- Deployment of PCoIP Management Console in AWS
|3.1.1||May 08, 2018||Release with new features and improvements|
|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|
|Enterprise Edition||Free Edition|
|This version of the PCoIP Management Console has been tested with Tera2 PCoIP Zero Client Firmware release 6.0.||X||X|
|This version of the PCoIP Management Console has been tested with Tera2 Remote Workstation Card Firmware release 5.0.||X||X|
The OVA package for this version of PCoIP Management Console has been qualified against VMware ESXi versions 5.5, 6.0 and 6.5.
It is no longer compatible with releases of ESXi prior to 5.5.
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.
Management Console stays in Free mode after an offline license is activated
After an offline license has been activated, the Management Console continues to operate in Free mode. The user interface will not state Enterprise, and it will not provide Enterprise features.
The license storage will show the offline license activation. (72135)
Dashboard Endpoints Requiring Reboot reports incorrect number
The dashboard Endpoints Requiring Reboot link displays an incorrect number of endpoints requiring reboot. This is observed after clicking on the link, the Endpoints table count does not match that displayed on the dashboard.
This can happen when updating Remote Workstation Cards, the dashboard count may not update after the Remote Workstation Card has been rebooted. (71085)
Database migration fails when the session timeout is exceeded
If a database migration exceeds the configured session timeout of the PCoIP Management Console web interface, the database may shift to in an inconsistent state. When this happens the log file will contain java.lang.IllegalStateException and java.lang.NullPointerException errors. (70838)
Workaround: Prior to performing the database migration, set the session timeout to Never.
Text cannot be edited from middle of the group move dialog using IE11
When using Internet Explorer 11, if the cursor is placed mid-text in the search text field of the group move dialog, after typing a character the cursor will jump to the end of the line. (70096)
Workaround: When retyping the content, erase it all and type from an empty text field. Or alternatively switch to Chrome, Firefox or Edge.
Migrations from releases prior to 2.5 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 1029 for instructions on cleaning the database prior to backup.
Migrated profiles fail to apply settings if the firmware has changed from 5.x to 6.x during the migration
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.
Power Reset statuses incorrect after group or profile change
When an endpoint is moved between groups, or the profile for the group is changed, then all statuses in the Endpoint table should update and either be unknown, or recalculated based on the new group or profile. This does not occur for 'Firmware Power Reset' and 'Profile Power Reset' statuses. These two status values continue to have the previous value. (67621)
Some predefined filters not showing results
The predefined filters Endpoint Updates Pending, and Endpoints Waiting on Restart do not consistently display endpoints matching those states. (66993)
APPLY profile active when it should be disabled
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)
Mouse hover is not revealing all active filters
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)
Endpoint settings temporarily removed from database during upgrade from Management Console 2.x to 3.0
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.
Profile application fails when "Server URI" and "DNS Name or IP Address" are too long
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.
Incorrect empty value for "Pool Name to Select" is shown
Blank values for the profile setting "Pool Name to Select" are incorrectly shown as "Not Set" on the Endpoint Details page. (66161)
Session -> Server URI setting not always being set on endpoint
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.
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 advanced "Custom Session SNI" setting
Blank values are not accepted for View Connection Server setting Custom Session SNI found in the advanced section. (66078)
OSD Logo is not saved if profile firmware version is switched on a new profile
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.
Some comparisons for IP Address and MAC Address filters do not work correctly
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)
ENDPOINT -> DETAILS active when it should be disabled
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.
Exporting the results of a search will show empty values in the Profile column. (63913)
Error 500: Internal Server
On some pages, if it is left idle for an excessive period, the Management Console may display an Error 500: Internal Server page. (63202)
Workaround: In your web browser, go back to the base URL of the Management Console and re-login.
Some endpoints that have not connected in a long time show as online
Some endpoints that have not connected in a long time show as online. (63017)
Web interface may fail to load when accessed by the FQDN
Workaround: Use the IP address or rename the MC VA so that the FQDN does not contain the word 'console'.
Profile Mismatch column on the Endpoint's page incorrectly shows True
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)
Web interface unavailable for a Management Console with DHCP assigned host name.
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 1450.
Disabling individual schedule does not work without start time.
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.
Incorrect count for additional schedules on dashboard
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)
Profile mismatch reported when Authorized Devices is set to 'Any'
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)
New features from latest PCoIP Management Console disappear when using FQDN instead of IP address
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.
Profile applications applied from the Endpoints page is not recorded in the Schedule > History page
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)
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.
Session filters return no results
Applying filters for Session Status 'In Session' or 'Out of Session' does not display devices in the endpoints table. (39456)
Deleting a group will silently delete auto-configuration rules
When a group is deleted, all auto-configuration rules assigned to that group will also be removed without any notification. (38229)
Endpoint naming using Group Naming does not work with auto configuration
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)
PCoIP Management Console does not check the value of device bandwidth setting
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.
Endpoint labels with underscore characters at the start or end are not displayed properly
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.
Daily schedules may occur one additional time
Daily recurring schedules may occur one additional time after the End Date and Time set in the schedule. (27959)
Profile's HD Audio setting may fail if set differently to Local USB Audio Driver
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)
Output error after migration from MC1 resolved
Migration script showed error message: "value too long for type character varying(500)" when both zero client and remote workstation card profiles have firmware uploaded on the Management Console 1 and 3 VMs. This issue has been resolved. (70756)
Database migration failure "Cannot get property 'value' on null object" resolved
Database migration from previous version of MC 3 or MC 2 could fail with the errors: "ERROR DefaultMeteorHandler:? - action=doPost, error: java.lang.NullPointerException: Cannot get property 'value' on null object" in the jetty logs.
This issue has been resolved. (70726)
Log message for expired messages changed
The daemon log message that occurs when there are only expired licenses in the license storage has been updated to: "No valid licenses found: Licenses are expired or can not be verified. Use /opt/teradici/licensing/mcviewlic.sh to check the installed licenses." (70088)
Empty license storage now logged as INFO
When the license storage is empty the daemon log now presents an INFO message, and provides the Flexera licensing error code: LicenseManagerImpl - No valid licenses found. Flexlm returned code (-532,3104)
If DEBUG or TRACE logging is enabled, then an exception will be displayed containing additional details from Flexera licensing. (70087)
Amazon Workspaces Session Connection Type now correctly gets set
The Amazon Workspaces Session Connection Type no longer requires multiple profile applications to take effect on an endpoint. It will get set on the first try. (69796)
Restore from previous version no longer breaks dashboard links
The dashboard links have been corrected to continue to work if the database is restored from a previous version of PCoIP Management Console. (69546)
Profile firmware change no longer changes OSD logo and certificate store settings
The settings for OSD logo and certificate are preserved when switching the profile firmware version, even if the profile has not yet been saved. (69215)
Changing firmware in profile no longer impacts video port resolution property
Changing firmware version in the profile caused video port resolution to become unchecked (if they were checked as part of the profile). This no longer occurs and the setting remains in the state it was prior to the firmware change. (69212)
GMT time zones mapped to UTC correctly from Management Console 1 profiles
Profile settings of GMT+0 GMT and GMT+6:30 Yangon and now correctly migrated from PCoIP Management Console 1. (68787)
Information on Authorized and Unauthorized USB settings correctly read from the Endpoint
The Authorized and Unauthorized USB settings are now read correctly from the endpoint and have been verified for the cases where:
- The Endpoint Details page did not show values for USB Authorized and Unauthorized devices when USB ID type is set in the profile.
- The Endpoint Details page did not show the value correctly when wildcards are set on the endpoint and USB class is set in the profile. (67926)
Session Negotiation Cipher Suite option of TLS 1.0 compatibility is no longer referenced when TLS 1.0 is no longer supported
The dropdown selection for Session Negotiation Cipher has been updated to have a help tip that describes which TLS versions are supported based on the firmware of the endpoint in use. (67752)
Group list dialogs now work in Internet Explorer 11.
Group list dialogs now work in Internet Explorer 11. (66762)
Database restore from 2.4 no longer incorrectly enables Broker Address Cache
A database restore from PCoIP Management Console 2.4 (or earlier) no longer causes Broker Address Cache to be enabled unless it was enabled in the original deployment. (66448)
Now able to move large numbers of endpoints
A memory limitation has been resolved and now large numbers of endpoints can be moved between groups or from ungrouped to grouped. (66369)
USB Audio Input/Output VID and PID correctly reported in Endpoint Details
An issue in the display of the USB Product and Vendor IDs for USB Audio Input/Output has been corrected. Additionally, the profile configuration now only accepts hexadecimal input (0000 to FFFF) for the fields. (66181)
View Connection Server + Imprivata OneSign connection type can be set with one profile application
View Connection Server + Imprivata OneSign connection type can be set with one profile application. There was an issue in previous releases that required multiple applications for this setting to take affect. (64076)
Reboots now occur depending on profile settings
Endpoints now reboot only if a profile setting that requires a reboot has been modified on the endpoint by the profile when the profile is applied to that endpoint. If a setting changes on the endpoint do not require a reboot, then the PROFILE POWER RESET column in the endpoint table will show SKIPPED. This does not change the behavior of the 'Skip reboot when applying profile on endpoints' option in the schedule page. If that setting is enabled, then the PROFILE POWER RESET column will show as SKIPPED if no reboot is required, or SKIPPED NO REBOOT if a reboot is required for the settings to take effect. (43903)
Schedule Start Date on Change Profile Confirmation dialog is no longer displayed as NaN-NaN-NaN 12: AM
Schedule Start Date on Change Profile Confirmation dialog is no longer displayed as NaN-NaN-NaN 12: AM (32524)