Serial / Com Port not working in Remote Desktop

I have a Terminal Server that runs my loan software.  Users have a Topaz 766 signature pad on their local desktop.  I have one computer that refuses to map the local serial port to the remote server.  I've tried different users logging into to both local and remote machines.  I've tried a new signature pad.

Here is the interesting thing, when I run a program locally to test the signature pad, the program works fine.  The disclaimer text shows up on my signature pad and my signature shows up on the computer screen.  Exactly what it's suppose to do.  However, when I run the same signature pad on the TS server, nothing shows up on the pad or the screen.

And yes, I did check the box to share / map / direct serial / com ports to the remote desktop.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

EricSimonsAuthor Commented:
Please note, SQL server has nothing to do with this question.  That was an error on my part.

I have tried to reinstall my software, I reinstalled the drivers for the signature pad.  I removed and reinstalled my com port through device manager.

It might be worth mentioning that other users can access the TS server fine and their signature pads work properly.
Cláudio RodriguesFounder and CEOCommented:
Well if it works for all other users on different machines and even for this user when he uses another machine, the issue is on the machine. Simple as that.
In that case a couple tests:
1. If you remove the hard disk and add a new one with a fresh install, does it work? If it does, the issue is on your existing installation of Windows. If it does not work the problem is with the machine itself.
2. You can try using Process Monitor (free from MS) to compare what a good machine does when you try using it over TS and when the bad one does it. If there is a registry/filesystem issue it will show it to you.

Cláudio Rodrigues
Citrix CTP
EricSimonsAuthor Commented:
It turns out that the users' profile on the terminal server had become corrupt.  Everything worked and looked normal except the remote desktop.  I say this because deleting the profile (thus forcing a rebuild on next logon) solved the issue.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.