Release Notes
Management Console 23.12.1
Management Requirements
- PCoIP Management Console 21.10 or newer supports Single Sign-on (SSO) via Multi-Factor Authentication (MFA) by integrating with the customer's Identity Provider (IDP).
- PCoIP Management Console 21.07 or newer supports self-signed certificates using SCEP for Remote Workstation Cards using firmware 21.07 or higher.
- PCoIP Management Console 21.01 or newer supports Zero Clients and Remote Workstation Cards using firmware 20.01 or higher.
- Customers upgrading to release 2010.10 or newer via RPM require access to the Internet to install Python 3.6 libraries. Optionally, customers can upgrade via the OVA format (which is packaged with Python 3.6 libraries).
- PCoIP Management Console 2.0 - 19.11 supports Zero Clients with firmware 5.x or 6.x and Remote Workstation Cards with firmware 5x.
Note: These are unsupported versions of software and firmware and Teradici strongly recommends Zero Client and Remote Workstation Card firmware 20.01 or higher, which are managed by Management Console 20.01 or higher. - Management Console manages endpoints using PCoIP firmware 5.x and newer. Check release notes for any special considerations when managing firmware with Management Console.
- 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.
- 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 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 profiles and deployments from earlier versions of PCoIP Management Console to this version.
- PCoIP Management Console is tested against the browser version available prior to release. Internet Explorer 11 is not a supported web browser.
Compatible browsers:- Firefox
- Chrome
- Edge
Release Downloads
PCoIP Management Console is available for download as OVA and RPM files.
It is also available in the Amazon Machine Image (AMI) format, and can be found in various regions in the Amazon ecosystem which are listed in each release.
Related Documents and Software
Release Overview
PCoIP Management Console version 23.12 is a release with new features and security improvements over release 23.08.
These release notes provide a summary of compatibility notes, resolved issues, and known issues for this release.
What's New in 2023.12
Support for Persistent Configuration
This release introduces a new Persistent Configuration Schedule Type, which enforces a configuration profile on managed endpoints. Each time a persistent configuration schedule runs, its endpoints will be checked for compliance; if an endpoint's profile has been modified and does not match the expected configuration, the Management Console will re-apply the configured profile.
For more information, see Managing Schedules.
Required PostgreSQL version updated to 14.8
The required PostgreSQL version has been updated to 14.8 for this release of Management Console.
Compatibility
PCoIP Zero Client & Remote Workstation Card
This version of the PCoIP Management Console has been tested with the matching version of firmware for PCoIP Zero Client and Remote Workstation Card and is compatible with the previous 3 releases.
VMware
The OVA package for this version of PCoIP Management Console has been qualified against VMware ESXi versions 7.0, 6.7, and 6.5. It is not compatible with releases of ESXi before 5.5.
Amazon
Amazon EC2 23.12 AMI is available here.
RPM Package Manager
This version of PCoIP Management Console RPM has been tested with CentOS 7.9, RHEL 7.9, RHEL 8.6, and RHEL 8.8.
None.
Profiles having broker cache entries containing a hyphen and are over 82 characters not displayed correctly
Profiles that have a broker cache entry containing a hyphen, and are over 82 characters long do not display the remaining characters after the hyphen. This entry is still correctly entered in the profile and is correctly applied to the endpoint.
To display the full broker cache entry, use the Chrome or Edge browser to activate the cursor in the profile's broker cache field and depress the Shift key and down arrow to see the complete address.
"802.1x Security" displayed as "Enable 802.1x Authentication" on the endpoint details page
The profile parameter 802.1x Security displays as Enable 802.1x Authentication on the endpoint details page under the security section.
Endpoint certificate usage type changes to No usage
After deleting an uploaded certificate in the profile, endpoint certificates in a profile that has a set usage type changes to No usage type.
Select the certificate usage type after uploading all certificates in the profile.
Activating the keyboard Enter button toggles the show/hide password function for New Certificate Rules.
When the cursor is placed in any of the fields for Request-1 of a new certificate rule, the show/hide password toggles when the keyboard Enter button is activated.
Dropdown options are enabled without selecting any endpoint under the ungrouped tab
Dropdown options are enabled without selecting any endpoint under ungrouped endpoint tab.
Selected endpoints are deselected after clicking on expand ALL
Selected endpoints are deselected after clicking on expand ALL.
Select endpoints after clicking on expand ALL.
Issues using group names that contain additional spaces for the same group name
Creating one or more groups with identical names and adding two or more adjacent spaces within the group names will display as separate group(s) with the same name on the Endpoints page. However, after creation of the endpoint groups with identical names, no groups can be found or appear within the New Group dialog.
Do not create endpoint groups with identical names.
Uploading an invalid OSD Logo image causes process to hang and produces an incorrect validation message
After uploading an invalid OSD Logo image, the validation message is incorrect and the displaying image loading process continues indefinitely.
Profile parameter labeled "Native resolution override enable" is incorrect
Profile parameter Native resolution override enable should be labelled Preferred resolution override on the Endpoint Details page.
Endpoint details preferred resolution parameter shows 0 x 0 instead of Native.
Endpoint details "Video Port <1/2/3/4>: Preferred Resolution" parameter shows 0 x 0 instead of Native.
Profile for Zero Client [Dual] fails when HD audio and Device bandwidth target set
Applying a profile to a Zero Client [Dual displays] fails when the profile has both HD audio and Device bandwidth targets set.
Use the endpoint AWI to set HD audio and Device bandwidth targets
Endpoint name not automatically changed when the "Rename Endpoints when" field is set to "first discovered".
The endpoint name does not automatically change when the "Prefix" and "Postfix" fields are configured and the Rename Endpoints when parameter is set to "first discovered".
Incorrect data is displayed for some columns of an exported endpoint details csv file
Incorrect data is displayed for the 'Certificate Status' and other columns of an exported endpoint details csv file using the Export All option.
Database backup upload fails with size greater than 505MB
Database backup upload fails with size greater than 505MB
Reduce the database size to less than 500MB.
SCEP issued certificate disappears after upgrading to FW 21.07.0
This issue affects customers using Management Console with profiles containing certificates.
SCEP certificates acquired in firmware 21.03 or earlier are treated as regular certificates after upgrading to firmware 21.07.0. If the Management Console profile has certificates, the regular certificates in the Zero Client certificate store are replaced by those in the profile.
Upgrade Management Console to version 21.07.0
# Remove certificates from the Management Console profiles # Upgrade Zero Client firmware to 21.07.0 # Request new SCEP 802.1x certificate, and select it for 802.1x authentication # Verify that Zero Client is authenticated using the new 802.1x certificate # Re-add the certificates in the Management Console profiles # Apply the profile # Verify Zero Client 802.1x authentication. and that the Zero Client certificate store has the expected certs (the 802.1x cert and those in the profile)
20.01 Endpoints not visible after upgrading from Management Console 19.05/19.11 to 20.01
If PCoIP endpoints running firmware 20.01 are managed by Management Console 19.11 or older, you will not be able to discover them after an upgrade to Management Console 20.01.
Downgrade all endpoints using firmware 20.01 to an older firmware before upgrading to PCoIP Management Console 20.01.
Profile application fails with display rotation
Profile application fails when monitor emulation rotation is set to 90 degrees clockwise for the 2nd display.
None
Peer column is empty when added to the Endpoint table
If the peer column is added to the Endpoint table, it will show no value.
Press the refresh button on the Endpoints page after the peer column is added to the Endpoint table.
Endpoint Details shows non-compliance before settings available
A recently discovered online endpoint may show non-compliance for some endpoints and profile values in the Endpoints Details page, even though there is no endpoint data available yet.
Wait for the Management Console to complete getting settings information from the endpoint, or use the REFRESH button.
Primary IPv6 DNS value not being verified
The Management Console is not verifying entered values in the Primary IPv6 DNS property. As a result, if an invalid value is entered, then the profile application will fail with the device returning the status: PEMSTATUSINVALIDNODEVALUE.
Manually ensure the Primary IPv6 DNS property value is correct.
No error message when attempting to delete a profile that is in use.
The error message "Error: Cannot delete profiles that are in-use. Please unassign the profile from all groups and try again." should display when attempting to delete a profile that is used by a group. Instead now there is an exception showing in the jetty log and no error message in the interface.
The certificate size in the certificate store of a profile is not accurate.
Certificates uploaded to store in profile does not show correct size after the profile is saved.
Filters for profile failure do not match the actual statuses.
Profile failure descriptions have been modified and the filters have not. This will result in not being able to do a search on profile failure since it now reports as profile failure offline.
Certificate status filters show Remote Workstation Cards
Certificate status filters show Remote Workstation Cards in the results even though certificates cannot be provisioned to those endpoints by SCEP.
CA Identifier field cannot be cleared
When creating an ENDPOINT CERTIFICATE rule, the CA Identifier field cannot be replaced with an empty value.
To clear the value on endpoints, first delete the original rule and then create a new one with no CA Identifier value.
Not all endpoints move between groups
Some endpoints may not move between groups if a large number of endpoints (for example > 1500) are selected to be moved.
MOVE TO GROUP dialog not showing any groups
The MOVE TO GROUP dialog box may not show any groups if some groups in the hierarchy share very similar names, only differing by the absence or presence of spaces.
Rename one of the groups so that it contains a different non-whitespace character.
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.
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.
Prior to performing the database migration, set the session timeout to Never.
Refresh button does not reset itself
The Refresh button on the Endpoints Details page may remain in the Refreshing state after being pressed.
Go back to Refresh immediately after hitting Refresh button if endpoint is in Offline status.
Some filters not correctly operating
The following filters do not correctly filter the endpoint table contents in this release:
- Profile Mismatch
- Power Reset
- Certificate Expiry date
- Get All Settings
- Network Location
- MAC Address
- IP Address
- Firmware Upload
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.
When retyping the content, erase it all and type from an empty text field. Or alternatively switch to Chrome, Firefox or Edge.
Request Certificate stays "in progress" if endpoint rejects server address
If the endpoint rejects the certificate server address, then the Request Certificate assignment will remain "in progress" and never get set to "failed".
Monitor Emulations are not migrated from Management Console 1.x
A migration from Management Console 1.x will successfully migrate the Monitor Emulation setting for Video Port 1, but the other Video ports will be set to 'Disable' after the migration.
Single character top level domain (TLD) invalid for View Connection Server
Single character top level domain (TLD) are rejected in the Server URI field of Session Connection Type "View Connection Server". For example, https://server.domain.x will be rejected.
Web browser may cache content from before upgrade
After an upgrade some web browsers may cache content from the previous release of the Management Console resulting in some new features or changes not rendering properly
Clear the web browser's cache.
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.
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.
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.
Certificate Status incorrect after changes outside of Management Console
The certificate status of an endpoint can be incorrect if the certificate store or 802.1x settings are modified on the endpoint (or endpoint is factory reset) from outside of the Management Console.
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.
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.
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.
Remote Configuration Internal and External Address Port always required
Remote Configuration (Settings > Remote) cannot be saved if the Internal Address and External Address do not have port number entered even though the help tip states that the port is only required for non-default port values.
Changing system certificate disables users
Changing the certificate for the Management Console will disable all users except the one that updated the certificate.
Log back in after changing the certificate and re-enable the users.
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.
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.
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.
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.
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.