PRODUCT RELEASE NOTES:
NCOMPUTING RX300 FRIMWARE, VERSION 4.4.9

Product: NComputing RX300 firmware

Version: 4.4.9

Device configuration version: 25

Supported hardware:

• NComputing RX300 thin clients
• NComputing RX300+ thin clients

Supported virtual desktop environments:  

• NComputing vSpace Pro LTS Edition
• NComputing vSpace Pro Enterprise Edition (vSpace AMP compliancy required)
• Supported host Windows OSes

• Microsoft Windows Server systems:

• Windows Server 2025*
• Windows Server 2022*
• Windows Server 2019*
• Windows Server 2016 (Multipoint Services)
• Windows Server 2016
• Windows Server Multipoint Server 2012
• Windows Server 2012 R2
• Windows Server 2008 R2

• Microsoft Windows desktop systems:

• Windows 11*
• Windows 10
• Windows 8.1
• Windows 7

* Supported in vSpace Pro Enterprise Edition only

• NComputing VERDE VDI, VERDE Secure Browser, and VERDE Remote Access (versions 8.3.4.1 and earlier, down to 8.2.8)
• Microsoft Remote Desktop Services (RDS) deployments

Supported device management systems:

• NComputing PMC (version 4.2.0 or higher)
• vSpace Console from vSpace Pro LTS Edition
• vSpace Console from vSpace Pro Enterprise Edition

Contained NComputing Pi Zero SDA firmware:

• 1.0.0

This document contains important information. Please read the entire document to ensure that your deployment process goes smoothly.

ABOUT THE PRODUCT:

NComputing RX300 and RX300+ devices are thin client devices supporting connections to NComputing vSpace Pro servers, NComputing VERDE VDI systems, as well as to Microsoft Remote Desktop Services deployments and Microsoft Windows desktop systems with the Remote Desktop feature enabled.

ABOUT THIS RX300/RX300+ RELEASE (VERSION 4.4.9):

4.4.9 is a universal RX300 and RX300+ official firmware release which replaces version 4.4.5 and earlier, adding enhancements and bug fixes.

Enhancements

• Improved GUI startup reliability to address a rare issue where the device could display a black screen with only a white mouse cursor.
• Sorted time zone listing in the proper order, based on UTC offsets and display names.
• Changed the task switcher shortcut from Alt+Tab to Ctrl+Alt+Up/Down Arrow.
• Added protection to prevent multiple configuration apply actions from being triggered by a faulty mouse.
• Updated vCAST software component for vSpace and RDP clients.

Resolved issues

• RX-2147 - Fixed an issue where the autologin countdown could stop during device bootup when connected to PMC.
• RX-2137 - Fixed an issue where Ethernet could fail to connect during bootup when TLS authentication was enabled, credentials had been previously configured, and fallback was disabled.
• RX-2140 - Fixed an issue where Wi-Fi connections could fail when the SSID contained national characters.

PREVIOUS RX300/RX300+ FIRMWARE VERSION 4.4.5 RELEASE NOTES:

Enhancements

• Updated vCAST component for smoother web-streaming performance
• Pop-up dialog boxes now appear centered on the display
• VERDE VDI Client refreshed with a cleaner UI and added compatibility for VERDE versions 8.3.4.1 and earlier, down to 8.2.8

Resolved issues

• RX-2123 – Hostname changes made in the GUI are now correctly reflected in the client OS
• RX-2121 - Fixed an issue where 802.1X networks without a fallback option incorrectly connected instead of failing as expected

PREVIOUS RX300/RX300+ FIRMWARE VERSION 4.4.0 RELEASE NOTES:

New features:

• Support for the enhanced ‘UXP Turbo’ protocol with the advanced H.264 codec (requires vSpace Pro Enterprise version 12.9.1 or higher), offering improved compression, reduced bandwidth, and lower latency, making it ideal for:

• vSpace Server access over WAN or VPN
• Applications requiring low network latency, such as CAD systems which need to render and animate 3D objects. 

The UXP Turbo with the H.264 support brings next-generation performance for vSpace Pro Enterprise servers running on Windows 10, Windows 11, Windows Server 2022, or Windows Server 2025.

• Possibility to upload wallpapers, boot-up splash images, certificates, and generic files (e.g. ovpn files) from the locally connected USB drive.
• Ability to use Generic Files to distribute OpenVPN configurations. 
• Ability to bypass the HTTP proxy when establishing management connection to PMC Endpoint Manager (e.g., when deployed on-prem), while using the configured HTTP proxy for other network connections (e.g., connections through the Internet).
• VPN icon in the system menu for IP display and quick configuration access.

Enhancements:

• New options in RX300/RX300+ vSpace Pro connection settings to enable/disable ‘UXP Turbo protocol’ and ‘H.264 decoding’ capabilities. 

These options provide the flexibility of being able to globally enable the H.264 encoding in vSpace Server (requiring higher CPU/GPU load), but disable the H.264 support on selected clients when not required. 

• Enhanced vCAST components for improved compatibility and optimized performance with full HD video content in vSpace sessions.
• Improved video and audio synchronization of vCAST-ed content.
• Support for eToken and Proton Electronic security keys to allow native redirection of them into vSpace sessions.
• Updated VERDE VDI client with Secure Browser support.
• Updated OpenVPN client to newer version.
• Continuing the auto-connect loop when encountering RDP connection errors (e.g. host machine not yet ready while powering up), if kiosk mode is configured. 
• Added Wi-Fi scan button to refresh SSIDs.
• Updated Network settings with an easy-to-navigate tab widget.
• Update device system time after login to Enterprise 802.1x network.
• Added [Esc] key support to close GUI dialogs.
• Improved handling of real-time PMC Endpoint Manager requests and communication.

Issues resolved:

• RX2092 – Resolved OpenVPN connection failure issue.
• RX2062 – Resolved issue with screen shadowing failure when PMC URL in device configuration contains the /pmc path. 
• RX2075 – Resolved Wi-Fi connection failure issue after rebooting after a power interruption.

PREVIOUS RX300/RX300+ FIRMWARE VERSION 4.2.18 RELEASE NOTES

Following are the new improvements introduced in RX300/RX300+ version 4.2.18:

• Updated software components for vCAST and SuperRDP Streaming in vSpace and RDP sessions.

The following RX300/RX300+ issues have been fixed in version 4.2.18:

• RX-2053 - Fixed the RX300+ issue where on rare occasions, the mouse pointer occasionally failed to function upon the device power up. Although the mouse cursor moved across the screen and showed activity, the pointer itself remained frozen.
• RX-2055 - Addressed the issue where the message sent from PMC did not appear on the device.
• RX-2051 - Resolved the issue where the client certificate files disappeared from the device when PMC requested the device to download CA certificate files.

PREVIOUS RX300 FIRMWARE VERSION 4.2.16 RELEASE NOTES

Following are the new improvements introduced in RX300/RX300+ version 4.2.16:

• Updated software components for vCAST and SuperRDP Streaming in vSpace and RDP sessions.

PREVIOUS RX300 FIRMWARE VERSION 4.2.15 RELEASE NOTES

4.2.15 is a universal RX300 and RX300+ firmware release which replaces the 4.2.11 and earlier firmware versions with feature enhancements and bug fixes. 

Following are the new product features introduced in RX300/RX300+ version 4.2.15:

• Addded support for tablet drawing monitor.
• Further optimized vSpace Client with enhanced UXP Turbo protocol support for speed & performance, and audio-video synchronization.
• Updated software components for vCAST Streaming in vSpace Client and RDP Client.

The following RX300/RX300+ issues have been fixed in version 4.2.15:

• RX-2043 - Microphone not working in Windows 11 (RDP client).
• RX-2041- Generate 'redirection settings' with none redirection fields when device receive no redirection policy from PMC.

PREVIOUS RX300 FIRMWARE VERSION 4.2.11 RELEASE NOTES

Following are the new product features introduced in RX300/RX300+ version 4.2.11:

• vCAST streaming software component updates for vSpace and RDP client.
• Allow PMC and vSpace Console to SHUTDOWN or REBOOT when terminal session is connected or when local apps are running.
• Support for UXP Turbo 2.0 protocol in vSpace Pro Enterprise version 12.7.3 and higher.
• Support PMC Endpoint Manager to remotely configure the device to update firmware locally via FTP/HTTP URL.
• Updated firmware support for the latest RX300+ thin client.

The following RX300/RX300+ issues have been fixed in version 4.2.11:

• RX-2035 - Fixed device does not refresh GUI when received Firmware Update settings pushed from PMC.

PREVIOUS RX300 FIRMWARE VERSION 4.2.8 RELEASE NOTES

Following are the new product features introduced in RX300 version 4.2.8:

• Universal firmware image for both RX300 and RX300+ devices.
• Support device “Raise Hand” feature to PMC Endpoint Manager (PMC 4.1 and above) for easier identification of devices whose users need help. When the device user presses the Shift-Ctrl-F2 key combination to ‘raise hand’ to PMC, PMC will display a notification and put a timestamp information into the “Raised Hand” column of Devices list.
• Updated vCAST Streaming software component.

The following RX300 issues have been fixed in version 4.2.8

• RX-2025 - Pushing profile from vSpace console or changing settings is not possible when vSpace session is connected.

PREVIOUS RX300 FIRMWARE VERSION 4.2.2 RELEASE NOTES

Following are the new product features introduced in RX300 version 4.2.2:

• Support of new ‘UXP Turbo’ protocol with vSpace Pro Enterprise (12.7.1 and higher versions) to provide enhanced desktop delivery experience for multimedia intensive use cases.
• Support for PMC’s device ‘lost’ and ‘found’ feature related to device ownership (ability to lock lost devices and unlock found devices).

Other improvements introduced in RX300 version 4.2.2:

• Enhanced PMC URL auto-discovery mechanism.
• Updated vCAST streaming software [vSpace and RDP connection modes].

The following RX300 issues have been fixed in version 4.2.2

• RX-2006 - Auto desktop connection feature does not work [VERDE VDI]. 
• RX-2000 - vSpace USB headset volume sound is too low.
• RX-1996 – Issues with static DNS after disconnecting VPN.

PREVIOUS RX300 FIRMWARE VERSION 4.1.5 RELEASE NOTES

Following are the new product features introduced in RX300 firmware version 4.1.5: 

Improvements introduced in RX300 firmware version 4.1.15:

• Updated VERDE client with VERDE VDI version 8.2.8 support
• Updated vSpace client and RDP client with vCAST streaming fixes
• Automatic download of device configuration from PMC Endpoint Manager during initial onboarding

The following RX300 firmware issues have been fixed in version 4.1.15:

• RX-1977 – Pushing device setting or profiles from vSpace Console to RX300 devices would fail and generate error messages. 
• RX-1974 - No video redirection support from webcam with H.264 video stream.
• RX-1991 - USB pendrive redirection not supported with empty storage label

PREVIOUS RX300 FIRMWARE VERSION 4.1.5 RELEASE NOTES

Following are the new product features introduced in RX300 firmware version 4.1.5: 

• Support for screen shadowing through PMC (requires PMC 2.7.0 or newer).
• Support for passcode-based PMC device onboarding (requires PMC 2.7.0 or newer).
• Selective protection of Setup GUI sections.
• Support for SPICE protocol in VERDE VDI Client.
• Network test tools.
• Ability to adjust audio volume with volume control keys.
• Automounter for CD/DVD disks (to allow CD/DVD redirection to RDP sessions).
• Support for Generic Files (this is a foundation for other upcoming features; PMC 2.7.0 or newer is required to manage this feature).

Other improvements introduced in RX300 firmware version 4.1.5:

• Default peripherals redirection settings optimized based on the selected device operation mode.
• Open Connect VPN (version 8.10) support.
• Simplified FortiNet SSL VPN Client configuration (ability to select a VPN server certificate).
• Enhanced GUI style and layout.
• Improved networking status icon accuracy. 
• ‘Configure…’ shortcut on the Ethernet and Wi-Fi icons.
• Support 2 or more instances to VNC server for screen shadowing.
• Support for remote troubleshooting file generation from PMC Endpoint Manager (2.7.0 and higher).

The following RX300 firmware issues have been fixed in version 4.1.5:

• RX-1971- USB pendrive does not get redirected in RDP session.
• RX-1946 – Disabled ‘windowed screen’ toggling in VERDE (SPICE) connection.
• RX-1920 – Fixed FortiVPN CA Certificate incorrect path.
• RX-1966 – Can’t connect to WiFi with SSID name containing ‘apostrophe’ character.

PREVIOUS RX300 FIRMWARE VERSION 4.0.5 RELEASE NOTES

4.0.5 is a major RX300 firmware release which replaces the 3.10.3 and earlier firmware versions with feature enhancements and bug fixes. This new version comes with several new VPN clients.

Following are the new product features introduced in RX300 firmware version 4.0.5:

• Additional VPN clients:

• L2TP/IPsec VPN client.
• IKEv2/IPsec VPN client.
• FortiClient SSL VPN client.

• Notifications about availability of firmware updates.
• Support for Subnet Tags (when managed by the upcoming PMC 2.6).
• Ability to set up a custom boot splash image.
• Support for the shutdown command sent by vSpace Console.

Other improvements introduced in RX300 firmware version 4.0.5:

• VPN reconnect after plugging in the Ethernet cable.
• NTP date and time update after plugging in the Ethernet cable.
• New default NComputing wallpaper.
• Updated vCAST web streaming components.

The following RX300 firmware issues have been fixed in version 4.0.5:

• RX-1910 – Incorrect calculation of MD5 sums for certificate files added manually.

PREVIOUS RX300 FIRMWARE VERSION 3.10.3 RELEASE NOTES

3.10.3 is a major RX300 firmware release which replaces the 3.9.2 and earlier firmware versions with feature enhancements and bug fixes. This new version comes with the support for native (functional) redirection of webcams.

Following are the new product features introduced in RX300 firmware version 3.10.3:

• Native redirection of webcams in all operation modes (excluding Raspbian Desktop mode).

Other improvements introduced in RX300 firmware version 3.10.3:

• RX-1869 – Prevent the use of native audio channel in UXP mode when audio redirection is not set to Native.

The following RX300 firmware issues have been fixed in version 3.10.3:

• RX-1871 – OpenVPN: Device caches the .ovpn file and user credentials even when not configured to do so.
• RX-1866 – Cracking sound in RDP session when using Zoom application.
• RX-1863 – No sound in USB headset when the headset was connected after a webcam.
• RX-1859 – vSpace Client crash when opening a specific page in web browser running in vSpace session.
• RX-1852 – OpenVPN client is not asking for key password when .ovpn file contains encrypted RSA private key.

PREVIOUS RX300 FIRMWARE VERSION 3.9.2 RELEASE NOTES

3.9.2 is a major RX300 firmware release which replaces the 3.8.1 and earlier firmware versions with feature enhancements and bug fixes. This new version comes with the VERDE VDI Remote Access feature to further enable work-from-home use cases.

Following are the new product features introduced in RX300 firmware version 3.9.2:

• Support for the VERDE VDI Remote Access feature.

Other improvements introduced in RX300 firmware version 3.9.2:

• Reduced Wi-Fi settings application time.
• Improved behavior of the Wi-Fi icon.
• 1270x720 will be set as Automatic resolution when the device will be booted up without any HDMI monitor connected.
• Improved system daemons reloading procedure when applying configuration changes.
• Improved RDP sessions stability by disabling audio redirection when "No audio output/input" is at the top of audio priority list.
• Improved dialog box for selecting USB devices identified by custom VID:PID.

The following RX300 firmware issues have been fixed in version 3.9.2:

• RX-1833 – GUI crash when Ethernet, VPN and PMC were connected and the Ethernet cable was unplugged/plugged. 
• RX-1832 – OpenVPN: The key file specified as parameter of the tls-auth entry of .ovpn file does not get copied from memory stick.
• RX-1828 – The Ethernet interface sometimes get disabled after firmware recovery.

PREVIOUS RX300 FIRMWARE VERSION 3.8.1 RELEASE NOTES

3.8.1 is a major RX300 firmware release which replaces the 3.7.0 and earlier firmware versions with feature enhancements and bug fixes. This new version comes with integrated VPN support to further enable work-from-home use cases.

Following are the new product features introduced in RX300 firmware version 3.8.1:

• Integrated OpenVPN client:

• Supported authentication methods include pre-shared keys, certificate-based, and username/password-based authentications.  

• Integrated OpenConnect VPN client (for connections to Cisco AnyConnect and compatible VPNs):

• Supported authentication methods include certificate-based and username/password-based authentications. 

• Integrated PPTP VPN client supporting username/password-based authentication. 
• Ability to establish vSpace sessions on vSpace Servers using custom UXP port numbers.
• Support for HID DigitalPersona fingerprint readers in vSpace Client, RDP Client, and VERDE VDI Client operation modes.
• Ability to automatically start published RemoteApp resources.
• Reset to factory defaults button. 
• Option to allow/disallow non-ASCII characters in usernames and passwords for RDP and VERDE connection settings.

Other improvements introduced in RX300  firmware version 3.8.1:

• Improved error handling for RDP sessions.
• Country selection for Wi-Fi configuration to enable/disable available Wi-Fi channels.
• Possibility do upload certificate files with any file name extension.

The following RX300 firmware issues have been fixed in version 3.8.1:

• RX-1782 - Fixed the issue where resetting to factory defaults has no effect for keyboard language setting.
• RXRDP-413 – Fixed the issue where Wi-Fi channels 12 and 13 are not visible in Wi-Fi scan results.

• RX-1778 - Fixed a rare issue where the device GUI would get stuck based on certain Ethernet configuration.

PREVIOUS RX300 FIRMWARE VERSION 3.7.0 RELEASE NOTES

RX300 firmware version 3.7.0 carries over all features and enhancements from the previous RX300 firmware version 3.6.6 and earlier releases.

Following are the new product features introduced in RX300 firmware version 3.7.0:

• RXRDP-391 Updated vCast Streaming software component.
• RX-1763 - Enhanced logs collection mechanism to cover more events.
• RX-1769 - Removed hardcoded lowercase() for user and domain in VERDE client binary

The following RX300 firmware issues have been fixed in version 3.7.0:

• RX-1764 - Accented characters in username did not work properly with VERDE login window.
• RX-1762 - Putting RX300 in sleep mode (using power button) for extended period of time with SDA attached will freeze RX300.
• RX-1760 - Local Linux desktop may appear when RDP session contains elements with RGB 5,5,5 color.
• RX-1761 - Session artifacts remain visible on the SDA screen when the device turns off the screen saver.

PREVIOUS RX300 FIRMWARE VERSION 3.6.6 RELEASE NOTES

RX300 firmware version 3.6.6 carries over all features and enhancements from the previous RX300 firmware version 3.6.5 and earlier releases.

Following are the new product features introduced in RX300 firmware version 3.6.6:

• Firmware upgrade option from local USB memory stick (upgrade RX300 firmware versions from 3.6.6 to future higher firmware versions) 

The following RX300 firmware issues have been fixed in version 3.6.6:

• Updated vCAST streaming software component 
• RX-1758 - Cups auto detection 'USB printer identification' string if is empty in configuration 

PREVIOUS RX300 FIRMWARE VERSION 3.6.5 RELEASE NOTES

RX300 firmware version 3.6.5 carries over all features and enhancements from the previous RX300 firmware version 3.6.0 and earlier releases.

Following are the new product features introduced in RX300 firmware version 3.6.5:

• Troubleshooting information collector tool

Other improvements introduced in RX300 firmware version 3.6.5:

• Improved device configuration settings applying routines for PMC
• VERDE client improvement to report more device details to VERDE server

The following RX300 firmware issues have been fixed in version 3.6.5:

• RX-1755 – Inaccurate message about ‘Empty group’ after applying profile from vSpace Console.
• RX-1753 – User authentication may fail in RDP Client mode when user name is specified as UPN.
• RX-1752 – RemoteApp connection fails when RD Session Host is using a non-standard port number.

PREVIOUS RX300 FIRMWARE VERSION 3.6.0 RELEASE NOTES

Following are the new product features introduced in RX300 firmware version 3.6.0:

• 802.1x network authentication support on Ethernet interface.
• Remote Desktop Gateway support for RDP connections.
• Native redirection of ReinerSCT cyberJack smart card readers.
• Support for vSpace for Linux.
• User experience settings for RDP connections.
• Date and time saving on device shutdown and restoring on device bootup.
• History collection for manually entered RemoteApp RD Web Access URLs.

Other improvements introduced in firmware version 3.6.0:

• FreeRDP client updated to the latest stable version.
• Username field validation in Kiosk Mode / User auto-logon configuration.
• Username field auto-population on logon screens.
• Domain field auto-population on RDP/RemoteApp logon screen.
• Improved input fields focusing rules on logon screens.
• Improved error handling when RemoteApp support is enabled.
• Internet Proxy support for VERDE VDI connections.
• Support for ext2, ext3, and ext4 file systems on locally mounted USB storage devices (used for native redirection or installation of certificates).
• Updated NComputing Pi Zero SDA firmware.
• Network connection loss detection for vSpace sessions.
• Increased video playback smoothness during vCAST Media Streaming with VLC player 3.0.6.
• Displaying the wallpaper during firmware update installation.
• Cosmetic changes and spelling improvements in the GUI.

The following RX300 firmware issues have been fixed in version 3.6.0:

• RX-1732 – Dual screen: When using touchscreen as primary display with position set to ‘Second’ and the Pi0 SDA as secondary display the touchscreen events are applied to secondary display.
• RX-1731 – Device fails to connect to PMC through auto-detected address when the DHCP reply is delayed.
• RX-1730 – Possibility to freeze the RX300 device when user presses the Sleep button when the auto-connect countdown reaches zero
• RX-1722 – Unplugging Ethernet when vSpace client is connected to vSpace Server ends with frozen session.
• RX-1715 – Device gets stuck without GUI when HTTP URL will be specified as RD Web Access URL.
• RX-1673 – WiFi interface remains active after scanning WiFi networks.
• RX-1665 – Touchscreen doesn't work when USB SDA adapter is connected.
• RX-1655 – Syslog gets spammed with "'action 17' suspended" messages.
• RX-1654 – Kiosk Mode application and application directory are not excluded from xfreerdp arguments when launching RDP RemoteApp programs.
• RX-1649 – Setup GUI allows saving an empty administrator password.
• RX-1643 – Green LED does not indicate SD card activity anymore after using the sleep/power button to wake the device up from sleep mode.
• RX-1641 – USB composite devices do not redirect into VERDE/RDP sessions (with Incentives Pro VID:PID list redirection)
• RX-1639 – [Dual display] RX300 + Pi0 SDA: session disconnect in less than a minute from logon.
• RX-1631 – Some keyboard shortcuts are blocking mouse and keyboard events.
• RX-1630 – User does not get logged out from RemoteApp list if screen saver action is set to "Disconnect sessions..."
• RX-1629 – ntfs-3g deb package for NTFS filesystem will not be installed if firmware update starts on firmware older than version 3.2.16.
• RX-1628 – Loss of PMC connection after disabling WiFi if autodiscovered PMC address was in use.
• RX-1626 – Device is collecting wallpapers instead of replacing old wallpaper with the new one.
• RX-1619 – VNC screen shadowing stops working after display resolution change.
• RX-1607 – Inability to use VNC if it was turned on at the same time when reconfiguring screen resolution.
• RX-1602 – RemoteApp: All icons presented by task-switcher are identical.
• RX-1595 – vCAST Web Streaming waits in infinite loop on some Vimeo videos.
• RX-1591 – DisplayLink adapter doesn't work after waking the device up from sleep mode.

FIRMWARE UPDATE INSTRUCTIONS:

Important note: The RX300 firmware version 4.4.9 can only be upgraded from RX300 firmware version 4.0.5 or higher version. If you have RX300 firmware version 3.x or 2.x, you must first upgrade to 4.0.5 firmware before you can upgrade again to higher firmware version. This is due to in RX300 firmware version 4.0.5 we eliminated the Raspbian Desktop operation mode and subsequent firmware update is only compatible when upgrading from 4.0.5 or higher firmware version.

Reference link to previous RX300 firmware version 4.0.5:

https://firmware.ncomputing.com/RX300/rx300-4.0.5.upd

The firmware update could take anywhere between 5 and 10 minutes. Please do not turn off your device during this time. Once the firmware update is complete, the device will reboot automatically.  

• Updating firmware from an FTP or web server

The device firmware can be updated manually from the Setup GUI with a firmware update package uploaded to an FTP or web server:

• Upload the ‘rx300-4.4.9.upd’ firmware update package file into your FTP or web server.
• On the RX300 or RX300+ device open the Setup GUI and go to the ‘Support’ section.
• Enter the FTP or HTTP URL of the firmware update package and click the ‘Update’ button.
• Alternatively, user can use the following NComputing’s web URL to download and install this version of firmware directly to the RX300 or RX300+ device.
  

Once the device finishes downloading the firmware update package the firmware update process will start and will take a few minutes. The process should not be interrupted. Especially when the process reaches 76% the progress bar will stop moving for a longer while. This is normal and the update will continue once the background tasks are completed. Firmware update will end with a device reboot.

• Updating firmware from vSpace Console

The device firmware can be updated from the vSpace Console included in vSpace Pro 11 or the vSpace Pro Enterprise Edition. To upgrade the firmware, open vSpace Console and follow the standard firmware update procedure. For devices located in the same LAN as vSpace Pro it is as following:

• Go to ‘Manage Devices’.
• Under Networks select LAN, locate and select the RX300 devices which should receive the firmware update.
• Click the ‘Update Firmware’ button on the toolbar.
• Select the ‘Latest from LAN’ method and click the ‘Update’ button.

Once the device finishes downloading the firmware update package the firmware update process will start and will take a few minutes. The process should not be interrupted. Especially when the process reaches 76% the progress bar will stop moving for a longer while. This is normal and the update will continue once the background tasks are completed. Firmware update will end with a device reboot.

• Updating firmware from PMC Endpoint Manager version 4.1.x (or newer)

The RX300 device requires a separate purchase of either AMP for vSpace Pro  or AMP for VERDE VDI to receive the PMC software license for that device.

Once PMC is registered to NComputing Management Portal, it will auto-detect the PMC licensing allowance for NComputing thin clients, including RX300/RX300+ devices that have been connected to PMC.

The RX300/RX300+ 4.4.9 firmware uses version 25 of the device configuration. To ensure smooth transition and uninterrupted management ability, NComputing suggests updating PMC to version 4.1.0 (or newer) before upgrading the device firmware. Please refer to PMC 4.0.0 Release Notes for the information about PMC updating. To add to PMC the support for RX300/RX300+ devices using configuration version 25, an appropriate PCU file (PMC Configuration Update file) needs to be uploaded to PMC. The necessary PCU file will be distributed together with the RX300/RX300+ firmware.

The device firmware can be updated from supported version of PMC. Follow the below steps to perform the firmware update on remote RX300/RX300+ devices:

• Logon to PMC as a user with administrative privileges, open the Menu, go to ‘Administration > Files’.
• Select ‘Firmware Image’ as file type.
• Click the ‘Choose file’ button and select the ‘rx300-4.4.9.upd’ file.
• Click the ‘Upload file’ button to upload the firmware package.
• In PMC 4.1.0 or newer version:

• Open the Menu, go to ‘Devices’.
• Select the devices which should receive the firmware update.
• Execute the ‘Update Firmware’ task of the Devices list.
• Select the ‘rx300-4.4.9.upd’ firmware package.

• Schedule the update date and time, or opt to update now.
• Click the ‘Apply’ button.

If ‘Update now’ was chosen, then within 30 seconds the device will receive a request to initiate the firmware update. The process can be followed by observing the Audit Events log on Dashboard. The firmware update process will take a few minutes and should not be interrupted. Especially when the process reaches 76% the progress bar will stop moving for a longer while. This is normal and the update will continue once the background tasks are completed. Firmware update will end with a device reboot.

ADDITIONAL NOTES: 

• Authentication methods supported by the VPN clients in 4.4.9 firmware:

• OpenVPN
• Open Connect
• PPTP
• L2TP/IPsec VPN – pre-shared key, username, password.
• IKEv2/IPsec VPN client – client certificate with password.
• FortiClient SSL VPN client – username and password.

• Setting up a custom boot splash image

Only image files in PNG format are supported.

• Managing RX300 devices from PMC

The RX300 device can be optionally managed by the PMC 2.9.4 (or newer) software. This software can be obtained as benefit of separate vSpace Pro AMP or VERDE AMP licenses.

• Managing the RX300 and RX300+ devices with 4.4.9 firmware from PMC

PMC version 4.1.x (or newer) will be necessary to manage RX300 and RX300+ devices. The 4.4.9 firmware uses version 25 of the device configuration when installed on RX300. To ensure smooth transition and uninterrupted management ability, NComputing suggests updating PMC to version 4.1.x (or newer) before upgrading the device firmware. Please refer to PMC 4.1.x Release Notes for the information about PMC updating. 

• PMC server auto-discovery

To automate the PMC server discovery the DHCP option 207 can be used. This DHCP option should provide a string value containing the URL in form of ‘https://<PMC_address>’, like: ‘https://pmc.company.local’, or: ‘https://192.168.10.12’.

• RDP Client connection configuration

The RX300 firmware version 3.4.7 introduced support for RemoteApp and Desktop Connections. The parameters necessary for the RDP Client connection are different depending on the RemoteApp support being enabled or not.

• RemoteApp and Desktop Connections not enabled: The RDP Client connects directly to specified Remote Desktop Session Host. 
• RemoteApp and Desktop Connections enabled: The RDP Client first communicates with the specified Remote Desktop Web Access server (which cooperates with Remote Desktop Connection Broker; both must exist in the RDS deployment). The Remote Desktop Web Access server URL must be specified in RDP Client connection configuration. This URL can be in simplified or full form, e.g.:

• 192.168.50.7 – will be expanded to: https://192.168.50.7/RDweb
• rdwa – will be expanded to: https://rdwa/RDWeb
• rdwa.company.local – will be expanded to: https://rdwa.company.local/RDWeb
• https://rdwa.company.local/RDWeb - will be used as is.

• Using custom parameters for RDP connections

The 3.7.0 firmware and higher versions allow specifying custom parameters for RDP connections. Please refer to FreeRDP documentation (https://github.com/FreeRDP/FreeRDP/wiki/CommandLineInterface) for the information about supported parameters. If multiple custom parameters must be specified then they should be separated by the “;” (semicolon) character.

• Using PMC 2.7.0 (or newer) for device screen shadowing

The software components allowing device screen shadowing from PMC act as yet another VNC viewer application. The VNC screen shadowing feature needs to be enabled on the devices for the PMC screen shadowing feature to work.

• Passcode-based PMC 2.7.0 (or newer) device onboarding

When the ‘Require passcode for device onboarding’ option will be activated under System Settings of PMC 2.7.0, then newly connecting devices will prompt the users to provide the onboarding passcode. Only if the user will provide correct onboarding passcode the device will successfully check-in and will be added to PMC’s database. This is a one-time process only. Already onboarded devices will never prompt users for any onboarding passcode.

• Using the network test tools

The results of network tests will be saved into a temporary file, which will be collected when creating a Troubleshooting File. The device will also execute the network tests when creating the Troubleshooting File on PMC administrator’s request. Appropriate test parameters (address and port) should be configured on the device before requesting the Troubleshooting File with PMC.

• vCAST support in RDP sessions

Support for vCAST Web Streaming and vCAST VLC Media Streaming in RDP sessions started from RX300 devices requires installation of the NComputing SuperRDP Server Pack software on the Remote Desktop machine. The NComputing SuperRDP server pack is available through your reseller (SKU: SuperRDP-PREM-VC-P).

• RX300 supported Secondary Display Adapters

This firmware supports following Secondary Display Adapter (SDA) options:

• NComputing Raspberry Pi Zero (Pi0) SDA

Secondary Display Adapters based on Raspberry Pi Zero are supported.

• DisplayLink SDA

Secondary Display Adapters based on DisplayLink DL-1x0 and DL-1x5 chipsets are supported. DisplayLink  adapters with following USB vendor ID and product ID (VID:PID) are supported:

• 17e9:0290 
• 17e9:0351 
• 17e9:030b 
• 17e9:0377 
• 17e9:0378 
• 17e9:0379 
• 17e9:037a 
• 17e9:037b 
• 17e9:037c 
• 17e9:037d 
• 17e9:410a 
• 17e9:430a 
• 17e9:4312

Device must be rebooted to become properly configured after physically connecting or disconnecting any DisplayLink adapter. Hot-plugging the DisplayLink adapters is not supported.

• NComputing N-series SDA

Secondary Display Adapters based on SMSC/Microchip UFX6000 chip, previously offered by NComputing for the N-series devices, are supported and can be used to extend the full-screen UXP and RDP desktop sessions.

• RX300 Secondary Display Adapters limitations

The Secondary Display Adapters are mainly purposed to allow desktop extension in full-screen vSpace (UXP) and RDP desktop sessions. Certain limitations apply to different scenarios as listed in the following table:

• vCAST limitations

The vCAST Web Streaming and vCAST Media Streaming technologies require the client device to use optimized (hardware-accelerated) display drawing to work properly. As not every Secondary Display Adapter is technically capable to offer the necessary drawing method  following limitations apply to vCAST:

N/A – not applicable

Note: For vCAST support in RDP sessions the SuperRDP software must be installed on the remote machine.

The vCAST Media Streaming technology can only offload to the client device H.264-encoded media contents. For other formats the VLC player needs to have the ‘Windows GDI’ video output selected under Video output settings.

• VNC screen shadowing limitations

The VNC screen shadowing feature is mainly purposed for remote viewing and controlling the local device GUI. When the device is running a terminal session some limitations apply and the screen shadowing might end-up with a black screen being displayed in VNC viewer application. This happens because of the optimized (hardware-accelerated) display drawing methods used in some scenarios. The display data bypasses the traditional frame buffer then and can’t be shadowed with VNC.

N/A – not applicable

• Touchscreen support

Touchscreen monitors are only supported when only one (primary) display is connected.

• Server CPU load in RDP sessions with RemoteFX enabled

Enabling the RemoteFX feature for Remote Desktop connections greatly improves user experience by providing very good GUI performance. This is thanks to optimized algorithms used to encode the areas of the session screen which contain dynamically changing contents (like videos or animations). Ideally the screen encoding on the server side should be accelerated by supported graphics cards. Leveraging server CPUs for RemoteFX screen encoding can cause high load and effectively limit the per-server user density.

• Kiosk mode application auto-start

Latest versions of Windows operating systems favor RemoteApp publishing (which is supported in the 3.7.0 firmware and higher versions) and do not allow launching applications with program paths specified on the client side. This functionality can be re-enabled by modifying the Windows registry:

Registry key: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList
Registry value: REG_DWORD fDisabledAllowList
Registry value data: 1

Registry key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
Registry value: REG_DWORD HonorLegacySettings
Registry value data: 1

• Native (functional) redirection of printers in RDP sessions

Following are the topics to consider when planning to use the native/functional redirection of printers in RDP sessions:

• Locally connected USB printers and network printers supporting the JetDirect protocol (also known as RAW or AppSocket) can be used with native redirection.
• Low-cost GDI printers should be avoided, as they may not work properly. More advanced printers understanding the PCL, PostScript, and/or other high-level page description languages are advisable and should work.
• Functional redirection of printers requires the installation of appropriate Windows printer driver on the remote machine running the RDP session. The literally spelled name of the Windows printer driver must be entered in the ‘Windows printer driver name’ when adding a printer for native redirection. 
• The ‘Windows printer driver name’ often matches the ‘USB printer identification’ string obtained from the USB printer during the detection process, but this is not a general rule. For some USB printers the ‘Windows printer driver name’ automatically populated when detecting the printer will have to be edited to match the real name of the Windows printer driver installed on the remote server. 
• The ‘type 3’ drivers for Windows x64 architecture should be selected for installation. ‘Type 4’ drivers are known to cause issues with functional redirection of printers.
• The list of Windows printer drivers installed on a Windows machine (with the information about class and architecture) can be obtained with the following command executed in Command Prompt:

wmic /NameSpace:\\Root\CIMV2 path Win32_PrinterDriver GET Name

• Native (functional) redirection of webcams in RDP sessions

Native redirection of webcams is only supported in RDP sessions, if the Remote Desktop Session Host is a Windows Server 2019 or a Windows 10 machine. Each user, under Privacy settings, needs to allow the applications to access the redirected camera.

• Native (functional) redirection of webcams in vSpace Client sessions

vSpace Pro Enterprise 12.4 is necessary for the native webcam redirection functionality. Each user, under Privacy settings, needs to allow the applications to access the redirected camera.

• Native (functional) redirection of webcams in VERDE VDI sessions using the UXP protocol

VERDE Guest Tools based on vSpace Pro Enterprise 12.4 are necessary for the native webcam redirection functionality with the UXP protocol. Each user, under Privacy settings, needs to allow the applications to access the redirected camera.

• Native (functional) redirection of smart card readers in RDP and UXP sessions

Functional redirection of smart card readers leverages the PC/SC daemon and smart card reader drives embedded in the device firmware. Please refer to Appendix A for the list of smart card reader drivers contained in RX300 firmware.

• Generic USB redirection of peripheral devices in RDP sessions on Windows Server 2016/2019 and Windows 10

In Windows Server 2016/2019 and Windows 10 the ‘Do not allow supported Plug and Play device redirection’ Group Policy setting is enabled by default (when not configured), which prevents the Generic USB redirection of the peripheral devices to the above mentioned operating systems. This Group Policy setting can be found under ‘Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection’. To be able to use the Generic USB redirection of RX300 peripheral devices in Remote Desktop sessions running on operating systems mentioned in this note this policy must be explicitly disabled. In Windows Server 2012 R2, Windows 8.1 and older Windows server and desktop operating systems the Remote Desktop Services by default allows the redirection of supported plug and play devices, thus the ‘Do not allow supported Plug and Play device redirection’ Group Policy setting does not need to be altered.

• PMC Device Management Quick Start Guide:

NComputing PMC is a device management system designed and developed to remotely manage NComputing access devices. 

Please refer to the PMC Quick Start Guide:

https://support.ncomputing.com/portal/en/kb/articles/pmc-3-0-start-guide

APPENDIX A – LIST OF AVAILABLE SMART CARD READERS DRIVERS

Drivers for following smart card readers are present in the firmware and the following readers should work:

Readers supported by the Reiner SCT cyberJack driver:

• REINER SCT cyberJack pp_a
• REINER SCT cyberJack ecom_a
• REINER SCT cyberJack pp_a2
• REINER SCT cyberJack RFID standard
• REINER SCT cyberJack RFID komfort
• REINER SCT cyberJack compact
• REINER SCT cyberJack go / go plus
• REINER SCT cyberJack wave

Readers supported by the ACS driver:

• ACS ACR32 ICC Reader
• ACS ACR3201 ICC Reader
• ACS ACR33U-A1 3SAM ICC Reader
• ACS ACR33U-A2 3SAM ICC Reader
• ACS ACR33U-A3 3SAM ICC Reader
• ACS ACR33U 4SAM ICC Reader
• ACS ACR38U-CCID
• ACS ACR3801
• ACS ACR39U ICC Reader
• ACS ACR39K ICC Reader
• ACS ACR39T ICC Reader
• ACS ACR39F ICC Reader
• ACS ACR39U ID1 Card Reader
• ACS ACR39U-SAM ICC Reader
• ACS ACR3901 ICC Reader
• ACS ACR83U
• ACS ACR85 PINPad Reader
• ACS ACR88U
• ACS ACR89 ICC Reader
• ACS ACR89 Dual Reader
• ACS ACR89 FP Reader
• ACS ACR100 ICC Reader
• ACS ACR101 ICC Reader
• ACS ACR102 ICC Reader
• ACS ACR122U
• ACS ACR1222 1SAM PICC Reader
• ACS ACR1222 1SAM Dual Reader
• ACS ACR1222 Dual Reader
• ACS ACR1222 1SAM PICC Reader
• ACS ACR1222 3S PICC Reader
• ACS ACR123 3S Reader
• ACS ACR123 PICC Reader
• ACS ACR123US_BL
• ACS ACR125 nPA plus
• ACS ACR1251 1S CL Reader
• ACS ACR1251 CL Reader
• ACS ACR122U
• ACS ACR1251U-C Smart Card Reader
• ACS ACR1251U-C Smart Card Reader
• ACS ACR1251K Dual Reader
• ACS ACR1251 1S Dual Reader
• ACS ACR1251 Reader
• ACS ACR1251 CL Reader
• ACS ACR1252 1S CL Reader
• ACS ACR1252 CL Reader
• ACS ACR1252 USB FW_Upgrade v100
• ACS ACR1252U BADANAMU MAGIC READER
• ACS ACR1252IMP 1S CL Reader
• ACS ACR1255U-J1 PICC Reader
• ACS ACR1256U PICC Reader
• ACS ACR1261 1S Dual Reader
• ACS ACR1261 CL Reader
• ACS ACR128U
• ACS ACR1281 1S Dual Reader
• ACS ACR1281 CL Reader
• ACS ACR1281 Dual Reader
• ACS ACR1281 PICC Reader
• ACS ACR1281 Dual Reader
• ACS ACR1281 PICC Reader
• ACS ACR1281 Dual Reader
• ACS ACR1281 2S CL Reader
• ACS ACR1281 1S PICC Reader
• ACS ACR1281U-K PICC Reader
• ACS ACR1281U-K Dual Reader
• ACS ACR1281U-K 1S Dual Reader
• ACS ACR1281U-K 4S Dual Reader
• ACS ACR1283 4S CL Reader
• ACS ACR1283 CL Reader
• ACS ACR1283U FW Upgrade
• ACS ACR1311 PICC Reader
• ACS AET62 PICC Reader
• ACS AET62 1SAM PICC Reader
• ACS AET65 ICC Reader
• ACS AMR220 Reader
• ACS APG8201
• ACS APG8201-B2
• ACS APG8201Z
• ACS APG8201Z
• ACS CryptoMate64
• ACS CryptoMate (T1)
• ACS CryptoMate (T2)
• ACS ACR38U
• ACS ACR38U-SAM
• ACS AET65 1SAM ICC Reader
• ACS CryptoMate
• IRIS SCR21U

CCID-compliant readers:

• Access IS ePassport Reader
• Access IS NFC Smart Module
• ACS ACR 38U-CCID
• ACS ACR101 ICC Reader
• ACS ACR122U PICC Interface
• ACS ACR1251 Dual Reader
• ACS ACR1252 Dual Reader
• ACS ACR1255U-J1
• ACS ACR3901U ICC Reader
• ACS ACR39U ICC Reader
• ACS APG8201 PINhandy 1
• ACS APG8201 USB Reader
• ACS CryptoMate (T2)
• ACS CryptoMate64
• ActivCard ActivCard USB Reader V2
• ActivIdentity Activkey_Sim
• ActivIdentity USB Reader V3
• AK910 CKey
• AK910 IDONE
• Aktiv Co., ProgramPark Rutoken Magistra
• Aktiv PINPad Ex
• Aktiv PINPad In
• Aktiv Rutoken ECP
• Aktiv Rutoken lite
• Aktiv Rutoken PINPad 2
• Aladdin R.D. JaCarta
• Aladdin R.D. JaCarta Flash
• Aladdin R.D. JaCarta LT
• Aladdin R.D. JaCarta U2F (JC602)
• Aladdin R.D. JCR-770
• Aladdin R.D. JC-WebPass (JC600)
• Alcor Micro AU9520
• Alcor Micro AU9522
• Alcor Micro AU9560
• ANCUD CCID USB Reader & RNG
• appidkey GmbH ID100L-USB-SC-Reader
• appidkey GmbH ID50 -USB
• appidkey GmbH ID60-USB
• ASK-RFID CPL108
• Athena ASE IIIe
• Athena ASEDrive IIIe Combo Bio PIV
• Athena ASEDrive IIIe KB
• Athena ASEDrive IIIe KB Bio PIV
• Athena IDProtect Flash
• Athena IDProtect Key v2
• ATMEL AT90SCR050
• ATMEL AT90SCR100
• ATMEL AT91SC192192CT-USB ICCD reader
• ATMEL AT91SO CCID Smart Card Reader
• ATMEL AT98SC032CT-USB
• ATMEL VaultIC420 Smart Object
• ATMEL VaultIC440
• ATMEL VaultIC460
• Avtor SC Reader 371
• Avtor SecureToken
• Axalto Reflex USB v3
• BIFIT iBank2Key
• BIFIT iToken
• BIFIT USB-Token iBank2key
• Bit4id CKey4
• Bit4id cryptokey
• Bit4id Digital DNA Key
• Bit4id iAM
• Bit4id miniLector
• Bit4id miniLector-s
• Bit4id tokenME FIPS v3
• BLUTRONICS BLUDRIVE II CCID
• Broadcom Corp 5880
• C3PO KBR36
• C3PO LTC31 v2
• C3PO LTC32
• C3PO LTC36
• C3PO LTC3x USB
• C3PO TLTC2USB
• CASTLES EZCCID Smart Card Reader
• CCB eSafeLD
• charismathics plug'n'crypt CCID token
• Cherry GmbH SmartBoard XX1X
• Cherry GmbH SmartBoard XX33
• Cherry GmbH SmartBoard XX44
• Cherry GmbH SmartTerminal ST-1275
• Cherry GmbH SmartTerminal ST-2xxx
• Cherry GmbH SmartTerminal XX1X
• Cherry GmbH SmartTerminal XX44
• Cherry KC 1000 SC
• Cherry KC 1000 SC Z
• Cherry KC 1000 SC/DI
• Cherry KC 1000 SC/DI Z
• Cherry Smart Card Reader USB
• Cherry Smartcard Keyboard G87-1xx44
• Cherry SmartTerminal XX44
• Cherry TC 1300
• Chicony HP USB Smartcard CCID Keyboard JP
• Chicony HP USB Smartcard CCID Keyboard KR
• Chicony USB Smart Card Keyboard
• COVADIS ALYA
• COVADIS Auriga
• COVADIS VEGA-ALPHA
• Dell Dell Smart Card Reader Keyboard
• Dell keyboard SK-3106
• DUALi DE-620 Combi
• DUALi DRAGON NFC READER
• eID_R6 001 X8
• Elatec TWN4 SmartCard NFC
• Elatec TWN4/B1.06/CPF3.05/S1SC1.32/P (Beta 3)
• ESMART Token GOST
• Eutron Card Reader
• Eutron CryptoIdentity CCID
• Eutron Digipass 860
• Eutron Smart Pocket
• Feitian 502-CL
• Feitian bR301
• Feitian bR500
• Feitian eJAVA Token
• Feitian ePass2003
• FEITIAN iR301
• Feitian R502
• Feitian SCR301
• Feitian Technologies FT SCR310
• Feitian VR504 VHBR Contactless & Contact Card Reader
• Free Software Initiative of Japan Gnuk
• FT CCID
• FT CCID KB
• FT ePass2003Auto
• FT U2F CCID
• FT U2F CCID KB
• Fujitsu Siemens Computers SmartCard Keyboard USB 2A
• Fujitsu Siemens Computers SmartCard USB 2A
• Fujitsu Smartcard Reader D323
• FujitsuTechnologySolutions GmbH Keyboard KB100 SCR
• FujitsuTechnologySolutions GmbH Keyboard KB100 SCR eSIG
• FujitsuTechnologySolutions GmbH Smartcard Keyboard G87-914x
• FujitsuTechnologySolutions GmbH SmartCase KB SCR eSIG
• GEMALTO CT1100
• Gemalto EZIO CB+
• Gemalto Ezio Shield
• Gemalto Ezio Shield Branch Reader
• Gemalto Ezio Shield Secure Channel
• Gemalto Gem e-Seal Pro USB Token
• Gemalto GemCore SIM Pro Smart Card Reader
• Gemalto GemPC Express
• Gemalto Gemplus USB SmartCard Reader 433-Swap
• Gemalto Hybrid Smartcard Reader
• Gemalto IDBridge K3000
• Gemalto PC Twin Reader
• Gemalto PDT
• Gemalto Prox Dual USB PC Link Reader
• Gemalto Prox SU USB PC LinkReader
• Gemalto SA .NET Dual
• Gemalto Smart Enterprise Guardian Secure USB Device
• Gemalto USB GemPCPinpad SmartCard Reader
• Gemalto USB Shell Token V2
• Gemplus GemCore POS Pro Smart Card Reader
• Generic MultiCard Device
• Generic Smart Card Reader Interface
• Generic USB Smart Card Reader
• Generic USB2.0-CRW
• German Privacy Foundation Crypto Stick v1.2
• Giesecke & Devrient GmbH Star Sign Card Token 350 (ICCD)
• Giesecke & Devrient GmbH Star Sign Card Token 550 (ICCD)
• Giesecke & Devrient GmbH StarSign Crypto USB Token
• Giesecke & Devrient GmbH StarSign CUT S
• GIS Ltd SmartMouse USB
• GoldKey Security PIV Token
• HDZB uKeyCI800-K18
• Hewlett Packard HP USB Smartcard CCID Keyboard
• Hewlett Packard MFP Smart Card Reader
• Hewlett-Packard Company HP USB CCID Smartcard Keyboard
• Hewlett-Packard Company HP USB Smart Card Keyboard
• Hewlett-Packard HP lt4112 Gobi 4G Module
• HID Global OMNIKEY 3x21 Smart Card Reader
• HID Global OMNIKEY 5022 Smart Card Reader
• HID Global OMNIKEY 5122 Dual
• HID Global OMNIKEY 5122 Smartcard Reader
• HID Global OMNIKEY 5422 Smartcard Reader
• HID Global OMNIKEY 6121 Smart Card Reader
• HID Global veriCLASS Reader
• HID OMNIKEY 5025-CL
• HID OMNIKEY 5127 CK
• HID OMNIKEY 5326 DFR
• HID OMNIKEY 5427 CK
• Hitachi, Ltd. Hitachi Biometric Reader
• Hitachi, Ltd. Hitachi Portable Biometric Reader
• id3 Semiconductors CL1356A_HID
• id3 Semiconductors CL1356T
• Identiv @MAXX ID-1 Smart Card Reader
• Identiv @MAXX Light2 token
• Identiv CLOUD 2980 F Smart Card Reader
• Identiv SCR3500 A Contact Reader
• Identiv SCR3500 B Contact Reader
• Identiv SCR35xx USB Smart Card Reader
• Identiv uTrust 2900 R Smart Card Reader
• Identiv uTrust 2910 R Smart Card Reader
• Identiv uTrust 2910 R Taglio SC Reader
• Identiv uTrust 3512 SAM slot Token
• Identiv uTrust 3522 embd SE RFID Token
• Identiv uTrust 3700 F CL Reader
• Identiv uTrust 3701 F CL Reader
• Identiv uTrust 4701 F Dual Interface Reader
• Identive CLOUD 2700 F Smart Card Reader
• Identive CLOUD 2700 R Smart Card Reader
• Identive CLOUD 4000 F DTC
• Identive CLOUD 4500 F Dual Interface Reader
• Identive CLOUD 4510 F Contactless + SAM Reader
• Identive SCT3522CC token
• Identive Technologies Multi-ISO HF Reader - USB
• IID AT90S064 CCID READER
• IIT E.Key Almaz-1C
• IIT E.Key Crystal-1
• InfoThink IT-102MU Reader
• INGENICO Leo
• Ingenico WITEO USB Smart Card Reader
• Inside Secure AT90SCR050
• Inside Secure AT90SCR100
• Inside Secure AT90SCR200
• INSIDE Secure VaultIC 405 Smart Object
• Inside Secure VaultIC 420 Smart Object
• Inside Secure VaultIC 440 Smart Object
• INSIDE Secure VaultIC 441 Smart Object
• Inside Secure VaultIC 460 Smart Object
• IonIDe Smartcard Reader
• KACST HSID Reader
• KACST HSID Reader Dual Storage
• KACST HSID Reader Single Storage
• Kapsch TrafficCom USB SAM reader
• KEBTechnology KONA USB SmartCard
• Kingtrust Multi-Reader
• KOBIL EMV CAP - SecOVID Reader III
• KOBIL KAAN Advanced
• KOBIL KAAN Base
• KOBIL KAAN SIM III
• KOBIL Systems IDToken
• KOBIL Systems mIDentity 4smart
• KOBIL Systems mIDentity 4smart AES
• KOBIL Systems mIDentity fullsize
• KOBIL Systems mIDentity fullsize AES
• KOBIL Systems mIDentity M
• KOBIL Systems mIDentity visual
• KOBIL Systems mIDentity XL
• KOBIL Systems Smart Token
• KRONEGGER Micro Core Platform
• KRONEGGER NFC blue Reader Platform
• Ledger Nano S
• Lenovo Integrated Smart Card Reader
• Lenovo Lenovo USB Smartcard Keyboard
• Liteon HP SC Keyboard - Apollo (Liteon)
• Liteon HP SC Keyboard - Apollo JP (Liteon)
• Liteon HP SC Keyboard - Apollo KR (Liteon)
• Macally NFC CCID eNetPad
• mCore SCard-Reader
• Microchip SEC1110
• Microchip SEC1210
• MK Technology KeyPass S1
• Morpho MSO1350 Fingerprint Sensor & SmartCard Reader
• Morpho MSO350/MSO351 Fingerprint Sensor & SmartCard Reader
• MSI StarReader SMART
• MYSMART MySMART PAD V2.0
• Neowave Weneo
• Nitrokey Nitrokey HSM
• Nitrokey Nitrokey Pro
• Nitrokey Nitrokey Start
• Nitrokey Nitrokey Storage
• NTT Communications Corp. SCR3310-NTTCom USB SmartCard Reader
• NXP Pegoda 2 N
• NXP PR533
• O2 Micro Oz776
• OBERTHUR TECHNOLOGIES ID-ONE TOKEN SLIM v2
• OCS ID-One Cosmo Card USB Smart Chip Device
• OMNIKEY 5421
• OMNIKEY 6321 CLi USB
• OMNIKEY AG 3121 USB
• OMNIKEY AG 6121 USB mobile
• OMNIKEY AG CardMan 3121
• OMNIKEY AG CardMan 3621
• OMNIKEY AG CardMan 3821
• OMNIKEY AG CardMan 5121
• OMNIKEY AG CardMan 5125
• OMNIKEY AG CardMan 6121
• OMNIKEY AG Smart Card Reader
• OMNIKEY CardMan 1021
• OMNIKEY CardMan 4321
• OMNIKEY CardMan 5321
• Panasonic Panasonic USB Smart Card Reader 7A-Smart
• Philips Semiconductors JCOP41V221
• Philips Semiconductors SmartMX Sample
• PIVKey T800
• Planeta RC700-NFC CCID
• Precise Biometrics Precise 200 MC
• Precise Biometrics Precise 250 MC
• Precise Biometrics Sense MC
• Raritan D2CIM-DVUSB VM/CCID
• Regula RFID Reader
• REINER SCT cyberJack go
• REINER SCT cyberJack one
• REINER SCT cyberJack RFID basis
• REINER SCT cyberJack RFID standard
• REINER SCT tanJack Bluetooth
• Rocketek RT-SCR1
• RSA RSA SecurID (R) Authenticator
• SafeNet eToken 5100
• SafeNet eToken 5300
• SafeNet eToken 7300
• SafeTech SafeTouch
• SAFETRUST SABRE SCR
• SchlumbergerSema SchlumbergerSema Cyberflex Access
• SCM Microsystems Inc. HP USB Smartcard Reader
• SCM Microsystems Inc. SCL010 Contactless Reader
• SCM Microsystems Inc. SCL01x Contactless Reader
• SCM Microsystems Inc. SCR 331
• SCM Microsystems Inc. SCR 3310
• SCM Microsystems Inc. SCR 3311
• SCM Microsystems Inc. SCR 331-DI
• SCM Microsystems Inc. SCR 335
• SCM Microsystems Inc. SCR 355
• SCM Microsystems Inc. SCR3310 USB Smart Card Reader
• SCM Microsystems Inc. SCR331-DI USB Smart Card Reader
• SCM Microsystems Inc. SCR3320 - Smart Card Reader
• SCM Microsystems Inc. SCR3340 - ExpressCard54 Smart Card Reader
• SCM Microsystems Inc. SCR33x USB Smart Card Reader
• SCM Microsystems Inc. SDI010 Smart Card Reader
• SCM Microsystems Inc. SDI011 Contactless Reader
• SCM Microsystems Inc. SPR 532
• Secure Device Solutions DOMINO-Key TWIN
• SecuTech SecuTech Token
• Sitecom Sitecom USB simcard reader MD-010
• Softforum Co., Ltd XecureHSM
• SpringCard CrazyWriter
• SpringCard CSB6 Basic
• SpringCard CSB6 Secure
• SpringCard CSB6 Ultimate
• SpringCard EasyFinger Standard
• SpringCard EasyFinger Ultimate
• SpringCard H512 Series
• SpringCard H663 Series
• SpringCard NFC'Roll
• SpringCard Prox'N'Roll
• Spyrus Inc PocketVault P-3X
• SYNNIX STD200
• Teridian Semiconductors TSC12xxFV.09
• THRC Smart Card Reader
• THURSBY SOFTWARE TSS-PK1
• TianYu CCID Key TianYu CCID SmartKey
• Tianyu Smart Card Reader
• Todos Argos Mini II
• Todos CX00
• ubisys 13.56MHz RFID (CCID)
• udea MILKO V1.
• Unicept GmbH AirID USB
• Unicept GmbH AirID USB Dongle
• Validy TokenA sl vt
• VASCO DIGIPASS 870
• VASCO DIGIPASS 875
• VASCO DIGIPASS 920
• VASCO DIGIPASS KEY 101
• VASCO DIGIPASS KEY 200
• VASCO DIGIPASS KEY 202
• VASCO DIGIPASS KEY 860
• VASCO DP855
• VASCO DP865
• VASCO DP905v1.1
• Verisign Secure Storage Token
• Verisign Secure Token
• VMware Virtual USB CCID
• WatchCNPC USB CCID Key
• Watchdata USB Key
• Watchdata W5181 
• Winbond CCID SmartCard Controller
• XIRING Leo v2
• XIRING MyLeo
• XIRING XI-SIGN USB V2
• Yubico Yubikey 4 CCID
• Yubico Yubikey 4 OTP+CCID
• Yubico Yubikey 4 OTP+U2F+CCID
• Yubico Yubikey 4 U2F+CCID
• Yubico Yubikey NEO CCID
• Yubico Yubikey NEO OTP+CCID
• Yubico Yubikey NEO OTP+U2F+CCID
• Yubico Yubikey NEO U2F+CCID