Management Console 2.1.0 Release Notes¶
Release Status: General Availability (GA)
- PCoIP® Management Console 2.1 is a feature release. It includes both the Enterprise Edition and introduces the Standard Edition which supports up to 2,000 managed devices using a single administration user. It is compatible with Tera2 Zero Clients on firmware 5.0 or higher.
- To evaluate Enterprise Edition features, request a 60-day Enterprise trial license
Note: Once a trial license expires, you will no longer be able to log into the PCoIP Management Console until you return the license. Once the license is returned, the PCoIP Management Console will revert to Standard Edition and you will be able to log in as long as the admin account has not been disabled.
- This article will provide a summary of compatibility notes, key feature additions, resolved issues and known issues for this firmware release.
- PCoIP Management Console 2.1 is only intended for use in managing PCoIP Tera2 Zero Clients from within a secured corporate network.
- Important: PCoIP Management Console 2.1 must not be accessible from unsecured networks, such as the open Internet. Making PCoIP Management Console 2.1 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 licenses to be activated.
- PCoIP Management Console 2.1 cannot import databases from versions of PCoIP Management Console before 2.0. However, migration instructions are available through the user guide for moving your deployment from earlier versions of PCoIP Management Console to PCoIP Management Console 2.1, and for how to import profiles from earlier versions of PCoIP Management Console to PCoIP Management Console 2.1
- Management of Workstation Access Cards
- Auto Config rules using DHCP options
- SCEP provisioning
- Persistent Auto Config (replaced in 2.0 with recurring schedules)
- Export of profiles
|Enterprise Edition||Standard Edition||Tera2 Zero Clients
|Deployments using the PCoIP Management Console to manage Tera2 zero clients on Zero Client Firmware 5. must use PCoIP Management Console release 2.0 or newer.
Tera1 devices and Remote Workstation Cards are not compatible with this release of PCoIP Management Console.
Using the latest release of the PCoIP Management Console is recommended.
|This release of the PCoIP Management Console has been tested with Zero Client Firmware release 5.0.2.||✔||✔||✔|
|The OVA package for this release of PCoIP Management Console has been qualified against VMware ESXi versions 5.1, 5.5 and 6.0.||✔||✔|
|At this time there is no official AMI for use with Amazon Web Services though we are working to provide one. However, users are able evaluate EC2 installation by creating their own AMI through the use of AWS provided conversion tools or by other means. Teradici cannot provide technical support for the PCoIP Management Console AMI produced through conversion tools, or on the conversion tools themselves.|
|Key Feature Additions||Products||Endpoint|
|Enterprise Edition||Standard Edition||Tera2 Zero Clients
|Standard Edition: PCoIP Management Console Standard Edition enables a single administrator to manage a basic deployment of up to 2,000 Tera2 PCoIP Zero Clients; upgrade firmware, manage configuration profiles, discover devices and schedule actions at no charge.
If an IT Administrator would like to upgrade they can purchase a subscription license of Enterprise Edition which enables large enterprise deployments to manage up to 20,000 Tera2 PCoIP Zero Clients from a single console by multiple administration users, and includes the assurance of support and maintenance for both the Tera2 PCoIP Zero Client firmware and PCoIP Management Console. With highly demanded enterprise features and usability, users can enjoy greater uptime.
|License Status: IT administrators are now able to look up their license status in a new license page. This page is found under SETTINGS, LICENSE and displays a list of all active licenses, their expiration date, and the number of end-point licenses that are available and consumed by managed devices. Expired licenses will not appear on this page.||✔||✔|
|License Expiration Notification: License expiration notifications area visible in a notice bar near the top of each page within the PCoIP Management Console Enterprise Edition user interface starting 60 days before the license expires. This permits administrators to ensure that they have sufficient notification in order to secure updated licenses prior the expiration of Enterprise licenses.
The notice can be dismissed for 30 days at a time by selecting the "do not warn" checkbox. Clicking the X in the corner of the warning will temporarily dismiss the notice for the current page view.
|System Configuration: First time setup has been simplified through additional tools added to the OVA.These include the nano text editor as an easier-to-use option over vi , and the system-config-network tool which can configure the appliance's host name and network interface card settings through a user interface. Executing the command nano will run the nano text editor, and system-config-network will run the network settings configuration tool.||✔||✔|
|Dashboard Reporting: Statistics reported on the dashboard are updated more frequently, within a few minutes and refined. Clicking on the statistics tab will open the 'end-points' page with the table filtered to show the devices accounted for in the statistic.
|Recovery of the admin user:
In the event that the password to the admin user of the web interface of the PCoIP Management Console is lost, or the admin user is disabled, and there is no other administration user that can reset the password (or the system is moved from Enterprise Edition to Standard Edition), two command-line tools have been added to aid in recovering this user.
|Offline status accuracy improved: Devices are now reported as having gone offline within approximately one minute of the event.||✔||✔||✔|
|Operating System Security:
The default security of the delivered appliance has been improved with the following:
Complete details on the security configuration of the OVA are available in the User Guide.
|Lockout due to failed login attempts: The ability for an external entity to perform dictionary-based attacks on the PCoIP Management Console software has been reduced with the introduction of a failed login lockout policy. If a user enters an incorrect password ten times consecutively within ten minutes, then that account will be disabled for ten minutes, and following users can try again.||✔||✔|
|Easier password change: IT administrators can have more confidence that they have not incorrectly typed a password when creating a new user or changing them due to the addition of the 'Confirm Password' field for the New User and Edit User pages.||✔||✔|
|Migration of system now includes logs: The system now maintains historical logs for the PCoIP Management Console when migrating to newer software versions, or creating a database backup of the system.||✔||✔|
|Key Resolved Issues||Products||Endpoint|
|Enterprise Edition||Standard Edition||Tera2 Zero Clients
|38899. The Dashboard reports an incorrect number of offline endpoints. Workaround: Use the Endpoints page filters to get accurate counts of online and offline endpoints.||✔|
|38588. If multiple entitlement IDs (activation codes) are activated for the same type of license sku (ie, 100, 500, or 1000 managed devices), the Management Console may not recognize all of them and report the device limit as being less than the total of all licenses. Workaround: Activate each entitlement ID on a different day.||✔|
|38573. In profiles migrated from Management Console 1.10.x to Management Console 2, the Display Topology resolution settings may be applied to the wrong port in Management Console 2.||✔||✔|
37816. The following keyboard layouts are lost when a profile is migrated from MC 1.x to MC 2:
Workaround: Edit the profile after migration to restore the desired keyboard.
|37751. Migrating a MC 1.x profile that has the Language property set to "Chinese-S (China)" creates a profile in MC 2.0 with the Language set to "Chinese Traditional". Similarly, migrating a MC 1.x profile that has the Language property set to "Chinese-T (Taiwan)" creates a profile in MC 2.0 with the Language set to "Chinese Simplified". Workaround: After migrating the MC 1.x profile correct the Language property.||✔||✔|
|37732. A zero client will remain offline in the Management Console if it disconnects unexpectedly from the Management Console and then reconnects within five minutes. If reconnect takes longer five minutes or the reason for disconnect was expected by the Management Console, then the zero client will reconnect properly. Workaround: Turn off the Management Console for more than five minutes or restart the Management Console.||✔||✔|
|37635. When viewing the history of Schedules the user name is blank for immediate (apply profile, power down, power reset, reset to factory defaults) initiated from the Endpoints or Endpoint Detail pages.||✔|
|37597. It is not possible to set the Preferred Resolution override to Native in a profile. It can only be set to a specific width by height value. Workaround: Reset the zero client to its factory defaults.||✔||✔|
|37535. It is not possible to create a profile with the Language property set to French.||✔||✔|
|34829. After restoring a database archive, the MC will run one instance each of the enabled recurring schedules that were scheduled to run between the archive creation date and the archive restore date. Workaround: After restoring a database archive, disable and then re-enable scheduled actions using the All Schedules control on the Schedules page to halt any in-progress schedules.||✔|
|34760. PCoIP Management Console 2.0 Enterprise Edition can migrate profiles from MC 1.10.3 and MC 1.10.4 with some known restrictions. Some properties are not migrated, including the OSD Logo and the broker address cache array content. The migration tool requires that the MC 2.0 instance can initiate SSH connections with the source MC 1.x instance. Profile content in MC 2.0 should be reviewed for correctness after performing the migration.||✔||✔|
|34174. Deleting a group will also delete the schedules linked to the group. Workaround: Remove the group from schedules that should be preserved before deleting the group.||✔|
|31485. In the Authorized and Unauthorized Devices section of the Management Console Profile editor the four USB Protocols shown for the Class ""Human Interface Device"" are mislabelled as Any, None, None and None. The correct labels in order, with the corresponding Protocol values in brackets, are Any (\*), None (0), Keyboard (1) and Mouse (2). Authorized Devices(/Unauthorized Devices) > Class > Human Interface Device > No Subclasses(/Boot Interface Subclass) > Protocol: Any, None, None, None, should be Any, None, Keyboard, Mouse. Workaround: Choose the option that changes the numeric Protocol value shown to the desired value."||✔||✔|
|24570. When editing a previously saved profile that contains settings in an Advanced section it is possible to click the Basic radio button for that section. This clears all of the settings in that Advanced section.||✔|
|Key Known Issues||Products||Endpoint|
|Enterprise Edition||Standard Edition||Tera2 Zero Clients
|68605. 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. Workaround: See KB 3243 for instructions on cleaning the database prior to backup. Ultimately consider upgrading to the latest release of PCoIP Management Console.||✔||✔|
|37830. The Quad Display Topology Port 1 Rotation and Port 2 Rotation values are not migrated when a MC 1.x profile containing these values is migrated to MC 2. When the migrated profile is viewed, the Port 1 Rotation and Port 2 Rotation fields will show as unset in the profile. If the profile is changed, then Port 1 and Port 2 Rotation values will change to be set to No Rotation.||✔||✔||✔|
|37600. It is not possible to disable Enhanced logging mode on a Zero Client using a Management Console profile. Workaround: Consider setting the Enhanced mode to one that is not applicable to your environment. For example, ONESIGN or UNIFIED COMMUNICATIONS.||✔||✔||✔|
|35075. When a profile without a configured Certificate Store is applied to a zero client then the Management Console will always show that the zero client does not match the profile. The Endpoints page shows a profile mismatch and the Endpoint Details page shows the Certificate Store does not match. Workaround: Configure a Certificate Store in the profile.||✔||✔|
|34756. For zero clients grouped using Auto Configuration to be given names that use the Primary Group Name and/or Deepest Sub-group Name options configured in Settings -> Naming, the "moved between grouped and ungrouped" rule for "Rename Endpoints when" must be selected instead of "first discovered" for the name to be applied.||✔||✔|
|34474. The Display Suspend Timeout and OSD Screensaver timeout profile properties range does not match that of the zero client. In the MC the Display Suspend Timeout property can be configured with a value between 60 to 28800 seconds. The PCoIP Zero Client AWI allows a range of 10 to 14400 seconds. Similarly, the Management Console Profile editor allows the OSD Screensaver Timeout property to be configured with a value between 10 to 9999 seconds. The PCoIP Zero Client AWI allows a range of 10 to 65535 seconds.||✔||✔||✔|
|34166 - Certificated created using SHA256/ECDSA keys or signing algorithms are not supported. There is no workaround if your environment only supports certificates generated using SHA256/ECDSA keys or signing algorithms||✔||✔||✔|
|33021. Management Console does not support the Zero Client's Clear Trusted View Connection Servers cache feature.||✔||✔||✔|
|32527. The 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. Workaround: Ensure that the profile content meets the requirements. Consider setting all three values in the profile to ensure this.||✔||✔||✔|
|32524. In the Change Profile dialog accessed from the Endpoints page, the Schedule Start Date value appears as "NaN-NaN-NaN 12: AM".||✔||✔|
|32398. Zero Clients that have the underscore character '_' at the start and/or end of the label are not properly displayed in the Management Console. Blank fields are shown instead of endpoint data. Workaround: Avoid underscores at the start and end of zero client labels.||✔||✔|
|32186. The Profile Mismatch column on the Endpoints page may be blank. Workaround: Refer to the Endpoint Details for profile mismatch information.||✔||✔|
|31660. PCoIP Management Console cannot manage the Zero Client's Management Security Level feature. Workaround: Use the Zero Client Administrative Web Interface to configure this setting.||✔||✔||✔|
|31659. PCoIP Management Console cannot manage the Zero Client's Management Discovery Mode feature. Workaround: Use the Zero Client Administrative Web Interface to configure this setting.||✔||✔||✔|
|31658. The Management Console cannot configure the zero client's View Connection Server + Imprivata OneSign Restrict Proximity Cards feature.||✔||✔||✔|
|31650. The Management Console cannot configure the zero client's PCoIP Connection Manager Organization ID feature.||✔||✔||✔|
|31648. RDS Application Access cannot be set by Management Console from the zero client profile settings.||✔||✔||✔|
|31647. IPv6 Address Resolution cannot be set by Management Console from the zero client profile settings.||✔||✔||✔|
|31646. Low Bandwidth Text Code is missing from the list of Profile settings.||✔||✔||✔|
|31645. PCoIP Management Console cannot manage the Zero Client's Management Unified Communications feature. Workaround: Use the Zero Client Administrative Web Interface to configure this setting.||✔||✔||✔|
|31644. PCoIP Management Console cannot manage the Zero Client's OSD Region Tab Lockout feature. Workaround: Use the Zero Client Administrative Web Interface to configure this setting.||✔||✔||✔|
|29846. 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.||✔||✔|
|Updated 28472. The following profile configuration settings for Imprivata OneSign are not yet available for configuration:
|27959. Daily recurring schedules may occur one additional time after the End Date and Time set in the schedule.||✔||✔|
|27823. 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.||✔||✔||✔|
|27704. 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.||✔||✔||✔|
26831. Zero Client profile settings relationship between Enable Password and Force Password Change is unclear.
|| Enable Password Protection || Force Password Change on next Login || Behaviour ||
|25358. Profiles attached to a group cannot be deleted, even though a dialog will prompt for the user to Delete or Cancel the delete action. 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.||✔||✔|
The above known issues are under investigation. Please subscribe to this knowledge base item to receive updates.