Knowledge Base NComputing vSpace Server vSpace Pro 10 & 11

            Smart Card Reader Support in vSpace Pro

            Enhanced Smart Card Reader Support:

            Extended smart card support for RX300 and vSpace Pro Client for Windows is now an included feature starting with vSpace Pro version 11.2.0. All future version will include this feature.

            If your organization requires smart cards for single sign-on, access control or other security-related measures, vSpace Pro version 11.2.0 provides enhanced smart card support for both RX300 and vSpace Pro Client for Windows with no limit on the number of smart card readers can be connected per vSpace Server. In this case, functional (native, virtual-channel-based) redirection of smart card readers has been added to overcome the limits of the Generic USB-based smart card reader redirection implemented in vSpace Pro 10.x and vSpace Server 8.4. Any CCID-compliant smart card readers should be able to work seamlessly with RX300 thin client and vSpace Pro client for Windows.

            Other thin clients (L/M/MX-series thin client) still have the restriction of a maximum of 10 connected smart card readers per vSpace Server. In this case, each smart card reader connected to the supported L/M/MX-series thin client is redirected and mapped to the corresponding logged-in session and is accessible from applications running the session. To ensure compatibility, the smart card reader should have its driver supported in the host Windows OS. 
            ·        To enable smart card reader support on supported L/M/MX/RX-series thin clients, please follow the below instructions to enable the smart card reader on vSpace Pro version 11.2.0 (in vSpace Console):

            Smart card reader setup for L/M/MX/RX-series thin clients in vSpace Pro 11:

            1.     In vSpace Console, go to “Manage Servers”,

            2.     Then select your vSpace Pro 11 server and select the “Settings’ menu,

            3.     From the “Settings” menu, click on “Performance Profiles” and select the “Manage Custom Profile” tab at the top

            4.     From this tab, click on “+” icon to add a new device Performance Profile and you will see a pop-up window,

            5.     From the pop-up window, enter the new profile name for the vSpace Pro Client (any name that makes sense to you), and in the copy from parameter, select “RX-series and Software Client on a high-speed network”, or other device performance profile if you have other client types. Click “ADD” to complete the process,

            6.  Then select the custom profile you just created, scroll down to “Enable Smart Cards” parameter and choose “Yes” to enable this feature. Click on “Apply” to finish the process. See screenshot below

            7. On the same vSpace Console window, make sure ‘Enable USB redirection’ is still checked (default value) under ‘Peripheral Devices’ tab.

            If you have L/M/MX-series thin clients, then you have completed all the necessary smart card configuration changes. With L/M/MX-series thin clients, there is a restriction of a maximum of 10 connected smart card readers per vSpace Server.

            If you have RX300 thin client, there is one additional step needed (change USB redirection policy from Generic USB to Native) to complete the smart card reader setup:


            From RX300 device, go to RX300 device settings, click on Peripherals, set peripheral devices redirection settings to ‘Custom’ and toggle the smart card readers parameter to ‘Native’. Click on Apply to save.

            For RX300 thin clients, there is no limit on the number of smart card readers can be connected per vSpace Server.


            Please see the list of supported CCID-complaint card reader devices for the RX300 in the vSpace Pro 11 release notes starting on page 10 in the link above.




            To verify the smartcard/smartcard reader functionality, you can install and run PCSC Bridge Application:




             Connect to Reader.




            Help us to make this article better
            0 0