Answer the question
In order to leave comments, you need to log in
Thin client - what peripherals are supported?
Good afternoon!
Faced with the need to consider the possibility of using thin clients in an organization. It is planned to use ordinary tired PCs, so you will have to configure everything yourself. The question is in choosing the axis for the client, server, as well as the operation protocol.
From here such questions:
1. Support of periphery by the thin client depends on what? What happens if I plug in an exotic device? Should it be "picked up" by the axis on the server or client?
2. Are there any general recommendations for not to mess with the choice? Is it enough Windows server + RDP or just watch some citrix?
Priority - equipment support and economical use of the communication channel.
There are a lot of articles on the net, but the subtleties are described, in my opinion, poorly.
Answer the question
In order to leave comments, you need to log in
as a shopping mall for tired computers, you can look at thinstation (distra is for this). Hardware support will be limited, but worth trying
Worked with oldies (tel on socket 478) using wtware . There were problems on clients at the stage of determining eth - not all old mothers, in principle, saw new adapters and vidyuhi. Further, there were no special problems, the system is very flexible and customizable.
In fact, we get RDP and terminal access at the output. The system costs money, but it is quite lifting. The test version and the combat (paid) version are distinguished by a black banner along the edge of the client's monitor, so to save karma, I advise you to pay the developers a pretty penny anyway.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question