I open Scandall Pro on the server, and click 'Select Scanner' and I see the scanner listed in the window with my TS session number, I select the scanner, and an error message displays 'Communication Failed'. I try to scan, and I get the error, failed to initialize scanner. When I connect to the server, and open devices and printers, I see the scanner listed. When I connect to the server, I am able to select the fi from the local resources menu as a device to redirect.

All of the necessary roles and policies are set to allow redirection of local devices. Nederland - Nederlands.We have a Fujitsu fi scanner connected to a W10 pro laptop that is remoting into Server r2 via remote desktop. Your feedback will help us improve the support experience. Tell us what we can do to improve the article Submit. Last Updated: Dec 30, Was this information helpful? Yes No. The theory here is that when developers updated their services to use this flag to open devices, they also added new functionality to make sure that their services restricted access to those devices to any other apps from other sessions that might also be using the service for example, if the service is a COM server. Only user-mode code that's running in that same session can access these devices. Therefore, users will see only USB devices that belong to them. Otherwise, you should contact the scanner manufacture for the latest driver that fixes the issue.

In this scenario, the scan doesn't start, and no error message is displayed. In that session, you open the Devices and Printers window. You install a driver for the scanner on the server. You connect a USB scanner to the Windows 8. Consider the following scenario: You prepare a Windows 8.

Rdp scanner redirection