Remote USB device not visible with RDP












3














I have the same problem as asked here How to access *remote* usb devices over rdesktop and here Remote desktop: remote USB devices not recognized long time ago, unanswered.



I have a remote machine with Windows 10 and an USB device plugged in there. When I go there physically, log into it, I can see the USB device. When I log into that machine remotely with RDP, the device is not visible/accessible. Like it was not there at all.



How can I access remote USB device of that remote machine, when logged in with RDP?



To be clear (because it's a common mistake around the internet) - I'm not trying to redirect local USB device over RDP. The device is plugged into the target, remote machine and I cannot see it when I connect to it over RDP (and only then).










share|improve this question



























    3














    I have the same problem as asked here How to access *remote* usb devices over rdesktop and here Remote desktop: remote USB devices not recognized long time ago, unanswered.



    I have a remote machine with Windows 10 and an USB device plugged in there. When I go there physically, log into it, I can see the USB device. When I log into that machine remotely with RDP, the device is not visible/accessible. Like it was not there at all.



    How can I access remote USB device of that remote machine, when logged in with RDP?



    To be clear (because it's a common mistake around the internet) - I'm not trying to redirect local USB device over RDP. The device is plugged into the target, remote machine and I cannot see it when I connect to it over RDP (and only then).










    share|improve this question

























      3












      3








      3







      I have the same problem as asked here How to access *remote* usb devices over rdesktop and here Remote desktop: remote USB devices not recognized long time ago, unanswered.



      I have a remote machine with Windows 10 and an USB device plugged in there. When I go there physically, log into it, I can see the USB device. When I log into that machine remotely with RDP, the device is not visible/accessible. Like it was not there at all.



      How can I access remote USB device of that remote machine, when logged in with RDP?



      To be clear (because it's a common mistake around the internet) - I'm not trying to redirect local USB device over RDP. The device is plugged into the target, remote machine and I cannot see it when I connect to it over RDP (and only then).










      share|improve this question













      I have the same problem as asked here How to access *remote* usb devices over rdesktop and here Remote desktop: remote USB devices not recognized long time ago, unanswered.



      I have a remote machine with Windows 10 and an USB device plugged in there. When I go there physically, log into it, I can see the USB device. When I log into that machine remotely with RDP, the device is not visible/accessible. Like it was not there at all.



      How can I access remote USB device of that remote machine, when logged in with RDP?



      To be clear (because it's a common mistake around the internet) - I'm not trying to redirect local USB device over RDP. The device is plugged into the target, remote machine and I cannot see it when I connect to it over RDP (and only then).







      windows windows-10 usb remote-desktop






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 11 at 23:35









      Googie

      1264




      1264






















          4 Answers
          4






          active

          oldest

          votes


















          1














          From what I read the Windows Terminal Services does not allow to use certain devices in a way I described in a question. Example of such device is a Smart Card reader (various kinds of hardware USB certificates/tokens).



          For such devices it's only allowed to use the device at the computer where it is physically plugged in and eventually redirect it over RDP to remote machine, where it can be then used over RDP session.



          Unfortunately it looks like such devices have to be plugged in locally to the RDP client, not server and tunneled (redirected) through RDP towards the server when connecting to it. There is no way to share it between different RDP accounts.



          Unless anyone else proves me wrong in a day or two, I will accept my answer.






          share|improve this answer





























            0














            Depending on what client you are using for RDP might change it slightly, but the official from Microsoft:



            For your issue I can suggest you to check group policy setting “Do not allow drive redirection” must be disabled under following path.



            Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostDevice and Resource Redirection



            It may also help to use an account that has admin on that machine.



            Scraped from:https://social.technet.microsoft.com/Forums/en-US/24ab3b8c-730d-4085-a69a-7626db39da10/local-client-drives-visible-but-not-accessible?forum=winserverTS






            share|improve this answer





















            • Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
              – Googie
              Dec 12 at 2:23





















            0














            I know you asked for RDP.



            But if you really need this device to work when you are connected remotely you can use any other remote connection options available like VNC, or even TeamViewer / Anydesk.






            share|improve this answer





















            • Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
              – Googie
              Dec 17 at 22:28



















            -1














            1)Open Remote Desktop Connection, click Local Resource tab and More button, unfold device node. Please check if you choose all device letter.



            2)Open Terminal Services Configuration, right-click RDP-tcp, choose properties. In Client settings, please check if disable device has been applied.



            3)Run Rsop.msc on Terminal server and see if Do not allow driver redirection has been configured under computer configurationsAdministrative TemplateWindows ComponentTerminal serverDevice and Resource redirection



            From: https://social.technet.microsoft.com/Forums/lync/en-US/2aa84bbe-4572-487e-bec3-69a56e4359e4/usb-devices-not-working-in-remote-desktop?forum=w7itpronetworking






            share|improve this answer























            • I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
              – Googie
              Dec 12 at 2:20











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1382797%2fremote-usb-device-not-visible-with-rdp%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            4 Answers
            4






            active

            oldest

            votes








            4 Answers
            4






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            From what I read the Windows Terminal Services does not allow to use certain devices in a way I described in a question. Example of such device is a Smart Card reader (various kinds of hardware USB certificates/tokens).



            For such devices it's only allowed to use the device at the computer where it is physically plugged in and eventually redirect it over RDP to remote machine, where it can be then used over RDP session.



            Unfortunately it looks like such devices have to be plugged in locally to the RDP client, not server and tunneled (redirected) through RDP towards the server when connecting to it. There is no way to share it between different RDP accounts.



            Unless anyone else proves me wrong in a day or two, I will accept my answer.






            share|improve this answer


























              1














              From what I read the Windows Terminal Services does not allow to use certain devices in a way I described in a question. Example of such device is a Smart Card reader (various kinds of hardware USB certificates/tokens).



              For such devices it's only allowed to use the device at the computer where it is physically plugged in and eventually redirect it over RDP to remote machine, where it can be then used over RDP session.



              Unfortunately it looks like such devices have to be plugged in locally to the RDP client, not server and tunneled (redirected) through RDP towards the server when connecting to it. There is no way to share it between different RDP accounts.



              Unless anyone else proves me wrong in a day or two, I will accept my answer.






              share|improve this answer
























                1












                1








                1






                From what I read the Windows Terminal Services does not allow to use certain devices in a way I described in a question. Example of such device is a Smart Card reader (various kinds of hardware USB certificates/tokens).



                For such devices it's only allowed to use the device at the computer where it is physically plugged in and eventually redirect it over RDP to remote machine, where it can be then used over RDP session.



                Unfortunately it looks like such devices have to be plugged in locally to the RDP client, not server and tunneled (redirected) through RDP towards the server when connecting to it. There is no way to share it between different RDP accounts.



                Unless anyone else proves me wrong in a day or two, I will accept my answer.






                share|improve this answer












                From what I read the Windows Terminal Services does not allow to use certain devices in a way I described in a question. Example of such device is a Smart Card reader (various kinds of hardware USB certificates/tokens).



                For such devices it's only allowed to use the device at the computer where it is physically plugged in and eventually redirect it over RDP to remote machine, where it can be then used over RDP session.



                Unfortunately it looks like such devices have to be plugged in locally to the RDP client, not server and tunneled (redirected) through RDP towards the server when connecting to it. There is no way to share it between different RDP accounts.



                Unless anyone else proves me wrong in a day or two, I will accept my answer.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 12 at 2:47









                Googie

                1264




                1264

























                    0














                    Depending on what client you are using for RDP might change it slightly, but the official from Microsoft:



                    For your issue I can suggest you to check group policy setting “Do not allow drive redirection” must be disabled under following path.



                    Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostDevice and Resource Redirection



                    It may also help to use an account that has admin on that machine.



                    Scraped from:https://social.technet.microsoft.com/Forums/en-US/24ab3b8c-730d-4085-a69a-7626db39da10/local-client-drives-visible-but-not-accessible?forum=winserverTS






                    share|improve this answer





















                    • Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
                      – Googie
                      Dec 12 at 2:23


















                    0














                    Depending on what client you are using for RDP might change it slightly, but the official from Microsoft:



                    For your issue I can suggest you to check group policy setting “Do not allow drive redirection” must be disabled under following path.



                    Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostDevice and Resource Redirection



                    It may also help to use an account that has admin on that machine.



                    Scraped from:https://social.technet.microsoft.com/Forums/en-US/24ab3b8c-730d-4085-a69a-7626db39da10/local-client-drives-visible-but-not-accessible?forum=winserverTS






                    share|improve this answer





















                    • Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
                      – Googie
                      Dec 12 at 2:23
















                    0












                    0








                    0






                    Depending on what client you are using for RDP might change it slightly, but the official from Microsoft:



                    For your issue I can suggest you to check group policy setting “Do not allow drive redirection” must be disabled under following path.



                    Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostDevice and Resource Redirection



                    It may also help to use an account that has admin on that machine.



                    Scraped from:https://social.technet.microsoft.com/Forums/en-US/24ab3b8c-730d-4085-a69a-7626db39da10/local-client-drives-visible-but-not-accessible?forum=winserverTS






                    share|improve this answer












                    Depending on what client you are using for RDP might change it slightly, but the official from Microsoft:



                    For your issue I can suggest you to check group policy setting “Do not allow drive redirection” must be disabled under following path.



                    Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostDevice and Resource Redirection



                    It may also help to use an account that has admin on that machine.



                    Scraped from:https://social.technet.microsoft.com/Forums/en-US/24ab3b8c-730d-4085-a69a-7626db39da10/local-client-drives-visible-but-not-accessible?forum=winserverTS







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Dec 12 at 1:20









                    AggrostheWroth

                    33612




                    33612












                    • Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
                      – Googie
                      Dec 12 at 2:23




















                    • Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
                      – Googie
                      Dec 12 at 2:23


















                    Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
                    – Googie
                    Dec 12 at 2:23






                    Guy from quoted article starts with following statement "I have a problem with mapping of local client drives when accessing a Windows Server 2012 machine via Remote Desktop.". I don't want to use my local device on remote host. I have a device plugged in physically to that remote host. Problem is I don't see it if I connect there with RDP. But I can see it just fine if I go there personally and log in to that computer from physical keyboard and monitor connected to that computer.
                    – Googie
                    Dec 12 at 2:23













                    0














                    I know you asked for RDP.



                    But if you really need this device to work when you are connected remotely you can use any other remote connection options available like VNC, or even TeamViewer / Anydesk.






                    share|improve this answer





















                    • Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
                      – Googie
                      Dec 17 at 22:28
















                    0














                    I know you asked for RDP.



                    But if you really need this device to work when you are connected remotely you can use any other remote connection options available like VNC, or even TeamViewer / Anydesk.






                    share|improve this answer





















                    • Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
                      – Googie
                      Dec 17 at 22:28














                    0












                    0








                    0






                    I know you asked for RDP.



                    But if you really need this device to work when you are connected remotely you can use any other remote connection options available like VNC, or even TeamViewer / Anydesk.






                    share|improve this answer












                    I know you asked for RDP.



                    But if you really need this device to work when you are connected remotely you can use any other remote connection options available like VNC, or even TeamViewer / Anydesk.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Dec 17 at 22:04









                    Yehuda

                    22336




                    22336












                    • Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
                      – Googie
                      Dec 17 at 22:28


















                    • Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
                      – Googie
                      Dec 17 at 22:28
















                    Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
                    – Googie
                    Dec 17 at 22:28




                    Yes, I was aware of that option. Problem with VNC is each connecting user will share the same session, or "screen". To have separate screens available per user I would have to setup as many vnc instances as there would be users of the system. That introduces other problems with maintaing this whole thing.
                    – Googie
                    Dec 17 at 22:28











                    -1














                    1)Open Remote Desktop Connection, click Local Resource tab and More button, unfold device node. Please check if you choose all device letter.



                    2)Open Terminal Services Configuration, right-click RDP-tcp, choose properties. In Client settings, please check if disable device has been applied.



                    3)Run Rsop.msc on Terminal server and see if Do not allow driver redirection has been configured under computer configurationsAdministrative TemplateWindows ComponentTerminal serverDevice and Resource redirection



                    From: https://social.technet.microsoft.com/Forums/lync/en-US/2aa84bbe-4572-487e-bec3-69a56e4359e4/usb-devices-not-working-in-remote-desktop?forum=w7itpronetworking






                    share|improve this answer























                    • I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
                      – Googie
                      Dec 12 at 2:20
















                    -1














                    1)Open Remote Desktop Connection, click Local Resource tab and More button, unfold device node. Please check if you choose all device letter.



                    2)Open Terminal Services Configuration, right-click RDP-tcp, choose properties. In Client settings, please check if disable device has been applied.



                    3)Run Rsop.msc on Terminal server and see if Do not allow driver redirection has been configured under computer configurationsAdministrative TemplateWindows ComponentTerminal serverDevice and Resource redirection



                    From: https://social.technet.microsoft.com/Forums/lync/en-US/2aa84bbe-4572-487e-bec3-69a56e4359e4/usb-devices-not-working-in-remote-desktop?forum=w7itpronetworking






                    share|improve this answer























                    • I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
                      – Googie
                      Dec 12 at 2:20














                    -1












                    -1








                    -1






                    1)Open Remote Desktop Connection, click Local Resource tab and More button, unfold device node. Please check if you choose all device letter.



                    2)Open Terminal Services Configuration, right-click RDP-tcp, choose properties. In Client settings, please check if disable device has been applied.



                    3)Run Rsop.msc on Terminal server and see if Do not allow driver redirection has been configured under computer configurationsAdministrative TemplateWindows ComponentTerminal serverDevice and Resource redirection



                    From: https://social.technet.microsoft.com/Forums/lync/en-US/2aa84bbe-4572-487e-bec3-69a56e4359e4/usb-devices-not-working-in-remote-desktop?forum=w7itpronetworking






                    share|improve this answer














                    1)Open Remote Desktop Connection, click Local Resource tab and More button, unfold device node. Please check if you choose all device letter.



                    2)Open Terminal Services Configuration, right-click RDP-tcp, choose properties. In Client settings, please check if disable device has been applied.



                    3)Run Rsop.msc on Terminal server and see if Do not allow driver redirection has been configured under computer configurationsAdministrative TemplateWindows ComponentTerminal serverDevice and Resource redirection



                    From: https://social.technet.microsoft.com/Forums/lync/en-US/2aa84bbe-4572-487e-bec3-69a56e4359e4/usb-devices-not-working-in-remote-desktop?forum=w7itpronetworking







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Dec 12 at 1:51

























                    answered Dec 12 at 1:45









                    yilia zhao

                    522




                    522












                    • I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
                      – Googie
                      Dec 12 at 2:20


















                    • I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
                      – Googie
                      Dec 12 at 2:20
















                    I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
                    – Googie
                    Dec 12 at 2:20




                    I deliberately mentioned I don't mean redirection of local device over RDP into remote host. What you provided is solution exactly for that.
                    – Googie
                    Dec 12 at 2:20


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1382797%2fremote-usb-device-not-visible-with-rdp%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    RAC Tourist Trophy