VB应用程序需要Windows TS瘦客户端唯一ID
我有一个在 .Net 2.0 框架上运行并安装在 Windows 终端服务器上的自定义条形码应用程序。我正在使用 HP 型瘦客户端，他们正在从安装了我的条形码应用程序的 TS 中拉出桌面。
在大多数情况下，条形码应用程序运行没有问题。我遇到的唯一问题是我的条形码应用程序需要根据瘦客户端所在的工作中心将标签打印到特定打印机。条形码应用程序旨在根据设备名称（Windows 名称）路由标签条形码交易源自的系统的名称。
我有一个完整的 Windows XP Pro 系统，也运行条形码应用程序，并且我对标签路由没有任何问题，因为每个类型的系统都有一个唯一的名称，我可以用于路由。我遇到的问题是，从瘦客户端运行的条形码应用程序（从条形码应用程序的角度来看）似乎是从终端服务器而不是单个瘦客户端运行。
有谁知道如何从这些瘦客户端中提取某种类型的唯一标识符以在条形码应用程序中用于标签的路由？
I have a custom bar code app running on .Net 2.0 framework and installed on a Windows Terminal Server. I’m using HP type thin clients and they are pulling their desktop from the TS that has my barcode app installed on it.
For the most part, the barcode app runs with no problem. The only issue I have, is that my barcode app needs to print labels to a specific printer based on the work center that the thin client is located in. The barcode app was designed to route the labels based on the device name (Windows name) of the system that the barcode transaction originated from.
I have a full blown Windows XP Pro system also running the barcode app and I have no problem with the label routing because each of those type systems has a unique name that I can use for routing. Where I’m running into a problem is that the barcode app running from the thin clients, appears (from the barcode app’s point of view) to running from the Terminal Server not the individual thin clients.
Does anyone have any idea how I can pull some type of unique identifier from these thin clients to use within the barcode app to use for routing of the labels?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个棘手的问题。如果您的瘦客户端已经设置了 IP 地址，我想我有一个适合您的解决方案。我发现一篇文章解释了如何获取 RDP 客户端 IP 地址（而不是服务器地址）。如果您通过 NAT，这将会出现问题，但如果您直接使用 RDP 连接，它应该可以工作：
http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/857af1fe-75a4-4845-b989-f18636f296c9/
That is a tricky problem. If your thin clients have set IP addresses though, I think I have a solution for you. I found an article that explains how to get the RDP client IP address (not the server's address). This will have a problem if you are going through a NAT but if you are connecting directly using RDP, it should work:
http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/857af1fe-75a4-4845-b989-f18636f296c9/