Post by habiba123820 on Nov 2, 2024 3:41:36 GMT -5
First, let's quickly go over the basic terms to make sure we're on the same page If you're an experienced admin, feel free to skip this point.
So:
A terminal server is a hardware server, virtual machine or a whole cluster of servers that have enough computing resources to solve not only their own problems, but also to process requests from other remote computers (terminals). A terminal server is needed to centralize calculations, optimize wordpress web design agency maintenance (indeed, it is easier to update 1C in one place, and not across the entire fleet of equipment) and reduce downtime of computing power (a regular office PC is rarely loaded more than 5-10%, the rest is idle). I will also note an increase in the level of data security, especially physical - after all, all data that is worked with on the terminal server remains on the terminal server.
Thin clients (not to be confused with thin and (further) thick 1C clients) are low-power computers that access a terminal server. They are compact, relatively inexpensive and lack excess computing power, often used without any hard drive (network boot). Their main functions are: to connect the user to the terminal server; to work with input-output devices (monitor, keyboard, mouse, acoustics). Conventionally, ±10% (most of it is spent on image output) of the calculations is on the thin client, and ±90% on the terminal server, but the figures may change depending on the tasks being solved.
Fat clients are full-fledged workstations, independent computers that take on all the calculations. For example, the 1C program can be stored and run locally on a fat client, but all internal 1C data is stored centrally on the server.
Semi-thin clients are full-fledged workstations where employees work with heavy software (CAD systems), but with business software (like the same 1C) work is carried out on a terminal server.
VDI (Virtual Desktop Infrastructure, desktop virtualization) is suitable for both office tasks and resource-intensive ones, such as rendering, 3D modeling, etc. In simple terms, each user gets a dedicated virtual machine. Not a very budget option, but it provides full isolation of employees and solutions using video cards are possible.
RDS (Remote Desktop Services) is a great option for a terminal server from Microsoft for everyday office tasks. All users work on one server (physical or virtual).
NOTE: Almost any PC or even smartphone can take on the role of a thin client (which is especially convenient when working remotely), but a thin client cannot take on the role of a thick client. Therefore, it is not necessary to buy employees special thin clients if the office already has work laptops or old PCs.
Now that we've covered the basic concepts, let's move on.
Do you need a separate terminal server for 1C?
Yes, it is better not to mix everything together and allocate a separate server for terminals. But often they do it differently.
There are many alternatives on the IT market, which gives free rein to system architects and administrators: different vendors, operating systems (OS), technologies, licensing models, etc. In theory, you can choose and do whatever you want, but in practice, everything comes down to the budget. Companies often save money by taking one server and cramming everything into it: databases, mail, web server, 1C file, terminal server... I call such servers a "budget whim."
So:
A terminal server is a hardware server, virtual machine or a whole cluster of servers that have enough computing resources to solve not only their own problems, but also to process requests from other remote computers (terminals). A terminal server is needed to centralize calculations, optimize wordpress web design agency maintenance (indeed, it is easier to update 1C in one place, and not across the entire fleet of equipment) and reduce downtime of computing power (a regular office PC is rarely loaded more than 5-10%, the rest is idle). I will also note an increase in the level of data security, especially physical - after all, all data that is worked with on the terminal server remains on the terminal server.
Thin clients (not to be confused with thin and (further) thick 1C clients) are low-power computers that access a terminal server. They are compact, relatively inexpensive and lack excess computing power, often used without any hard drive (network boot). Their main functions are: to connect the user to the terminal server; to work with input-output devices (monitor, keyboard, mouse, acoustics). Conventionally, ±10% (most of it is spent on image output) of the calculations is on the thin client, and ±90% on the terminal server, but the figures may change depending on the tasks being solved.
Fat clients are full-fledged workstations, independent computers that take on all the calculations. For example, the 1C program can be stored and run locally on a fat client, but all internal 1C data is stored centrally on the server.
Semi-thin clients are full-fledged workstations where employees work with heavy software (CAD systems), but with business software (like the same 1C) work is carried out on a terminal server.
VDI (Virtual Desktop Infrastructure, desktop virtualization) is suitable for both office tasks and resource-intensive ones, such as rendering, 3D modeling, etc. In simple terms, each user gets a dedicated virtual machine. Not a very budget option, but it provides full isolation of employees and solutions using video cards are possible.
RDS (Remote Desktop Services) is a great option for a terminal server from Microsoft for everyday office tasks. All users work on one server (physical or virtual).
NOTE: Almost any PC or even smartphone can take on the role of a thin client (which is especially convenient when working remotely), but a thin client cannot take on the role of a thick client. Therefore, it is not necessary to buy employees special thin clients if the office already has work laptops or old PCs.
Now that we've covered the basic concepts, let's move on.
Do you need a separate terminal server for 1C?
Yes, it is better not to mix everything together and allocate a separate server for terminals. But often they do it differently.
There are many alternatives on the IT market, which gives free rein to system architects and administrators: different vendors, operating systems (OS), technologies, licensing models, etc. In theory, you can choose and do whatever you want, but in practice, everything comes down to the budget. Companies often save money by taking one server and cramming everything into it: databases, mail, web server, 1C file, terminal server... I call such servers a "budget whim."