![](/uploads/1/2/7/3/127342314/829591702.jpg)
Good afternoon spiceheads,We're working on a project that will capture signatures digitally for our loan applications. The software used to create those applications is held on a server with RD services enabled on it which users will connect to when they're using the software. I have connected a signature pad that can do the com port redirection to my PC for testing and am able to use it fine locally. However, when I use remote desktop to get into the server that is hosting the software to test it, the device is not discovered in device manager.When remoting in, I've gone under local resources and checked the box for ports to be shared.
Participate as Beta-tester. Help us make the next releases of Serial Port for Remote Desktop our best yet. As a member of the FabulaTech Beta Software Program, you can take part in shaping FabulaTech software by test-driving pre-release versions and letting us know what you think. With this feature, users can redirect locally connected, serial (COM) ports, such as built-in RS232 ports or USB to Serial adapters, to their remote desktops. To support serial port redirection, your View deployment must meet certain software and hardware requirements.
Is there something I need to configure in RDS or something I need to change locally? Here is my 3 cents. I hope this helps.1. Enable serial port redirection using powershell.Run windows powershell as administratorl.Type Set-RDVirtualDesktopCollectionConfiguration -CollectionName Name -CustomRdpProperty 'redirectcomports:i:1' where Name is the actual name of the RDS Collection. Type ' ' around the collection name if there are spaces in the name. For example type 'My Collection Name'.2. verify com port redirection is not disabledin tsconfig.msc verify that com port redirection is not disabled in the server.run tsconfig.msc.
Right click the rdp-tcp in the center, click properties, select client settings. Ensure the COM port is not checked in redirection disable.a note: you may not have tsconfig.msc on your server.
Run it from anywhere and inside the software select another computer and select the server you have your rds on.3. check that com port redirection is not disabled in group policyrun gpedit.msc on the servergo to local computer policy computer configuration administrative templates all settingsscroll down and click on 'Do not allow COM port redirection'. Make sure the policy is not enabled.4. I would also agree with nick8010. The topaz has software that needs to be installed on the server. Maybe take a topaz and plug it directly into the server to set one up and test it, then retry it using rdp once you get it running directly from the server console.if all else fails.this is obviously not the best solution but it would at least work.
![Download rdp software Download rdp software](/uploads/1/2/7/3/127342314/697929251.jpg)
You could use a serial port redirector. I've used eltima usb and serial redirectors in VM solutions and they seem to work pretty well. It can be pricey but it might be a solid solution for you if you cant find a free fix using rdp.Edited Jun 27, 2019 at 13:43 UTC. The device is USB, but does serial redirection so it works with the software provided over RDS. It was recommended to me by the vendor we purchased from as well as the company who provides the software.
The Topaz software is on both my desktop and the RDS virtual server, hence why I could test on one and get it to work, but the test on the second wouldn't show anything. I've changed the COM port in the software to match the one that the device was using, but now all I get is one black line no matter what I write on the pad.Terminal Services is discontinued in RDS with Server 2016.I can check group policies/local policies, but I'm getting the pad to write something, just not what I'm writing on the pad itself. I would assume at this point it is a driver problem.
![](/uploads/1/2/7/3/127342314/829591702.jpg)