RX420(RDP)|RX440(RDP)|RX-RDP+ Thin Clients

Designed and optimized for Microsoft (AVD, Windows 365, RDS), and NComputing (vSpace Pro and VERDE)

ABOUT THE PRODUCT

The RX420(RDP) and RX440(RDP) cloud-ready thin clients are built on the Raspberry Pi 4B platform with integrated 2GB and 4GB system RAM, respectively. They bring premium performance and native dual display support, providing a rich PC-like experience in an affordable, energy saving device with a small footprint. They also come with integrated local Chromium browser to provide additional flexibility such as web kiosk mode or productivity mode with direct access of web content and web apps without desktop virtualization. 

The RX-RDP+ cloud-ready thin client is built on the Raspberry Pi 3B+ platform. The device brings great performance with an affordable budget for single display computing.

These RX-series thin clients are designed for Microsoft (RDS, AVD, Windows 365) and NComputing (vSpace Pro Enterprise, VERDE VDI and Remote Access), delivering a secure computing environment to access virtual desktops and virtual apps. 

Both RX420(RDP) and RX440(RDP) thin clients come with integrated local Chromium browser support, providing additional flexibility such as web kiosk mode or productivity mode with direct access to web content and web apps without desktop virtualization.

These RX-series thin clients can be remotely managed by the IT admin via NComputing PMC Endpoint Manager. RX-series thin clients provide a simple-to-deploy, centrally managed, high-performance virtual desktop, perfect for use in SMB and SME organizations with DaaS or VDI deployment.

Features highlights:

• Microsoft Teams optimization support for Microsoft AVD (Azure Virtual Desktop), Windows 365, and RDP sessions, ensuring a seamless video conference experience.
• Native dual display support for RX420(RDP) and RX440(RDP); single display for RX-RDP+
• Multimedia enhancement through Microsoft RemoteFX
• Microsoft Windows 365 Cloud PC, Microsoft AVD, Microsoft RDS, VERDE VDI & Remote Access, vSpace Pro Enterprise, and Virtual Cable UDS Enterprise DaaS and VDI support
• NComputing vCAST Streaming technology with SuperRDP software (separate license required)
• Broad USB peripherals support
• Multi-touch screen support (up to 10 fingers) on primary display
• Manageability with PMC Endpoint Manager software
• Gigabit Ethernet or built-in 2.4/5GHz Wi-Fi network connectivity
• Low cost of ownership and low power consumption

SUPPORTED VIRTUAL DESKTOP ENVIRONMENTS

• Microsoft Azure Virtual Desktop (AVD)

• Deployments in Azure Commercial Cloud

• AVD (ARM-based) – formerly known as Spring 2020 release
• AVD (Classic) – formerly known as Fall 2019 release

• Deployments in Azure Government Cloud

• Microsoft Windows 365 – Cloud PC
• Microsoft Remote Desktop Services (RDS)

• Microsoft Windows Server systems:

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

• Microsoft Windows desktop systems:

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

• NComputing VERDE VDI, VERDE Secure Browser, and VERDE Remote Access (version 8.2.8 or higher)
• NComputing vSpace Pro Enterprise (version 12.9.1 or higher)

• Added support for the new ‘UXP Turbo (H.264)’ protocol.

• Virtual Cable 

• UDS Enterprise 4.0

SUPPORTED APPLICATIONS

Following desktop virtualization clients are present in RX420(RDP), RX440(RDP) and RX-RDP+ devices:

• AVD Client (for AVD and Windows 365) 
• RDP Client
• VERDE VDI Client
• vSpace Client
• Virtual Cable UDS Enterprise Client

RX-series device firmware also comes with a integrated local application support for extended functionality without solely relying on the desktop virtualization environment. The built-in local application is:

• Chromium browser - available on RX420(RDP), RX440(RDP), but not on RX-RDP+

AZURE VIRTUAL DESKTOP AND WINDOWS 365 CLIENT FEATURES

• Multi-Factor Authentication (MFA) and conditional MFA support
• Support for RemoteApp programs and desktops
• Kiosk mode auto-login
• Audio/video (AV) Optimization support for Microsoft Teams in Azure Virtual Desktop (AVD), Windows 365, and RDP sessions
• RDP Shortpath (UDP-based transport protocol)
• Support for peripheral devices:

• USB webcams
• USB and network printers
• USB mass storage devices
• Digital (HDMI, DisplayPort, S/PDIF), analog, USB audio
• USB smart card readers and security keys (support for in-session authentication)
• Multi-touch touchscreens support
• Other USB devices through Generic USB redirection

• Clipboard redirection support
• Native dual display support with independent screen rotation
• Please refer to the ‘RX-Series Thin Client AVD and Windows 365 Setup Guide’ for step-by-step procedures.

VIRTUAL CABLE UDS ENTERPRISE CLIENT FEATURES

• UDS Enterprise Client for Linux (version 4.0) integration
• Support for UDS Enterprise virtual applications and desktops
• Support for Microsoft Teams optimization (audio/video) when using AVD client type in RDP sessions
• Support for peripheral devices:

• USB webcams
• USB and network printers
• USB mass storage devices
• Digital (HDMI, DisplayPort, S/PDIF), analog, USB, and Bluetooth audio (beta preview)
• USB smart card readers and security keys 
• Multi-touch touchscreens
• Other USB devices through Generic USB redirection

• Native dual display support with independent screen rotation
• Please refer to the ‘Getting Started with LEAF OS for UDS Enterprise’ for step-by-step procedures.

INTEGRATED VPN CLIENTS

• OpenVPN, OpenConnect VPN, PPTP, IPSec/L2TP, IPSec/IKEv2, and FortiClient SSL VPN

SUPPORTED ENDPOINT MANAGEMENT SYSTEMS

• Device configuration version used by this RX540 and RX580 version:

This firmware utilizes a corresponding device configuration version when operating on the RX-RDP+, RX420(RDP), and RX440(RDP). The PMC configuration update (PCU) file equips PMC with the necessary information to effectively manage this firmware version.

• PMC Endpoint Manager (version 4.1 or higher):

RX420(RDP), RX440(RDP) and RX-RDP+ device license comes with a perpetual license to use PMC Endpoint Manager. RX420(RDP), RX440(RDP) and RX-RDP+ devices can be easily configured using PMC Endpoint Manager software. An admin can remotely manage RX420(RDP), RX440(RDP) and RX-RDP+ devices over local and wide-area networks, including locations behind firewalls and NAT-routers through an easy-to-use, web-based user interface. 

PMC comes with automatic discovery, check-in, and configuration provisioning of new devices, making the deployment easy. Administrators can setup device profiles with all settings and configurations, then assign the profiles to groups of devices. Only a few clicks are needed to schedule device firmware updates, access the summary dashboard or view the detailed event logging. Users are always up-to-date with the latest technology.

• vSpace Console (only available in vSpace Pro Enterprise desktop virtualization):

Included in the vSpace Pro Enterprise Edition release (version 12.9.1 or higher). vSpace Console can manage a subset of RX420(RDP), RX440(RDP) and RX-RDP+ device configuration related to vSpace configuration parameters and provide integrated user session management of RX420(RDP), RX440(RDP) and RX-RDP+ devices (e.g. Multi-View, remote view, take over, message, stop/pause). 

FIRMWARE UPDATE INSTRUCTIONS

The firmware update (including the download of firmware package) can take a few minutes. Please do not turn off your device during this time. Once the firmware update is complete, the device will reboot automatically.  

• Updating the firmware locally

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

• For FTP or web server (URL):

• Upload the firmware update package file (.upd) into your FTP or web server.
• On the RX420(RDP), RX420(RDP), and RX-RDP+ 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.

• For a locally connected USB memory stick:

• Download the latest .upd file and save it to a USB memory stick.
• Insert the USB stick to RX420(RDP), RX440(RDP), or RX-RDP+.
• On the RX420(RDP), RX440(RDP), or RX-RDP+ device, open the Setup GUI and go to the ‘Support’ section.
• Select ‘Update from the USB memory stick’ radio-button, select the firmware update file displayed in the pop-up, and click the ‘Update button’.

Once the device finishes downloading the firmware update package, the firmware update process will start and will take a while (around half a minute). The process should not be interrupted. Firmware update will end with a device reboot.

• Updating firmware from PMC 

The device firmware can be updated from any version of PMC. Follow the below steps to perform the firmware update on remote RX420(RDP), RX440(RDP), and RX-RDP+ 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 latest .upd file.
• Click the ‘Upload file’ button to upload the firmware package.
• In PMC 4.1 or newer:

• 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 latest .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. For remote devices the process can be followed by observing the Audit Events log on Dashboard. The firmware update process will take a while and should not be interrupted. Firmware update will end with a device reboot.

ADDITIONAL NOTES

AVD, Windows 365 and RDP clients related:

• AVD Client connection configuration

The RX420(RDP), RX440(RDP) and RX-RDP+ firmware supports connections to Microsoft Azure Virtual Desktop deployments hosted in Microsoft Azure cloud. When the AVD Client will be added to Applications list, then, under Application Settings, the AVD release version matching customer’s deployment(s) should be selected. The ARM-based or Windows 365 (formerly known as Spring 2020) AVD release will be selected by default. The AVD Classic (Fall 2019) or Azure Government releases can be selected alternatively.

• Accessing published AVD resources

After logging into the AVD account, user will be presented with a list of AVD published resources. The resource listing can be expanded or collapsed by clicking at the top-level category. Double-clicking on any RemoteApp or desktop icon allows launching the resource. The taskbar at the bottom of the screen can be used to manage multiple opened applications.

• AVD Client connection in Kiosk Mode

The Kiosk Mode settings allow the user to automatically login to his/her AVD account and, if required, automatically launch a particular Windows application or desktop. 

The Domain field allows pre-configuration of the Azure Active Directory domain name. Preconfiguring a domain name will simplify user logon, as the user will only need to provide their names, without the ‘@domain name…’ suffix. Please note that multifactor authentication (MFA) is not supported when Kiosk Mode is enabled.

• Using the RX420(RDP), RX440(RDP) or RX-RDP+ device as Windows 365 Cloud PC client

In the AVD Client application, under Application Settings, the AVD (ARM-based) or Windows 365 release needs to be selected to be able to connect to Microsoft Windows 365 Cloud PC.

• Microsoft Teams optimization  (audio/video) in AVD, Windows 365, and RDP sessions

In optimized Microsoft Teams application, audio and video streams are offloaded from the virtual desktop or remote desktop session and processed locally on the client device. This helps reduce network bandwidth usage and improves overall user experience by minimizing latency and providing smoother video conferencing.

To enable Teams AV optimization, both server-side and client-side needs to be configured.

Server-side configuration: 

• Refer to “Use Microsoft Teams on AVD” document for the information.
• For Microsoft Teams audio/video optimization in AVD, Windows 365, and RDP sessions:

• Following registry key needs to be created prior to Teams installation: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams
• Following value must exist in the Teams key: 
  IsWVDEnvironment (DWORD) = 1
• Remote Desktop WebRTC Redirector version 1.50 or higher must be installed. The latest version can be found on the Microsoft website here.  The WebRTC Redirector Service is a necessary component to optimize the Microsoft Teams experience on Windows AVD, Windows 365, and Remote Desktop Services.

Client-side configuration:

• For AVD and Windows 365 connections:

• In AVD Client application, under Application Settings, select the Enable Microsoft Teams optimization checkbox.

• For RDP connections:

• In RDP Client application, under Application Settings, select AVD as Client type and select the Enable Microsoft Teams optimization checkbox.

• Support for AAC audio codec in AVD client
  The AAC (Advanced Audio Coding) audio codec reduces the amount of audio data sent from the session host to AVD client when playing audio. This can be beneficial for audio latency sensitive applications (e.g., VoIP, WebRTC, etc.) By default, the PCM (Pulse Code Modulation) audio codec is used by the AVD client. PCM codec requires more network bandwidth to transmit the audio data.

To enable the AAC audio codec:

• For AVD and Windows 365 connections:

• In AVD Client application, under Application Settings, select the Enable AAC audio codec checkbox.

• For RDP connections:

• In RDP Client application, under Application Settings, choose AVD as Client type and select the Enable AAC audio codec checkbox.

• RDP Shortpath support (direct UDP-based transport) for AVD and Windows 365 sessions
  The RDP Shortpath feature enables direct, UDP-based, transport between the AVD client and the AVD or Windows 365 session host. Thanks to reduced overhead of the UDP protocol, RDP Shortpath greatly enhances overall user experience.

To enable RDP Shortpath, both server-side and client-side needs to be configured.

Server-side configuration: 

• Refer to “Configure RDP Shortpath for AVD” document for the information.

Client-side configuration:

• In AVD Client application, under Application Settings, select the Enable RDP Shortpath checkbox.

• Clipboard redirection support for AVD and Windows 365 clients can be enabled or disabled in AVD settings.
• RDP Client connection configuration

The RX420(RDP), RX440(RDP) and RX-RDP+ firmware supports 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 application configuration. This URL can be entered 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.

• Ability to select RDP client type 

The AVD client can be used for on-prem RDP connections. Users can benefit from the features which are available in the AVD client (which is based on official Microsoft Linux client SDK), but absent in the standard RDP client, especially from Microsoft Teams Optimization.

• Using custom parameters for RDP connections

The RX420(RDP), RX440(RDP) and RX-RDP+ firmware allows specifying custom parameters for RDP connections. If multiple custom parameters must be specified then they should be separated by the “;” (semicolon) character.

Note: Custom parameters can be specified separately for the RDP and AVD client type selections. The syntax of the custom parameters for both client types is different. Please refer to FreeRDP documentation for the information about supported parameters for the RDP client type selection: https://github.com/FreeRDP/FreeRDP/wiki/CommandLineInterface

• RD Session Host, AVD, and Windows 365 virtual machine configuration for best user experience

The RDP and AVD clients integrated in RX420(RDP), RX440(RDP) and RX-RDP+ devices support the use of H.264/AVC encoding (Advanced Video Codec) in RDP, AVD and Windows 365 sessions. Using AVC ensures the best user experience. To take advantage of this H.264/AVC graphics mode, following Group Policy setting must be enabled: 

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment: Prioritize H.264/AVC 444 graphics mode for Remote Desktop Connections. 

This Group Policy setting can be deployed through Active Directory Group Policy Objects or, in simplest case, it can be configured on the local machine with Local Group Policy Editor (gpedit.msc).

Refer to this KB article on how to setup.

• RD Session Host, AVD and Windows 365 virtual machine configuration for webcam redirection

The RDP and AVD clients integrated in RX420(RDP), RX440(RDP) and RX-RDP+ devices support the native (functional) redirection of USB webcams. To ensure proper webcam redirection, please make sure that the following Group Policy setting is not enabled:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection: Do not allow video capture redirection

This Group Policy setting can be deployed through Active Directory Group Policy Objects or, in simplest case, it can be configured on the local machine with Local Group Policy Editor (gpedit.msc).

Additionally, each user under Settings > Privacy > Camera, needs to allow the applications to access the camera. 

Note: Webcams described as driverless Windows webcams (webcam not requiring any special vendor drivers to work on Windows) or Video for Linux version 2 compliant webcams should work. To preserve the network bandwidth when using redirected webcams, the device firmware tries to use the H.264 encoder to compress the webcam’s video stream before sending it to RDP or AVD session.

• RD Session Host, AVD and Windows 365 virtual machine configuration for printers redirection

The RDP and AVD clients integrated in RX420(RDP), RX440(RDP) and RX-RDP+ devices support the native (functional) redirection of local printers. USB and network printers are supported. To ensure proper printers redirection, please make sure that the following Group Policy setting is not enabled:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection: Do not allow client printer redirection

Printer drivers appropriate for the redirected printers must be installed on the RD Session Host, AVD or Windows 365 VM for successful printers redirection. ‘x64, Type 3 – User Mode’ printer drivers need to be installed. The ‘Remote Desktop Easy Print’ driver cannot be used with printers redirected from RX420(RDP), RX440(RDP) and RX-RDP+ thin clients. To prevent the attempts to use this unsupported driver, the following Group Policy setting can be disabled in Computer Configuration or User Configuration:

Computer/User Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection: Use Remote Desktop Easy Print printer driver first

The above mentioned Group Policy settings can be deployed through Active Directory Group Policy Objects or, in simplest case, they can be configured on the local machine with Local Group Policy Editor (gpedit.msc).

Following are the topics to consider when planning to use the native/functional redirection of printers in RDP, AVD or Windows 365 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 field when adding a printer for native redirection. 
• Even though the Windows printer driver name often matches the USB printer identification string obtained from the USB printer during the detection process, 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

• RD Session Host, AVD and Windows 365 virtual machine configuration for smart cards redirection

The RDP and AVD clients integrated in RX420(RDP), RX440(RDP) and RX-RDP+ devices support the native (functional) redirection of smart cards (smart card readers). CCID-compliant, ReinerSCT and ACS smart card readers are supported. To ensure proper smart cards redirection, please make sure that the following Group Policy setting is not enabled:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection: Do not allow smart card device redirection

This Group Policy setting can be deployed through Active Directory Group Policy Objects or, in simplest case, it can be configured on the local machine with Local Group Policy Editor (gpedit.msc).

• RD Session Host, AVD and Windows 365 virtual machine configuration for Generic USB redirection of peripheral devices

The RDP and AVD clients integrated in RX420(RDP), RX440(RDP) and RX-RDP+ devices support the Generic USB redirection of peripheral devices. In latest Windows Server and Windows desktop operating systems, 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. 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 RX540 and RX580 peripheral devices, this policy must be explicitly disabled. This Group Policy setting can be deployed through Active Directory Group Policy Objects or, in simplest case, it can be configured on the local machine with Local Group Policy Editor (gpedit.msc).

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.

• Server CPU load in RDP 8 sessions with RemoteFX enabled

Enabling the RemoteFX feature for Remote Desktop connections greatly improves user experience in legacy Windwos OS versions 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  and do not allow launching applications with executable 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

Published RemoteApp program or desktop will be automatically started when program or desktop name will be specified as Application in RDP Client application’s Kiosk Mode settings.

• vCAST support in RDP sessions

Support for vCAST Web Streaming and vCAST VLC Media Streaming in RDP sessions started from RX420(RDP), RX440(RDP) and RX-RDP+ 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).

• vCAST limitations

The vCAST Web Streaming and vCAST Media Streaming technologies require the client device to use optimized display drawing to work properly. Such optimized drawing methods are only available when the terminal session runs in full-screen desktop mode. For that reason, vCAST is not supported in published RemoteApp programs. RemoteApp desktop sessions run in full-screen mode and support vCAST.

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.

vSpace Pro Client and VERDE VDI Client related:

• Connecting to vSpace Pro Enterprise servers

vSpace Client connections from RX420(RDP), RX440(RDP) and RX-RDP+ devices are only supported on latest vSpace Pro Enterprise (12.9.2 or newer) servers. vSpace Pro LTS servers will not accept connections from RX420(RDP), RX440(RDP) and RX-RDP+ devices.

Unlike the vSpace Clients contained in the NComputing RX300 thin client devices, the vSpace Clients from the RX420(RDP), RX440(RDP) and RX-RDP+ firmware do not contain any embedded vSpace Client connection licenses. Appropriate vSpace Client connection licenses need to be purchased and added to the vSpace Pro Enterprise deployments to allow uninterrupted vSpace Client connections from RX420(RDP), RX440(RDP) and RX-RDP+ devices. Without the necessary licenses, the vSpace sessions will run in trial mode and will be disconnected after 10 minutes.

vSpace Pro Client Connection License ordering SKUs:

• 1 year  (vSpacePro-SW-1A)
• 3 years (vSpacePro-SW-3A)
• 5 years (vSpacePro-SW-5A)

• Connecting to VERDE VDI or VERDE Remote Access

Two license types are supported. Both are concurrent connection models:

• VERDE-WFH-1A-10 (VERDE VDI Suite - Remote Access 10-seat license, annual subscription) 

This license type allows Remote Access connections to PCs through the VERDE Connection Broker and is the most affordable option.

• VERDE8-CCU-1A (VERDE VDI Suite –1-seat license, annual subscription)

This license type allows Remote Access connections to PCs through the VERDE Connection Broker and supports connections to VDI sessions hosted by VERDE Servers.

• Native (functional) redirection of webcams in UXP sessions

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

Local Chromium Browser related:

• Local printing support for local Chromium browser in RX420(RDP) and RX440(RDP)

For each defined local printer, an additional instance of the same printer gets created with the '_local' suffix appended to the name. For this additional printer, based on the specified Windows Printer Driver Name, RX420(RDP)/RX440(RDP) try to find a suitable Linux printer driver. With that, the local Chromium web browser should be able to print. In Chromium, using the ‘See more…’ options in Printing dialog may be necessary to find the additional local printer:

In the example above, the 'HPDJ_5520' printer was defined in the device configuration. This caused the creation of two Linux printers: HPDJ_5520 (driverless, to be used in AVD, RDP, and Citrix sessions only) and HPDJ_5520_local (with Linux driver configured, to be used in Chromium browser).

• Custom Chromium policy support

Chromium policy customization file can be added Chromium browser under its Application Settings. Please refer this KB article ‘Customize local Chromium browser policy settings’ for configuration details. 

• Multiple instances of local Chromium browser (e.g., different customized Chromium policies, pre-defined bookmarks, etc.) can be created on LEAFOS, EX500W, RX420(RDP), RX540 and RX580 devices. Please refer to this article ‘Configure multiple instances of local Chromium browser’ for instructions.

Networking and connectivity related:

• Authentication methods supported by the VPN clients:

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

• Preconfiguring Wi-Fi connection using the wifi-config.txt file

When deploying new (with factory default settings) RX420(RDP), RX440(RDP), and RX-RDP+ devices the Wi-Fi connection can be automatically configured using information from the wifi-config.txt file stored on a locally connected USB memory stick. This helps streamlining new deployments by eliminating the need for users to manually configure local Wi-Fi connections.

The wifi-config.txt file must be a plain text file containing the Wi-Fi configuration parameters in ‘parameter_name=parameter_value’ format in each line.

The mandatory parameters are:

• ssid – the name of the Wi-Fi network
• passphrase – the clear-text password for the Wi-Fi network (using Personal security)

Optional parameters are:

• security – valid values: ‘personal’ (default if not specified) or ‘enterprise’
• country – two-uppercase-characters country code, e.g. US, GB, FR, DE, IN, etc., for United States, Great Britain, France, Germany, India, etc.
• user_name – Wi-Fi user name for ‘enterprise’ security
• user_password – Wi-Fi user password (in clear-text) for ‘enterprise’ security
• hidden_ssid – true or false to enable or disable support for Wi-Fi networks not broadcasting their names
• ip_address – static IP address (only needed when ‘type’ will be set to ‘static’)
• network_mask – network mask (only needed when ‘type’ will be set to ‘static’)
• default_gateway – IP address of default gateway (only needed when ‘type’ will be set to ‘static’)
• advanced_security – Wi-Fi encryption type: ‘auto’, ‘wpa’, or ‘wpa2’
• authentication_method – Wi-Fi authentication method: ‘peap’, ‘ttls’, ‘tls’
• frequency – Wi-Fi frequency: ‘auto’, ‘2.4’, or ‘5’
• type – type of IP configuration: ‘dhcp’ (default if not specified) or ‘static’

Other device setting related:

• Simple Certificate Enrollment Protocol support

The RX device allows using the Simple Certificate Enrollment Protocol for obtaining the Certification Authority and client certificates, which can then be used for the 802.1x network authentication with the TLS protocol. The SCEP settings can be configured on the Security > SCEP page of the Setup UI.

The configurable parameters are:

• Use SCEP for certificate enrollments – When selected, the device will use the SCEP protocol to obtain the Certification Authority and client certificates.
• SCEP server URL – The address (IP or hostname) or URL of the SCEP server. When only an address is specified, the SCEP server URL will be composed by prepending the ‘http://’ protocol scheme and appending the ‘/CertSrv/mscep/mscep.dll’ path. For example: if ‘scep.company.local’ would be specified as SCEP server URL, the actual URL would become: ‘http://scep.company.local/CertSrv/mscep/mscep.dll’. This will work when the Microsoft Network Device Enrollment Service (NDES) will be used as the SCEP server. When using an SCEP server other than Microsoft NDES, the complete URL should be specified, not just an address.
• SCEP challenge password source – Two options are selectable here: Specified below and NDES admin page. 

• Specified below – The SCEP challenge password will be taken from the SCEP challenge password field of SCEP settings. This option makes sense when the SCEP server is configured with a static SCEP challenge password. 
• NDES admin page – This option has been designed to allow using dynamic (one-time) SCEP challenge passwords. The SCEP challenge password will be obtained from the NDES admin page before creating each certificate signing request, which will be sent through SCEP then. If the specified SCEP server URL is just an address, then the URL of the NDES admin page will be composed by prepending the ‘https://’ protocol scheme and appending the ‘/CertSrv/mscep_admin/’ path. For example: if ‘scep.company.local’ would be specified as SCEP server URL, the actual NDES admin page URL would become: ‘https://scep.company.local/CertSrv/mscep_admin’. As the name of the option suggests, this will only work with Microsoft NDES. When a complete URL is configured as SCEP Server URL, then the same URL will be used as NDES admin page URL, only the scheme will be changed to ‘https://’. This will not work with NDES. For that reason, when using Microsoft NDES as SCEP server, we advise to only specify the server address (not the full URL) as the SCEP server URL.

• SCEP challenge password – The (usually static) SCEP challenge password to be used when creating certificate signing requests.
• NDES admin user name – The name of the Active Directory user permitted the access to the NDES admin page. It will be used when obtaining the SCEP challenge password from the NDES admin page.
• NDES admin user password – The password of the NDES admin user.
• Certificate subject type – Two options are selectable here: Device name only and Device name with DNS domain.

• Device name only – Only the current device name from the General > Device name settings will be used as the Common Name and Subject Alternate Name in the requested client certificate. E.g., RX4201000000035750d6d.
• Device name with DNS domain – The current device name from the General > Device name settings with the DNS domain name (obtained from DHCP or configured statically) will be used as the Common Name and Subject Alternate Name in the requested client certificate. 
  E.g., LEAF681DEF38CF69.company.local.

No other components than the Common Name will be included in the subject of the requested client certificate.

• Private key length – Selection of the private key length: 1024, 2048, or 4096 bits.
• Keep the old private key when renewing the certificate – When selected, the already present private key will be re-used when renewing the certificate. Otherwise, a new private key will be generated when renewing the certificate.
• Custom parameters – This field will not be currently used.

Note: The SCEP support has only been tested with the Microsoft Network Device Enrollment Service (NDES) acting as SCEP server. The NDES admin page selection for the SCEP challenge password source will only work when NDES and only when an address (not a URL) has been specified as SCEP server URL.

Information about the Certificate Authority certificate and client certificate currently stored on the RX device will be displayed above the SCEP settings on the Security > SCEP page of the Setup UI.

• Using the SCEP-obtained client certificates for 802.1x network authentication 

The Certification Authority and client certificates obtained with the SCEP protocol can be used for the 802.1x Ethernet and Wi-Fi network authentication with the TLS method. For this purpose, two new parameters have been added to Enterprise (802.1x) Ethernet and Wi-Fi network settings in RX devices 6.7.500 and higher versions: CA certificate source and Client certificate source. Two selections are possible for both of them: Device configuration and SCEP.

• Device configuration – The certificate will have to be selected in device configuration, as it was in all older RX versions.
• SCEP – The certificate obtained with SCEP will be used.

Practical deployment advise: 

As the 802.1x network access control standard disallows the network access from devices which cannot authenticate themselves, the RX device, to be able to make use of the SCEP protocol for obtaining the certificates necessary for 802.1x authentication, must be first temporarily connected to some open network. This open network should allow the device to connect to PMC Endpoint Manager, which should provide to the device the configuration which will: 1. contain the SCEP settings, and 2. contain the 802.1x network settings (including the options to enable 802.1x support with the TLS authentication method and to use the SCEP-obtained certificates for 802.1x authentication). Alternatively, assuming that the final destination of the deployed devices will allow fallback to an open network (e.g., to a guest VLAN), the fallback network should allow access to PMC Endpoint Manager which will provide the necessary configuration. The devices, once configured in the fallback network, should be able to automatically switch to the secured network, as they will already have all the information (especially the SCEP-obtained certificates) necessary to successfully complete the 802.1x authentication.

• Custom device naming

Before version 6.7.500 it was possible to configure a custom RX device name by specifying it in device’s General settings. The configured device name will be used by the DHCP client when requesting IP configuration, it gets reported to PMC during check-in, so it can be used to identify the device in PMC, also the VDI clients report the device name to the session hosts which in turn make it available for the applications through the CLIENTNAME environment variable. In older RX versions, the default device name was set to ‘RX420’ or ‘RX440’ with the SOC serial number.

RX allows automating the device naming based on configurable rules. The device name prefix, its body (which can be SOC serial number or parts of the MAC address), and the suffix are now configurable on the General > Devie Name page of the Setup UI. Following settings are available:

• Specified – The freely specified device name, as in previous RX versions.
• Set automatically – The device name will be set automatically based on the configured rules.
• Prefix – The device name prefix. 
• Body – The body (middle part) of the device name. It can be the whole SOC serial number or, 6, 8, 10, or 12 (the whole) characters of the Ethernet or Wi-Fi interface MAC address.
• Suffix – The device name suffix. 

After resetting the device to factory defaults, the prefix will be set to ‘RX420’ or ‘RX440’, the body will be set to ‘whole SOC serial number’, and the suffix will be empty. With such settings, the default device name will be set in the same way as it was in the previous RX versions.

• Support for the Virtual Cable UDS Enterprise virtualization environment

UDS Enterprise client has been updated to version 4.0. This client will be launched when the UDS Enterprise connection will be initiated in the Chromium browser and when the ‘RDP Tunnel for Desktop’ will be used for establishing the connection. The RDP Settings, which are configurable for the Chromium browser application, will be taken into account then. Especially, the type of the RDP client used for the connection initiated through Chromium browser can be selected. Selecting the AVD client as client type allows the UDS Enterprise users to benefit from the Microsoft Teams optimization. 

• On-screen keyboard

The binaries of the ‘onboard’ on-screen keyboard are contained in the firmware image. The on-screen keyboard can be configured under "Keyboard and Mouse" settings. 

• Configurable power button custom actions

The RX420(RDP), RX440(RDP), and RX-RDP+ devices can be configured to execute the following actions when the user presses on the power button:

• entering the sleep mode, 
• shutting down,
• rebooting,
• not performing any action.

The actions can be executed immediately or postponed for a specified period of time, when a pop-up message with a countdown counter will be displayed allowing the user to cancel the action or to select a different one. 

To configure the ‘Power button actions’, go to Settings > Management > Power Button Actions.

• Ability to rescale the RX thin client local display and selected applications

When using high-resolution displays, especially 4K, it may be beneficial to upscale the RX thin client GUI components, to make them appearing bigger and thus become better readable. Scaling factors from 100% (which is the default, meaning no scaling) to 200% are selectable under Display settings. The RX420(RDP), RX440(RDP) and RX-RDP+ software components which will respect the scaling selection are:

• Desktop and local applications
• Logon windows of client applications (AVD, RDP, VERDE VDI), the server chooser of vSpace Client, RDP sessions, AVD sessions.

Note: The scaling ratio of some applications might be silently adjusted to a value accepted by the application or kept set to 100%, if the application does not support scaling.

• Using VDI clients to control access to RX420(RDP) and RX440(RDP) applications

The VDI client applications which perform user authentication and enumerate the VDI resources prior to starting the actual terminal session and for which the RX420(RDP) and RX440(RDP) firmware has access to user credentials can be used to control access to other applications. To enable this feature, the Use this application to grant access to other applications (e.g. local Chromium browser) checkbox needs to be selected in Application Settings. With this feature enabled, RX420(RDP) and RX440(RDP) will not allow access to all other applications until the user will successfully authenticate in the one, which has this option enabled.

The following applications can be used for this purpose:

• RDP Client (only when the RemoteApp and Desktop connections will be enabled)
• AVD Client

• Support for Asian multilingual input

The IBus (Intelligent Input Bus) component can be optionally enabled under Keyboard and Mouse settings for the Chinese, Korean, Japanese and Thai keyboard layouts. This allows proper keyboard input in local Chromium Browser application.

Note: Enabling IBus is not necessary (and even not advisable) if no local Chromium Browser is used, and the user will only work in remote desktop sessions.

• Setting up a custom boot splash image

Only image files in PNG format are supported.

PMC Endpoint Manager related:

• PMC license for managing the RX420(RDP), RX440(RDP) and RX-RDP+ devices

Each RX420(RDP), RX440(RDP) and RX-RDP+ device comes with a perpetual license for the PMC Endpoint Manager software and first-year complimentary software maintenance update (AMP for RDP) license. After the expiration of the first-year complimentary Device AMP license, the device will not be able to receive and apply firmware updates. An extended Device AMP licenses must be purchased and allocated to each RX420(RDP), RX440(RDP) and RX-RDP+ device to allow local or remote (via PMC) firmware updates.

• PMC Endpoint Manager 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://10.25.40.190’. If DHCP response will not contain the 207 option, the device will attempt to use the ‘https://pmc’ URL as PMC URL. This will work if the DNS system for the current DNS domain will be able to resolve the ‘pmc’ hostname to a valid PMC IP address.

• Using PMC Endpoint Manager 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 device onboarding

When the Require passcode for device onboarding option will be activated under System Settings of PMC Endpoint Manager, 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.

• Support for the device “Raise Hand” feature for easier identification of devices whose users need help 

When the device user will press 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.

• Secure Shell support

RX allows establishing Secure Shell (SSH) connections to RX Linux shell. The Secure Shell access is disabled by default and can be enabled under Management > Secure Shell settings. The user with Secure Shell access is ‘rx’ and a password must be set to allow the access.

ADDITIONAL RESOURCES

• Getting Started: RX-series thin clients for Microsoft AVD and Windows 365

• Getting Started: LEAF OS for UDS Enterprise

• RX420(RDP), RX440(RDP) and RX-RDP+ User Configuration Guide:

RX420(RDP), RX440(RDP) and RX-RDP+ are easy-to-use and provision. For users who want to learn how to use advanced features and/or customizations, please refer to the RX420(RDP), RX440(RDP) and RX-RDP+ User Configuration Guide:

https://ncomputing.box.com/shared/static/310pp20tfhh4aqc6x4nj14sxch52q360.pdf 

• 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 4.x Quick Start Guide:

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