Rdp Serial Port Redirection Attacks
I don't think the accepted answer here is entirely correct. Right next to me is a barcode scanner connected to a Prolific USB2Serial adapter connected to a Windows 7 client (with installed Prolific Drivers). The Client sees this Prolific Adapter as COM3. Now if I connect to any terminal server while allowing ports to be mapped (Options > Local Resources > More.
If the sum of digits is divisible by three, then the number is divisible by three (e.g.
Serial Port 25 Pin
Check 'Ports'), that virtual COM3 will be available on the Terminal Server with no problem. So to answer the question: If you can install drivers on the Terminal Server Client machine and you install the Prolific driver, then you can enable Port redirection on the Client and the Port will be available and working correctly on the Server. If you can't install drivers on the client, you will need an external 3rd party software as it was linked by @TheCompWiz.
Printer Redirection Rdp
A maximum of two serial ports per session can be redirected. Currently, the redirected serial port is not accessible from Windows Remote Desktop Servers. RDP serial port redirection will be supported in future ThinLinc releases. The redirection is handled by processes called cyclades-ser-cli. I want to redirect the serial port from thin client to virtual desktop in VMware view 5.0.1. Scenario: ESXi 5.0.0 update1. VMware View 5.0.1. Guest O.S: Windows 7 sp1 64bits I use RDP protocol which can redirect to virtual desktop,but PCoIP cannot. Does PCoIP support serial port redirection? Windows client computers sometimes require COM port redirection when using Remote Desktop Services (RDS) provided by Windows Server 2012 and Windows Server 2012 R2.An example would be the use of a serial attached smart card reader on the client computer. Amongst features of terminal desktop services running RDP port, there is port redirection of parallel/serial from remote to local PC. Can this redirection be somehow used to transfer large data to avoid using Clipboard (due to the known stack bug which may force user to close terminal desktop and re-logon)?