Management Console 2.0.1 Release Notes¶
Release Status: General Availability (GA)
Release Overview:
- PCoIP® Management Console 2.0 is only available in the Enterprise Edition, which is a paid-for subscription product starting at an MSRP of $20 USD/zero client.
- Find a reseller
- Request a 60-day enterprise trial license
- A complimentary version of PCoIP Management Console 2 is planned for release at the end of January 2016.
- PCoIP® Management Console 2.0 introduces the Enterprise Edition, support for up to 20,000 managed devices, multiple administration users, redesigned interface, additional discovery security options, multi-level device groups, recurring schedules, and improved profile and firmware update performance. It is compatible with Tera2 Zero Clients on firmware 5.0 or higher.
- PCoIP Management Console release 2.0.1 is an important security and bug fix update. Please ensure you upgrade 2.0.0 to 2.0.1 as soon as possible.
- This article will provide a summary of compatibility notes, key feature additions, resolved issues and known issues for this firmware release.
Important Requirements:
- Either the zero client AWI or PCoIP Management Console 1.10.3 or 1.10.4 must be used to upgrade zero clients to firmware 5.0. PCoIP Management Console 2.0 cannot detect or manage devices on firmware versions prior to version 5.0.
- Zero Clients on firmware 5.0 can only be managed by PCoIP Management Console 2.0 or higher. PCoIP Management Console 1.x cannot detect or manage devices on firmware higher than 4.8.
- The PCoIP Management Console user guide provides additional information on how to upgrade Tera2 Zero Clients to Firmware 5.0. http://www.teradici.com/web-help/MC_HTML5/TER1401005_PCoIP_MC_Help.htm#03_GettingStarted/11_UpgradeOldFW.htm
- This release of PCoIP Management Console is unable to manage Remote Workstation Cards. If you choose migrate to Zero Client Firmware 5.0 and PCoIP Management Console 2.0, then you will need to maintain PCoIP Management Console 1.10.4 to manage Remote Workstation Cards.
- This release of PCoIP Management Console is unable to manage Tera1 Zero Clients. If you choose migrate your Tera2 Zero Clients to Zero Client Firmware 5.0 and PCoIP Management Console 2.0, then you will need to maintain PCoIP Management Console 1.10.4 to manage Tera1 Zero Clients.
Important Notes:
- PCoIP Management Console 2.0 is only intended for use in managing PCoIP Tera2 Zero Clients from within a secured corporate network.
Important: PCoIP Management Console 2.0 must not be accessible from unsecured networks, such as the open Internet. Making PCoIP Management Console 2.0 accessible from the open Internet is an unsupported use of the product and will void any warranty. - PCoIP Management Console 2.0 is available in the Enterprise Edition only, and requires a license to operate. Fill out the form at http://connect.teradici.com/tryMC to request an Enterprise Trial License. The user guide provides additional information on activating and managing licenses: http://www.teradici.com/web-help/MC_HTML5/TER1401005_PCoIP_MC_Help.htm#03_GettingStarted/03_ManagelLicense.htm
- This release of PCoIP Management Console requires an accessible Internet connection for licenses to be activated.
- PCoIP Management Console 2.0 cannot import databases from previous versions of PCoIP Management Console. However, migration instructions http://www.teradici.com/web-help/MC_HTML5/TER1401005_PCoIP_MC_Help.htm#03_GettingStarted/13_Migrate.htm are available through the user guide for moving your deployment from earlier versions of PCoIP Management Console to PCoIP Management Console 2.0, and for how to import profiles from earlier versions of PCoIP Management Console to PCoIP Management Console 2.0 http://www.teradici.com/web-help/MC_HTML5/TER1401005_PCoIP_MC_Help.htm#03_GettingStarted/09_ImportProfile.htm
- PCoIP Management Console 2.0 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.0. 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
- Database import from previous versions of Management Console
- Console for configuring OS settings (e.g.: time zone, static addressing)
- This release is available as an OVA, for use with ESXi and other hypervisors compatible with the OVA format.
| Compatibility Notes | Products | Endpoints | |
| Enterprise Edition | Tera2 Zero Clients |
Tera2 Remote Workstation Cards |
|
| Deployments using the PCoIP Management Console to manage Tera2 zero clients on Zero Client Firmware 5.0 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.0. | ✔ | ✔ | |
| The OVA package for this release of PCoIP Management Console has been qualified against VMware ESXi versions 5.1 and 5.5. This package has had preliminary testing successfully completed against VMware ESXi version 6.0 but is not yet qualified for use with that version. |
✔ | ✔ | |
| 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:
|
✔ | ✔ | |
| Key Release Details |
| Security updates and minor bug fixes. |
| Key Resolved Issues | Products | Endpoints | |
| Enterprise Edition | Tera2 Zero Clients |
Tera2 Remote Workstation Cards |
|
| 37664. The operating system contains an unnecessary account with user name "user" and the password "user". Workaround: Remove the account from the system, Log in to the MC VM as root. Type userdel -r user at the command prompt. | ✔ | ||
| 37370. After restoring the Management Console database the Management Console 1.x profile migration script migrate_mc1_profile.sh is no longer able to migrate profiles. Workaround: SSH or log into the Management Console VA console and run the following command after restoring the database: psql -c "CREATE EXTENSION dblink;" pcoip_mc_db postgres | ✔ | ||
| 36491. After restoring the Management Console database the Settings -> Database screen may incorrectly display an error message reading "Error performing actions after restore". This message is incorrect and can be safely ignored. The database was restored correctly. | ✔ | ||
| 36415. Certificates without a CN value in their Subject or Issuer fields cannot be imported into Management Console profiles. | ✔ | ||
| 36412. If a zero client is running firmware 5.0.0 is configured with a FQDN that consists of just a hostname with no domain information, the Management Console will be unable to communicate with it. Workaround: Modify the zero client FQDN to include a domain. | ✔ | ||
| 36024. On the Profile Edit page, the Vendor ID and Product ID fields for the USB Authorization, USB Unauthorization and USB Bridged Override tables accept non-hexadecimal values. When a profile containing a such a non-hexadecimal value is applied to a zero client the value 0000 is written to the client instead. | ✔ | ||
| 35091. The Profile Mismatch column on the Endpoints page does not change state immediately after a profile is edited or the profile assigned to the group is changed. The value in the column is updated when the Management Console reads the zero clients settings from the device. This happens once per hour. | ✔ | ||
| 33674. When viewing the Schedule History page in Internet Explorer the LAST UPDATED column will show the text "Invalid Date" for every schedule run listed in the table. Workaround: View the page using Firefox or Chrome. | ✔ | ||
| 33250. The Profile property fields Audio Input- > Preferred USB Vendor ID, Audio Input -> Preferred USB Device Product ID, Audio Output -> Preferred USB Vendor ID and Audio Output ->Preferred USB Device Product ID use decimal notation instead of the hexadecimal notation commonly used for USB Product and Vendor ID values. | ✔ | ||
| 32686. The profile setting "Certificate Check Mode Lockout" dropdown contains an incorrectly named option named "Allow users from changing the Certificate Check Mode". This property should be named "Allow users to change the Certificate Check Mode". | ✔ | ||
| 31099. The PCoIP Management Console may not show the zero client's PCoIP session status on the Endpoints page. The In Session column is empty. Workaround: Use the Endpoint Details page to view the PCoIP session status. | ✔ | ✔ | |
| Key Known Issues: | Products | Endpoints | |
| Enterprise Edition | Tera2 Zero Clients |
Tera2 Remote Workstation Cards |
|
| 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. | ✔ | ||
| 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. | ✔ | ||
| 39468. If multiple license SKUs are activated on the Management Console using a single entitlement ID (activation code), then the Management Console may erroneously warn that there are more devices connected than are registered. This will not prevent new devices from connecting to the Management Console up to the appropriate license limit | ✔ | ||
| 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 | ✔ | ✔ | ✔ |
| 32524. In the Change Profile dialog accessed from the Endpoints page, the Schedule Start Date value appears as "NaN-NaN-NaN 12: AM". | ✔ | ||
| 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. |
✔ | ✔ | |
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. |
✔ | ||
| 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. | ✔ | ✔ | |
| 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. | ✔ | ||
| 37535. It is not possible to create a profile with the Language property set to French. | ✔ | ||
| 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. | ✔ | ||
| 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. | ✔ | ||
| 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. | ✔ | ✔ | |
| 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. | ✔ | ||
| 33021. Management Console does not support the Zero Client's Clear Trusted View Connection Servers cache feature. | ✔ | ✔ | |
| 32731. The Management Console Profile editor's Time Zone selector includes values that are not available on the Zero Client. They are the zone names that begin with "Etc/" and the entries that are not formatted as Region/Sub-region, including HST, MET and MST. When these values are applied the Zero Client will use the UTC time zone. Workaround: Use the Zero Client's time zone list to find the your time zone and configure that value in the Management Console's Profile editor. | ✔ | ✔ | |
| 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. | ✔ | ✔ | |
| 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. | ✔ | ✔ | |
| 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. | ✔ | ✔ | |
| 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|| |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.
✔