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 Notes, Known Limitations and Known Issues for this firmware release.
- 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.
|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.