Management Console 1.10.4 Release Notes

Release Status: General Availability (GA)

Release Overview: PCoIP Management Console 1.10.4 GA is a security update. This article will provide a summary of Release Details, Compatibility NotesKnown Limitations and Known Issues for this firmware release.

Important Notes:

  • This release is a security update. It is strongly recommended that all PCoIP Management Console users upgrade to this release.
  • The combined file format including firmware 4.8.0 is to be used with PCoIP Management Console 1.10.3 or 1.10.4, it will not be supported in earlier Management Console releases.
  • The combined file format contains firmware 4.8.0 for Tera2 zero clients plus firmware 4.7.1 for Tera2 host cards and firmware 4.7.1 for Tera1 zero clients and Tera1 host cards.

Note: There are individual releases for Tera1 and Tera2 processor-based products, and a combined package that can be uploaded to the PCoIP Management Console. The Management Console will intelligently apply the firmware based on the managed device processor type.

Key Release Details
Products Platforms
Tera1 Tera2 Workstation VMware Horizon
The password used to encrypt database archives is now configurable from the VM Console interface in the "Manage database" section. Setting a custom password adds the password to a list in the file /opt/​database_snapshot/.password.

When a database archive is created it is encrypted using the most recently set custom password, or the default password if no custom password is set. When a database archive is decrypted the system attempts all of the custom passwords in the file before trying the default password.

To revert to using the default password, delete /opt/

RC4 ciphers are no longer supported for device management connections.  
RC4, EDH and EXP ciphers are disabled for secure FTP.  

Compatibility Notes:
Products Platforms
Tera1 Tera2 Workstation VMware Horizon
This PCoIP firmware is compatible with the release of VMware Horizon View that was generally available when this firmware was released (6.0.1). It is also compatible with one major release of Horizon View prior to this. Other versions of Horizon View may also be compatible, but will need to be verified in your specific deployment environment.  

Deployments using the PCoIP Management Console to manage Tera2 endpoints must use PCoIP MC release 1.8.1 or newer.
Using the latest release of the PCoIP Management Console is recommended.


Deployments using the PCoIP Management Console to manage Tera1 endpoints must use PCoIP MC release 1.7.0 or newer.
Using the latest release of the PCoIP Management Console is recommended.

This release of the MC has been tested with firmware release 4.8.0, 4.7.0, 4.6.0, 4.5.1, 4.2.x, 4.1.x, 4.0.x, 3.5.x, 3.4.x, 3.3.x 3.2.x and 3.1.x.
It has also been tested with VMware Player version 4.0.6, VMware Player version 5.0.2, VMware Workstation version 7.1.6, and VMware ESXi version 5.1.0.
While mixed firmware release operation is not tested, firmware 4.8.0 is compatible with 4.7.x, 4.6.x, 4.5.x, 4.2.x, 4.1.x, 4.0.x, 3.5.x, 3.4.x, 3.3.x 3.2.x and 3.1.x releases.

Firmware 4.0.0 and later is not interoperable with firmware releases 3.0 and earlier.

Note: PCoIP firmware 4.5.1 or 4.6.0 will be used as a minimum firmware requirement prior to moving to release 4.7.0 or newer.

Firefox 23 (or later)
Internet Explorer 8, 9 and 11(compatibility view only) 


Key Known Limitations Products Platforms
Tera1 Tera2 Workstation VMware Horizon

34502. The PCoIP Management Console cannot be used to configure the IPv6 Gateway Address field.
Workaround: Enable and configure DHCPv6 or SLAAC to set this field or configure the field statically using the device Administrative Web Interface.

33910. Management Console 1.x is unable to manage zero clients that have been upgraded to firmware 5.0.
34424. The Auto Power Off feature, called Client Power Down Timeout Seconds in the MC, is supported in Tera2 zero clients only. The Profile setting incorrectly states that it is supported in both Tera1 and Tera2 zero clients.

Known Issues
25466. The combined file containing firmware 4.8.0 for Tera2 Zero Clients, with file suffix .pcoip, is not compatible with MC 1.10.2 or older. Workaround: To use this combined file upgrade to MC 1.10.3.
32657. Wake on LAN cannot be applied to the host card from a Profile setting. Workaround: use the AWI to change the Wake on LAN setting on a PCoIP host card.
32586 - Device labels not used as device names. If the option "use device labels as device names in the MC" is set to yes the device name displayed in the device tab will still use pcoip-portal-mac. Workaround: Move the device in question from one Group to another Group and the device label will show up.

28750. After Persistent AutoConfig has run, if the admin is logged into Management Console with Internet Explorer 10, an alert will pop up stating that the user is logged out. Internet Explorer may be locked up at this time. Workaround: Close Internet Explorer, and reopen it to Management Console or use Firefox.

34417. When using the Update tab to update firmware if you select a firmware version of the devices to update and it contains a suffixed release number (e.g. -p1 or -rc2) then no zero clients are displayed in the list of devices to update. Workaround: Select Group instead of Version Number.
29487. Persistent AutoConfig will always provision a firmware to the device and reboot it, even if it has been configured to only provision firmware when different from what is currently on the device. This causes zero clients to always reboot. Workaround: Do not include firmware in the profile for the group the device is placed in by AutoConfig.
25886. Devices that have firmware updated outside of a profile will continue to report the old firmware version for a while. Workaround: Device firmware reporting may take up to one hour to update. Rediscovery of the device will make this update occur sooner.
35311. Vulnerability scan will find CVE-2015-3306 ProFTPD mod_copy as a critical vulnerability. Workaround: Disable ProFTPD mod_copy function see KB 2751.

The above known issues are under investigation. Please subscribe to this knowledge base item to receive updates.