Geek Answers Handbook

VB application requires a unique Windows TS thin client identifier

I have a custom barcode application that runs on .Net 2.0 and is installed on a Windows terminal server. I use HP type thin clients and they pull their desktop out of TS on which my barcode application is installed.

For the most part, the barcode application works without problems. The only problem I encountered is that my barcode application needs to print shortcuts on a specific printer based on the work center where the thin client is located. The barcode application is designed to route labels based on the device name (Windows name) of the system from which the barcode transaction occurred.

I have a full-blown Windows XP Pro system that also launches a barcode application, and I have no problems with label routing, because each of these type systems has a unique name that I can use for routing. Where I encounter the problem that the barcode application is running on thin clients, it appears (from the point of view of barcode applications) to start from a terminal server, rather than individual thin clients.

Does anyone know how I can get some unique identifier from these thin clients for use in a barcode application to use for routing shortcuts?

+4
source share
1 answer

This is a difficult problem. If your thin clients have set IP addresses, I think I have a solution for you. I found an article that explains how to get the IP address of an RDP client (and not the server address). This will have problems if you intend to use NAT, but if you connect directly using RDP, it should work:

http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/857af1fe-75a4-4845-b989-f18636f296c9/

+2
source

More articles:


All Articles