Teradici Releases Latest Zero Client Firmware 3.4

Teradici just recently released its latest firmware for PCoIP  with version 3.4. Your truly submitted USB hand scanner information that has led to bug fixes in this release!!  J

Release Details:

• Support for "T=1" PIV CAC Smartcards
• Support for smartcard bridging override (for post-session smartcard authentication)
• Enhanced Event Log and configuration options 
• Ability to turn on/off the additional logging from the event logging web page
• Increased the number of messages stored in the event log
• Changed the default event log from terse to verbose (added rate limiting on the message writes to allow this change) 
• Support for Syslog to allow PCoIP Zero Clients or PCoIP Host Cards to transmit event log messages to a remote location
• Enhanced message information for user visible On-Screen-Display (OSD) messages
• RDP module components including UI tabs have been removed. 
• Added support for the following keyboard layouts:
• Czech
• Slovenian
• Romanian
• Added support for TE’s IntelliTouch™ surface acoustic wave and AccuTouch™ five-wire resistive touchscreen technologies used in Elo TouchSystems™ products.
• Reduced the SSO time when using a zero client in a VMware View deployment with a smart card reader.
• Improved support for accessing the device web pages using Internet Explorer 8 and 9

 Resolved Issues:

• Fixed a problem where some DOT4-based printers do not work.
• Fixed audio codec issue (Realtek ALC886) when resuming from sleep mode in a workstation environment (Windows7 and Vista)
• Fixed issue that prevented connection to VMware View Connection Server through certain network load balancers.
• Implemented multiple audio quality and recording improvements.
• Fixed a problem where the device event log included messages that reported an Ethernet PHY POST test failure. This occurred on devices with the RTL8211BN and RTL8211DN PHY
• Fixed PCoIP Host Card reset under network loss scenario
• Fixed a problem where a zero client may reset while the OSD is active and the display is rotated 90 degrees counter-clockwise.
• Fixed a problem that caused large USB transfers to fail. The problem may occur while transferring photos to/from devices such as Canon cameras. The problem may also cause some print jobs to fail on certain DOT4-based printers.

Note: This issue is resolved when using PCoIP Zero Clients with 128MB (1Gbit) of system memory. Please check your PCoIP Zero Client feature specification documentation to determine the system memory size. If you have 64MB (512Mbit) of system memory, then this fix does not apply.

• Fixed a problem where the performance of a session may degrade on networks with broadcast traffic.
• Fixed a problem where some USB hand scanners do not work.
• Fixed a problem introduced in FW release 3.3.0 where devices may reset after accessing device web pages. The problem occurs when DHCP is enabled and the length of the network domain name is large.
• Fixed a problem that prevents users from accessing a device web page. The problem occurs when the Device Name field includes illegal characters or too many characters. The following rules are now enforced when configuring this field.
• The first and last character must be a letter (A-Z, a-z) or a digit (0-9)
• The remaining characters must be letters, digits, or hyphens
• The length must be 63 characters or less
•  Implemented changes to improve image quality and bandwidth management as compared to FW 3.3.x. These changes affect LAN and WAN connections between PCoIP host cards and zero clients.

 

Known Issues:

• The desktop display resolution may change when a user resizes the software client window while a session is active with a PCoIP Host card. This occurs if the client window becomes smaller than the current desktop or a larger resolution will fit within the client window. Sometimes when this change occurs the graphics driver scales the image resulting in the desktop not fitting within the client window. To work around this resize the client window or configure the graphics driver to use the monitor’s built in scaling feature.The above known issues are under investigation.