PCoIP Management Console 3.2.1 Release Notes¶
PCoIP Management Console version 3.2.1 is an update over 3.2.0, that resolves the issue of Certificates not persisting in Profile after editing, and provides other bug fixes
These release notes provide a summary of 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.
What's New in Release 3.2¶
Active Directory user authentication (Enterprise)
PCoIP Management Console Enterprise now supports connecting to an Active Directory server for user authentication into the console.
The Active Directory can be configured in SETTINGS > AUTHENTICATION. The default connection uses LDAPS but can be configured for LDAP as well. AD Groups can be defined to permit access into the application, and their respective user roles set.
User Roles (Enterprise)
Two user roles have been introduced: System Administrator can perform any function on the Management Console; and Administrator, who can access everything except the SETTINGS pages.
A role can be assigned to individual users created locally on the Management Console, or by the Active Directory group that an AD authenticated user is part of.
Web Interface performance improvements
Performance of the Endpoints table has been significantly improved through optimizations of the database interaction for generating the endpoint information.
OS and Library Updates
Operating system, applications and libraries that the PCoIP Management Console relies on have been updated.
Override to USB 1.1 can now be managed
PCoIP Management Console can now configure the Override to USB 1.1 feature on Tera2 Zero Clients. This feature is used when some USB devices perform better over the network if they are constrained to USB 1.1 instead of operating at USB 2.0.
Force Local Cursor Visible can now be managed
Force Local Cursor Visible has been added to the profile settings.
The setting can be found under Peripherals > USB.
When enabled, the zero client always shows the local cursor. When disabled, the local cursor is only shown when the host requests it, or a locally-terminated mouse is connected.
Profile Mismatch is now Profile Compliance
To improve clarity of the profile compliance status of an endpoint, the Profile Mismatch column has been renamed to Profile Compliance with the possible values of Compliance, Non-compliant, Unknown, and No profile.
Additionally, to prevent false reporting, profile mismatch in the endpoint table will be set to unknown in the following cases
- Groups are moved from one group to the other.
- Endpoints are moved from one group to the other.
- A profile is set to or cleared from a group.
- The profile set to a group is modified.
- The GET ALL SETTINGS is activated. (Manual, Regular intervals, after profile application, or when endpoint is discovered)
- When a database archive is restored.
- When an endpoint is discovered for the first time.
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.2 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.2, and for importing profiles from earlier versions to version 3.2.
- OVA: PCoIP Management Console 3.2.1
- AMI: PCoIP Management Console 3.2.1 ami-051359cb8d27920ac US West-2 (Oregon)
Related Documents and Software¶
- Teradici PCoIP® Management Console 3.2 Administrators' Guide
- Tera2 PCoIP® Zero Client Firmware 6.1 Administrators' Guide
- Tera2 Zero Client Firmware 6.1.1 Release Notes
- PCoIP® Remote Workstation Card Firmware 5.0.1 Administrators' Guide
- Tera2 Remote Workstation Card Firmware 5.0.1 Release Notes
- Deployment of PCoIP Management Console in AWS
|3.2.1||December 21, 2018||Security updates and bug fixes|
|3.2.0||November 22, 2018||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.1.||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 6.0, 6.5 and 6.7.
It is not 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 not a supported web browser.
Editing active filters no longer causes issues (79086)¶
There was an issue with editing and renaming active filters that could render filters inaccessible for editing, or clearing the active filter. This has been resolved.
Deleting one profile certificate only deletes the intended certificate (79082)¶
Previously, deleting one certificate from a profile would delete all certificates in the profile. Now, the specified certificate is deleted when deleting a certificate.
Request Certificate enabled when certificate rule applied to group (79061)¶
The Request Certificate menu item in the Endpoints page is now enabled as expected when a certificate rule has been applied to a group.
Group search in ENDPOINTS page slowness (78790)¶
The slowness in the group search dialog on the ENDPOINTS page has been resolved by introducing a delay of 1 second for refining the search based on the entered text.
Switching firmware version in profile no longer clears certificate or broker cache settings (78788)¶
Switching firmware version in profile no longer clears certificate or broker cache settings. The selection (checked or unchecked) remains after the version change.
Resolution to loss of certificates in profile (78421)¶
The issue where uploaded certificates may become lost in a profile after the profile has been later edited, has been resolved.
Subdomains for Active Directory authentication permitted (78401)¶
Subdomains such as ldaps://sub.domain.company.com are now permitted in the address field when configuring Active Directory authentication.
SNMP community does permits the entry of invalid characters (78073)¶
In the profile, the SNMP community field permits the entry of characters that are not supported by the Zero Client or Remote Workstation Card.
Peer column is empty when added to the Endpoint table (77142)¶
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 (77043)¶
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.
Auto Reconnect setting not forcing a reboot (76946)¶
The Auto Reconnect setting, which is an Advanced setting for Direct to Host + SLP Host Discovery should require a reboot when set. The Management Console, however, is not forcing the endpoint to reboot when this setting is changed via the profile.
Primary IPv6 DNS value not being verified (76943)¶
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: PEM_STATUS_INVALID_NODE_VALUE.
Manually ensure the Primary IPv6 DNS property value is correct.
No error message when attempting to delete a profile that is in use. (75030)¶
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.
Bridge USB devices shows as non-compliant if order differs (74884)¶
Bridged USB devices will show as non-compliant if the same VID and PID combinations are in the profile and the endpoint but in a different order.
Different order in broker address cache list shows as Non-Compliant (74857)¶
Profile compliance will show an endpoint as non-compliant if it has the correct broker address cache list, but in a different order than in the profile.
Incorrect profile compliance for monitor emulation and topology resolutions (74413)¶
Profile compliance is not calculating properly for the Monitor Emulation or Topology Resolutions settings.
The certificate size in the certificate store of a profile is not accurate. (74351)¶
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. (73241)¶
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 (73178)¶
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 (72694)¶
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 (72022)¶
Some endpoints may not move between groups if a large number of endpoints (for example > 1500) are selected to be moved.
Dashboard Endpoints Requiring Reboot not updating (71770)¶
The Dashboard's Endpoints Requiring Reboot is not updating after Remote Workstation Cards have rebooted.
MOVE TO GROUP dialog not showing any groups (71558)¶
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.
Invalid maximum heap size error in daemon-startup log (71232)¶
Invalid maximum heap size: -Xmx-306m
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
is present in the daemon-start log file if the instance size or RAM is too small for the PCoIP Management Console. See the administrator's guide for minimum requirements.
Dashboard Endpoints Requiring Reboot reports incorrect number (71085)¶
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 (70838)¶
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 (70632)¶
The Refresh button on the Endpoints Details page may remain in the Refreshing state after being pressed.
Profile mismatch is not accurate (70631)¶
The profile mismatch column in the endpoints table, and the profile mismatch highlight in the endpoints details pages can be incorrect.
Ungrouped endpoints not restored from earlier databases (70319)¶
Restoring a database from an older version of the Management Console (such as 2.4) will result in endpoints that were in the Ungrouped tab to no longer be present.
Rediscover the endpoints that were in the ungrouped tab.
Some filters not correctly operating (70128)¶
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 (70096)¶
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 (69762)¶
If the endpoint rejects the certificate server address, then the Request Certificate assignment will remain "in progress" and never get set to "failed".
Path required in SCEP server URI (69668)¶
Monitor Emulations are not migrated from Management Console 1.x (68795)¶
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 (68660)¶
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|https://server.domain.x/] will be rejected.
Web browser may cache content from before upgrade (68545)¶
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 (68452)¶
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|https://help.teradici.com/s/article/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 (67932)¶
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 (67621)¶
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 (67294)¶
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 (66993)¶
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 (66972)¶
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 (66971)¶
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 (66866)¶
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 (66454)¶
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 (66374)¶
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 (66162)¶
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 (66161)¶
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 (66133)¶
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. (66127)¶
A new session type may not get applied to an endpoint if the profile setting is missing the server URL.
Blank values are not accepted for View Connection Server advanced "Custom Session SNI" setting (66078)¶
Blank values are not accepted for View Connection Server setting Custom Session SNI found in the advanced section.
OSD Logo is not saved if profile firmware version is switched on a new profile (66032)¶
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.
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 (65917)¶
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.
ENDPOINT -> DETAILS active when it should be disabled (64042)¶
When selecting a group in the ENDPOINTS table, the ENDPOINTS -> DETAILS menu item is shown as active when it should be disabled.
Exporting the results of a search will show empty values in the Profile column. (63913)¶
Exporting the results of a search will show empty values in the Profile column.
Error 500: Internal Server (63202)¶
On some pages, if it is left idle for an excessive period, the Management Console may display an Error 500: Internal Server page.
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 (63017)¶
Some endpoints that have not connected in a long time show as online.
Web interface may fail to load when accessed by the FQDN (61464)¶
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 (61140)¶
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.
Web interface unavailable for a Management Console with DHCP assigned host name. (59280)¶
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."
Follow the steps described in knowledge base article [KB 1450|https://help.teradici.com/s/article/1450].
Disabling individual schedule does not work without start time. (55912)¶
Disabling individual schedule does not work if the user selects only the date without a start time.
Ensure your schedule has a start time in addition to a start date.
Incorrect count for additional schedules on dashboard (55636)¶
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.
Profile mismatch reported when Authorized Devices is set to 'Any' (54060)¶
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.
New features from latest PCoIP Management Console disappear when using FQDN instead of IP address (51732)¶
Some web browsers retain cache from previous releases of PCoIP Management Console cache, therefore features from the new version of PCoIP Management Console disappear when using FQDN instead of IP address.
Clear the web browser's cache.
Profile applications applied from the Endpoints page is not recorded in the Schedule > History page (48169)¶
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.
Exporting endpoints on Firefox downloads a file with unexpected filename and without '.csv' file extension (43864)¶
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.
At the time of saving, rename the file.
Session filters return no results (39456)¶
Applying filters for Session Status 'In Session' or 'Out of Session' does not display devices in the endpoints table.
Deleting a group will silently delete auto-configuration rules (38229)¶
When a group is deleted, all auto-configuration rules assigned to that group will also be removed without any notification.
Endpoint naming using Group Naming does not work with auto configuration (34756)¶
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.
PCoIP Management Console does not check the value of device bandwidth setting (32527)¶
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.
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 (32398)¶
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.
Avoid underscores at the start and end of endpoint labels.
Daily schedules may occur one additional time (27959)¶
Daily recurring schedules may occur one additional time after the End Date and Time set in the schedule.
Profile's HD Audio setting may fail if set differently to Local USB Audio Driver (27823)¶
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.