We have a client whose network is totally locked down and our software is a cloud based RDP Server. We do have the need for local signature pads (USB) that talk with a socket to the RDP server, but each user has to have a separate port path. We use their server username as this unique id so that the server signature socket can direct the signature to the correct users desktop.
We are not getting a lot of support from the agencies IT group, so we would like to do this without their involvement. They will have to install the signature pads locally, but different users log into a single device so I actually need to execute an application on the client prior to the RDP Remote App opening its connection to the server.
I am open to ideas because I don't want to have to write an application to do this on the client and then winexec our remote app. If this is the only way then so be it, but with todays technology I assume I am not the first to run into this problem.
Our servers are in the cloud and our RDP Terminal Server is a Windows 2008 R2 Server. The signature pads are Topaz HSB (USB) pads and use sigsock.exe to talk through 3 ports to the server.