RDP and access to PCSC device on remote computer

DCA 20 Reputation points
2023-06-06T05:50:43.7433333+00:00

Hello everyone,

I have following issue

COMPUTER A is connecting with RDP to COMPUTER B on which I have several PCSC devices

To open session I'm using the an admin user of COMPUTER B - when connected locally on COMPUTER B all the devices are visible and I can use them. RDP is allowed as well as all accessibility to any device over RDP (in group policy)

Nevertheless, PCSC devices (reader) can not be accessed nor even listed - whereas they correctly appear in Device Manager.

What as I missing ? (important: I'm not trying to use PCSC devices on computer A from which the session is opened, but the remote devices on computer B)

Thanks for Help

David

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,259 questions
0 comments No comments
{count} votes

Accepted answer
  1. Limitless Technology 43,966 Reputation points
    2023-06-06T10:51:37.31+00:00
    Hello DCA,
    
    Thank you for your question and for reaching out with your question today.
    
    If you are experiencing issues accessing PCSC devices (smart card readers) on COMPUTER B via RDP from COMPUTER A, despite the devices being visible in Device Manager, there are a few potential causes and troubleshooting steps you can try:
    
    1. Check Remote Desktop Settings: Ensure that remote access to devices is allowed in the Remote Desktop settings on COMPUTER B. To do this, follow these steps:
    
       a. On COMPUTER B, go to "System Properties" by right-clicking on "This PC" and selecting "Properties."
       
       b. Click on "Remote settings" on the left-hand side.
       
       c. In the "Remote Desktop" section, make sure "Allow remote connections to this computer" is selected.
       
       d. Click on "Advanced" and verify that "Devices and resources" is checked under "Local devices and resources."
    
    2. Verify Group Policy Settings: Check the Group Policy settings on COMPUTER B to ensure that the appropriate policies allowing device redirection over RDP are configured. Specifically, look for policies related to "Device Redirection" or "Remote Desktop Services."
    
    3. Verify User Permissions: Ensure that the admin user you are using to connect to COMPUTER B via RDP has sufficient permissions to access and use the PCSC devices. Verify that the user has the necessary privileges, such as membership in the "Administrators" group or specific permissions related to smart card usage.
    
    4. Update Device Drivers: Make sure that you have the latest device drivers installed for the PCSC devices on COMPUTER B. Outdated or incompatible drivers can sometimes cause issues with device access over RDP. Visit the manufacturer's website for the PCSC devices and download the appropriate drivers.
    
    5. Test with a Different User: Try connecting to COMPUTER B via RDP from COMPUTER A using a different user account with administrative privileges. This can help determine if the issue is specific to the user account you are currently using.
    
    6. Check Event Logs: Check the event logs on COMPUTER B for any relevant error messages or warnings related to device redirection or smart card usage. Look for entries in the "Application" or "System" logs that may provide clues about the issue.
    
    If the above steps do not resolve the issue, it may be necessary to further investigate the specific configuration, network environment, or consult with IT support or the manufacturer of the PCSC devices for more advanced troubleshooting steps.
    
    If the reply was helpful, please don’t forget to upvote or accept as answer.
    
    Best regards.
    
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. DCA 20 Reputation points
    2023-12-07T13:26:20.6133333+00:00

    Hello, many thanks for response and hints

    Sorry for late reply but unfortunately, after many many tests and checks, none of those has solved the issue

    We had to find a workaround meanwhile - using a VNC client/server - but this solution requires a license and involves a third-party we'd like to avoid.

    Is there any way to have technical support from Microsoft, just testing if they have the issue ?

    0 comments No comments