Management Console 2.1.1 Release Notes

Release Status: General Availability (GA)

Release Overview:

  • PCoIP Management Console 2.1.1 is and maintenance and security update to PCoIP Management Console 2.1. It is strongly recommended that all users upgrade to this release.
  • PCoIP Management Console 2.1 introduced 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.
  • This article will provide a summary of compatibility notes, key feature additions, resolved issues and known issues for this firmware release.
  • 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.

Important Requirements:

  • 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
  • PCoIP Management Console 2.1 is not based on PCoIP Management Console 1.x. As a result, some features of PCoIP Management Console 1.x have not yet been implemented in 2.1. Those features are:
    • 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

Compatibility Notes Products Endpoints
Enterprise Edition Standard Edition Tera2 Zero Clients

Deployments using the PCoIP Management Console to manage Tera2 zero clients on Zero Client Firmware 5.0 or higher must use PCoIP Management Console release 2.0 or higher.
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.1.1.
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.       
Browsers:
  • Firefox 45
  • Internet Explorer 11
  • Chrome 50
  • Edge 25
 

Key Feature Additions Products Endpoint
Enterprise Edition Standard Edition Tera2 Zero Clients
No changes from MC 2.1.0 (no new features introduced in 2.1.1 over 2.1.0)

Key Resolved Issues Products Endpoint
Enterprise Edition Standard Edition Tera2 Zero Clients
43988. In larger deployments with thousands of zero clients scheduled, profile applications may not apply for a very long time.

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.
45027. When manually discovering endpoints, the Management Console may not find any devices within an IP range if there is no device at the first IP address.
40933. There are times when the radio button for Advanced profile settings is unavailable. 
43032. Property Pool Name to Select is missing from the View Connection Server + Auto-Logon session type.
40488. The dashboard and endpoints screens may occasionally not update information.
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 - Certificates 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.  
28472. The following profile configuration settings for Imprivata OneSign are not yet available for configuration:
  • Direct to View Address
  • Invert Wiegand Data
  • Restrict Proximity Cards
  • Use OSD Logo for login banner
   
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 ||

  • | Enabled | Enabled | User forced to change password |
  • | Enabled | Disabled | User forced to change password |
  • | Disabled | Enabled | User is not forced to change password |
  • | Disabled | Disabled | User is not forced to change password |
  • | Not set | Enabled|Behaviour depends on default Zero Client value for Enable Password Protection|
  • | Not set | Disabled | Behaviour depends on default Zero Client value for Enable Password Protection |
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.