Should I bother with thin clients?

Question

Iron

Hey!
There was a question at the enterprise about the re-equipment of the PC fleet. There were thoughts of introducing thin clients into the enterprise, which gave rise to a bunch of different questions.
1. Since the software is different for each user, someone needs AutoCAD, someone needs 1C, someone needs specific software for equipment maintenance. And everyone without exception needs microsoft office, and for everything to spin on Win10. Is it possible to organize this on thin clients?
2. What pitfalls await us?
3. Is it possible to drive each user into AD?
4. Will it all be stupid in a 100Mb network?

Answer 1

You should not bother.
Users to put the most common computers.
You have a lot of software, including specific ones. And all on one server. The server crashes - and the whole enterprise will rise. In this case. Why thin client wrote above.
As for developers - if they suddenly work with ports (protocols) or hardware, then what kind of clients are we talking about? Even virtualization fails. There we will already talk about windows xp, not to mention hardware.
And so typical desires.
Laptops are low power. The screen is small. Or everything is ok - but the price is high. Not rational.
Nettop (small 20x20 cm). And here I would say that all of the above. But that's not the point. You can even find options, but cooling. All models are bad. And there is no place for normal. I declare as a user of these models.
Total, even if the percent pulls - there is no built-in video on it. On graphics-dependent applications, there will be overheating and crazy fan speeds with a typical sound.
Monoblock. Relative miniature - increased price. Complicated repair I need to look for accessories. Average power.
Total optimally normal computer. Cheap, efficient. With a smart selection of components, it is easy to find a replacement for them. No freezes. Supports everything.

Answer 2

Thin clients for 1c operators, sales managers and others. And developers-designers need workstations.

Answer 3

autocad through the terminal - bad business; specific software - first you need to check how it will work; office - no problem; win10 - no way, the terminal server is a windows server, not a dozen.

Answer 4

1) look at a budget laptop - they are equivalent in terms of processor / memory, 10k will work
2) for example, the impossibility of increasing more than 4GB of memory in the board, but you still want it
3) really, especially with a gun and a good word (joke)
4) microtics Gbps are already inexpensive, I don’t remember when non-gigabit cards are inserted

Answer 5

In general, thin clients are not only a terminal. There are also VDI including those with 3D acceleration for AutoCad and the like. But you need to understand what goals you want to achieve. If the main thing is to save money, then most likely a shopping mall with a terminal will come out much more expensive. If you ask if a 100Mbps network is enough for you and if it is possible to drive everyone into AD, then it is clear that you have a small company of 10-100 people. In your case, you don't have to worry about it. At most, you can put accountants on the shopping mall and the terminal to increase security.

Answer 6

Really. But I would feel sorry for the users if possible. A local workstation is always better.

Answer 7

3. Is it possible to drive each user into AD?

a considerable number of people will be surprised - "what happens differently?"
However, an enterprise for a dozen computers - it may not be so ...
All actions must have some kind of meaningful goal. Simply so to tire out in AD - probably really there is no sense. It means that the vehicle has not yet matured that you can administer with your head, not with your feet)
Terminals - again - everything is not just because you wanted to ... and this does not save money ...

Answer 8

A thin client is thin because it works with a terminal server.
Not on your own.
0) You cannot use a thin client with a non-server OS. Not Windows 10, but you will have Windows Server. There are special methods - such as ViTerminal, through which you can turn non-server Windows into server ones.
1) You can install the software that you need on the server (if only this software can work correctly on the terminal server and its license allows it). Of the above doubts, only with AutoCAD, you need to check here (and you don’t even need to buy a thin client - just use the thin client software on a regular computer - WtWare, WtPro; and then buy 1 piece of the "iron" thin client and repeat the check). And Office and 1C - no problem.
3) AD will be only for the user (that is, only for the terminal server), not for the thin client. This is a regular situation.
4) Depends on the number of thin clients. You can check experimentally (and you don't even need to buy a thin client - just use the thin client software on a regular computer - WtWare, WtPro), adding and adding under one. As it ceases to suit - leave the rest on ordinary computers.

Answer 9

IMHO for me:
Thin clients only for office plankton - bukhs, storekeepers, salespeople, secretaries, lawyers, craftsmen, etc. In general, those who have an extremely narrow list of tasks - mainly driving data into yellowprog, excel and the like.
There are only full-fledged system workers in the technical department - you won’t be able to configure the terminal so that it digests autocad normally, especially in 3d and gives it to the user - if there is not enough performance in Cads, then they do clustering, not a terminal.
On the equipment workstations, again, either a full-fledged system unit or a barebone - there is no other way - the terminal works badly with usb printers, and making friends with the machine is still a universal crap and you don’t have to do that.

Answer 10

Make a park of virtual machines,
each user will pull up his virtual machine by domain name
as a Clint piece of iron, we use Fujidsu PCoIP
in a win10 virtual machine and each has its own software
, you can 1s through rdp to the extreme
about network speed, I won’t tell you

Answer 11

The main question you should ask yourself is why?
You can do almost anything, but for this there must be a very specific measurable goal, the achievement of which can be verified.
The use of terminals or VDI (if we are talking about custom OSes) has both a number of advantages and a number of disadvantages, which can only be evaluated relative to the final goal, and not just as a spherical horse in a vacuum.
One thing is for sure, it won't be any cheaper for mass use within a standard business day.

Answer 12

codepen.io/Geyan/pen/VPQgwY?editors=1100 like this