1C terminal mode of operation is a special type of computer system architecture in which a terminal server is used to process data. Terminal clients (user computers) in this mode do not process information, but only receive the result of data processing. Only graphic data for the monitor and data from the mouse and keyboard are transferred from the server to the client and back. As a result, the performance of 1C programs increases several times, and the load on the local network decreases.

Advantages of using 1C terminal server

In addition to the significantly increased speed of 1C programs, switching to terminal mode has the following advantages.

• Requirements for personal computers users. With terminal access to 1C, the enterprise does not need to purchase powerful computers for each user. Only one machine should be sufficiently productive - the server itself. Low-power computers can be used as user PCs without spending additional money on upgrading them. This point may become key, for example, for budget organizations.
• The level of data protection increases. There is no need to worry that the data will be damaged or intercepted during its transfer to the terminal client. Firstly, all traffic is encrypted. Secondly, it is not the information itself that is transmitted, but only its graphic equivalent for the monitor. The data is stored on a secure remote server and does not “travel” across the network. For the same reason, data is insured against loss during network failures. This is especially important when working with a 1C database in file server mode, which is sensitive to power outages.
• The time and costs for administering the information system are reduced. On the server you can create the required number of standard profiles with a specific set of applications. This is much faster than setting up the same number of user PCs. In addition, administration can be remote. The system administrator may be in another city or even country, but can still quickly set up workplace in 1C for a new employee.

With the transition to the 1C terminal server, company employees have the opportunity to work with the accounting program remotely online. The characteristics of the terminal access architecture allow you to connect to 1C using low-speed and even weakly protected communication channels.

Terminal Server is an effective solution for companies that are faced with the problem of limited bandwidth local network. For such companies, Smart Office offers a service

So! Having installed Windows, go to Administrator. If everything is done correctly, we see the “Manage Your Server” window and no (!) activation messages.

Adding the "Terminal Server" role

The list of “roles” (now this is what they call it ;-) of our server is empty. We add a role to our server. The computer simulates searching for something on the local network, and offers us to choose: between the role that we need in HIS opinion and the one that we need in YOUR opinion. Since you and I no longer believe in artificial intelligence and other fairy tales, and our opinion is somehow more valuable to us, we choose: Custom.

In the list of roles that appears, select Terminal Server and click Next. Click Next again, and then OK - confirming your readiness to reboot the computer.

After the reboot, go under Administrator and tell the installation of the terminal server to Finish. Now: in the Managing window your computer a role has emerged: Terminal Server. Although below it is said that: “Since the terminal license server was not found, the terminal server will issue temporary licenses for the connection, each of which will expire after 120 days.”

This situation does not suit us at all, for this reason we are installing a terminal license server. To do this, go to Start → Control Panel → Install and Remove Programs → Windows Components. Check the box next to Terminal Server Licensing. Click Next. After Finish.

Activating Terminal Server:

Now we have a terminal license server installed. But it still needs to be activated!

If you have a corporate proxy, you need to register it in Control Panel → Settings.

Go to Administration → Terminal Server Licensing. We see that the server found on our computer is in the Not activated state.

Right-click and say Activate server. Select the connection type Automatic. We enter our personal data (name, organization, surname, country - strictly those that were entered when Windows installation). I left the next page (E-Mail, address) empty. Click Next and wait.

Activation must be successful. It’s unclear what the point was Microsoft intended in this activation? What is it for, other than collecting statistics? After successful activation, you will be prompted to add licenses. Let's continue.

The Client Access License (CAL) Activation Wizard will launch, which will first go back to Microsoft. Then it will ask for the type of license you want to install. I chose the Enterprise Agreement, and the next step was to ask me for the magic number.

Now you need to specify the product - Windows Server. License type - per Device. The license installed perfectly. Close the Terminal Server Licensing window.

Setting up the server

From the Administration folder, drag out the Computer Management and Terminal Server Manager shortcuts to the desktop. This is not necessary, but it is much more convenient.

Go to Computer Management, create a group/groups of 1c users.

To do this, go to Administration → Terminal Services Configuration. IN Server settings Setting remove the restriction "Restrict each user to one session". In the Connections list, select connections and configure their Properties:

Client Settings tab:

We replace user settings regarding disks and printers with our own:

• connect everything (that is, the top checkbox must be unchecked, and the next 3 must be active and installed);
• Limit color depth to 16 bits;
• Prohibit forwarding of LPT, COM, Audio ports.

Permissions Tab:

• We add the created 1c user groups and give them the rights: Guest Access + User Access, I set it to full.

Close Terminal Services Configuration. Next we do the following:

• Go to My computer.
• We say Propetries on drive C:
• Go to the Security tab
• We say Advanced...
• We remove the rights that allow the Users group to create folders and files.

Go to Control Panel → System. "Automatic update" tab. Disable everything automatic update completely.

Go to Administration → Local Security Settings → Account Policies → Password Policy. Set "Maximum password age" = 0 - it's more convenient.

Go to Computer Management and add yourself as a user.
Let's not forget:

• Password never expires
• Add yourself to 1c user groups.
• Uncheck "Require user`s permission" on the "Remote control" tab

Connect to the server:

We are trying to connect from another computer to the terminal server. To do this, we need to install a client on the computer. XP already has a similar client: “Start → Utilities → Accessories → Communications → Remote control desktop."
Although, even on XP it is worth reinstalling: the client included in Win2003 Server will still be newer.

The client is located in the folder: C:\WINDA\SYSTEM32\CLIENTS\TSCLIENT. it also supports installation on Windows 98. Install it on all machines from which you want to work on the terminal server.

After starting the client, click the "Options" button. For 1c users, you should use the following settings:

"General" tab:

• fill in the computer, username, password fields
• domain (if a network with domains - the domain name, if without domain names - the server name)

Client window for connecting to Windows Terminal Server

"Screen" tab:

• desktop - full screen;
  color palette - 16 bit.

Tab "Local Resources":

sound - do not play;
keys - only in full screen mode;
automatically connect to drives and printers - As you wish.

"Advanced" tab:

• speed - modem 28.8 - must remain 1 tick - graphics caching.

Now these settings can be saved to a file with the RDP extension. Pay attention to the "Save password" checkbox on the "General" tab. This checkbox is available for Win2000 and WINXP operating systems. For others - no. Unfortunately, Win9x users are deprived of the ability to save a password in an RDP file - for this reason, configure your Win9x users so that, with the exception of the 1c password, they will need to enter a Windows password.

What you do with this password is up to you. It is possible to assign one password to everyone, or it is possible to generate your own password for any user. Although, it is extremely better for you to know the password of any user - it will be useful for remote joining and administering sessions.

Once you've configured the connection properly, make sure it works, and if you want, save it to an RDP file (possibly directly to your desktop).

Software installation:

From personal experience I can say that it is worth installing as little software as possible on the server. It is better to install only the most necessary, since the speed of working with the server depends on the number of programs and load.

I would limit myself to installing the following software on the server:

• Total Commander;
• WINRAR;
• XP RUS;
• Software for database assistance (for example MUSCLE).

Everything was installed correctly - that is, through the Control Panel. From Office I installed only Word, Excel and Access. Disabled things like Binder and Office_Panel.

After that, all that remains is to go to “C:\Documents and Settings\Administrator” and “C:\Documents and Settings\All users” and adjust the contents of the folders

• \Start men;
• \Start menu\Programs;
• \Start menu\Programs\Startup;
• \Deskto.

for unnecessary labels.

http://bazzinga.org/js/tiny_mce/themes/advanced/skins/default/img/items.gif); background-position: 0px 0px; ">Install 1c:Enterprise:

We install 1c as always by running the installation.

Create a folder to store future databases. It contains subfolders for the corresponding user groups, into which we transfer the 1c database from the old location.

We check access to the folder with 1c databases:

• Right-click Propetries → Security → Advance.
• All rights must be inherited from the root of the disk: Administrators, SYSTEM and Hosts must have "Full Control", group 1c - "Read & Execute" rights.

• We add rights for the corresponding 1c user group (to which this database belongs). Check all the boxes except:
  Full Control, Delete, Change Permissions, Take Ownership (for "This folder, subfolders and files")
• Thus, our group with “Special” rights will appear in the list of rights

A little secret: if you want someone other than the Administrator to be able to save any of the 1c databases, you need to give this person write rights to the file C:\Program Files\1cv77.ADM\BIN\1CV7FILE.LST .

• right click → Propetries → Security → Advanced
• add rights for the 1c-Admins group: Check all the boxes except: Full Control, Delete, Change Permissions, Take Ownership

When you first start 1c, you may encounter the fact that 1c did not want to accept its own metal security key. When starting up, it thinks for a long time, and later writes: “The security key was not found” - and falls out.

However, I have not heard from other people about such problems. Installing the HASP driver emulator will help you. However, that's a different story!

Leave your comment!

1C for many system administrators It has always been and remains a headache. The 1C terminal server, as one of the key nodes, requires increased attention, because financial activities are tied to it. So I recently had the task of collecting all my eggs in one basket - all the accountants on one terminal server. At the same time, there is no data about what resources - CPU, RAM, disk iops - are consumed by client applications.

I couldn’t find anything on official resources other than compatibility with operating systems. Having already had accountants' PCs and the ZABBIX monitoring server working for a long time, I decided to act a little differently and started collecting real data. Actually, this was the only thing available to me.

You will find other articles about 1C in the corresponding section -.

On the Internet, many companies offer on their website to select a terminal server configuration for a certain number of 1C users, but none of these sites indicate the nature of the load on the server - it is not specified whether users plan to run something else besides 1C, it is not written for what type client (thick or thin), the configuration is being calculated, etc. All this in no way inspires confidence in the correct selection.

To understand on what hardware to deploy the terminal server, I decided to collect performance data on all PCs in the accounting department for a certain period.

The task sounds like this: collect CPU power consumption data and random access memory on each accounting PC.

Conditions: Each accounting employee uses 1C (from 2 to 8 copies of the program are open at a time, on average 6. One of these programs is a 1C thick client, all the others are thin clients). From time to time, accountants use Excel to download and analyze data, and a browser to work with bank clients. No resource-intensive applications are launched. Exactly the same software will be launched in terminal sessions.

What we have: Each accountant has a Core i5 4460 or an equivalent processor, 8GB RAM, OS - Windows 8.1.

Processing power

So, I present to your attention a graph of the processor load of each accounting PC:

Gaps in charts are quite normal, since accountants do not work at night and on weekends. Or they work, but not all of them.

Conclusion on processor power: judging by the graph (green line), the average load on the CPU does not exceed approximately 5% - some have more, but there are examples with less consumption. 5% is on average the minimum that everyone needs.

Clarifications: we must take into account the fact that the OS itself also consumes processor power. On a terminal server there will be only one such system, regardless of the number of users, but if you measure a single PC, then from the final results you will need to subtract approximately 1%, which is spent on operating the system. In total we get 4%.

What you didn't take into account: the load on the terminal server OS will most likely increase in proportion (or with some coefficient) to the increase in the number of users, so maybe I deducted this 1% in vain. Someone may wonder why I took the load purely offhand, roughly. Because it seems to me that the exact average value will still not reflect the situation in a more correct way, since too much influence on productivity from “third” forces is involved in these measurements (to begin with, many Windows Services 8.1 will not be available on the terminal server at all and vice versa). Intermediate output:

We continue to analyze the situation. You can also notice from the graph that when you turn on the PC, there is an increased consumption of resources and this is normal, since at this moment services start, users launch the software necessary for work, and load data. Below is a graph of CPU load on the same PCs, but the emphasis is on the moment the system boots (highlighted in red):

Thus, we can say that the CPU load when turning on the PC is around 30%. This does not mean that now each accountant’s terminal session needs to reserve equivalent capacity. This means that you need to reserve 30% one-time for everyone. This implies that all accountants will not log into the terminal server at once, but for quick launch For the necessary software, you need to have 30% of the equivalent Core i5 4460 power in reserve. Intermediate output:

Required CPU reserve above the average load of each workstation - 30% CPU

The situation with the required processor power gradually began to become clearer; now it is necessary to determine the need for RAM.

RAM

Here everything is much simpler - you need to subtract approximately 512MB from the consumed RAM of the accountant’s workplace - this is exactly how much Windows 8.1 consumes without load. Let's summarize all the data in one list:

1. RAM consumption Windows 8.1 OS - 512MB;
2. The minimum RAM required for the terminal server to operate without load is 2GB;

Thus, the formula for determining the required amount of RAM is:

TS Server RAM = (RAM bk -512) * N + 2048

Where RAM boo— the average amount of memory consumed by one accountant’s workstation; N— number of jobs for accountants.

A little more detail about the first parameter:

Above are the graphs free volume RAM at each workplace of accounting employees.

RAM output: The average amount of occupied memory based on 8GB per workstation (do not look at the scws44 graph, this PC has 4GB, not 8GB) is 2.5GB. If we subtract 512MB (OS) from this volume, we approximately get:

RAM consumption (without the volume occupied by the OS) at the accountant's workplace = 2GB

Clarifications: Of course, this value is approximate and will still change in a real situation. Also take into account the amount of memory that administrators may need, because their sessions on the terminal server will also take up resources, albeit small ones.

What you didn't take into account: The OS may periodically require volumes in excess of what it needs. For example service processes TrustedInstaller.exe or svghost.exe or any others periodically pump out significant amounts of RAM, you definitely need to reserve something for them too.

It would seem that all the tasks have been completed, but no, there are still some left. About them below.

Discs

The load on the disk subsystem in the case of a terminal server will be reduced mainly to reading data and therefore the requirements for disks are not as stringent as, for example, in the case of a DBMS. The average load of a regular desktop disk (WD Blue) of an accountant’s workplace is shown in the graphs below:

Please note that in the graphs inactivity time is displayed(idle time). Inactivity of 95% indicates that the actual disk utilization is only 5%. Intermediate output:

The average load on a single disk of an accountant’s workstation is 5%

Disk output: If you do not take into account short-term peaks, the average load on the disks is 5%.

Clarifications: In this average value, a significant share is occupied by the needs of the operating system.

What you didn't take into account: The most competent way to assess disk needs is to evaluate performance in input/output operations per second (iops), which I, however, will prefer to abandon for the purposes of this article. I/O operations and disk utilization percentages typically do not have a linear relationship with each other (or do not always do so). It all depends on the nature of the load. In my case, the existing performance evaluation is quite sufficient.

Terminal server 1C - configuration selection

First, we need to find out the performance rating of the reference processor, which we took as a basis for our measurements. In my case, this processor is Core i5-4460, which is installed on almost every employee in the accounting department. Its performance rating, according to the website www.cpubenchmark.net, is 6622.

Based on the calculations of the previous chapter, we determine the required processor power:

4% * 7 (the number of accountant jobs in my case) + 1% (for the OS) + 30% = 59% (compared to Core i5 4460).

You also need to take into account the fact that from time to time accounting employees make large data downloads from 1C, which takes up quite a lot of resources - usually at least one physical processor core. That is, in our case, 25% of the performance of the reference CPU. As a result, the actual required power is already 84%.

A little explanation: Almost no one selects processors based on the fact that they are loaded at 84% or so. For example, I consider CPU utilization equal to or higher than 85% to be critical. In my practice, I usually select the processor power so that when performing the required tasks, the load on it does not exceed 60% on average.

6620 * 0,84 / 0,6 = 9268

That is, specifically for my task with my conditions, a minimum is required Intel Xeon E3-1240 V2 @ 3.40GHz. This CPU will provide the performance you need, plus a little headroom for the future.

UPD: 07/15/2016:

The amount of RAM will be 16GB (for 7 workstations of accounting employees, calculations are given above). It should be noted that this is the minimum required volume. It is still advisable to have a reserve so that applications and the OS do not start swapping and destroy the disk subsystem. Perfect option will be 2 sticks of 16GB, only 32GB - almost any server motherboard supports this capacity.

Based on the load on the disks (see above), the performance of two SATA disks will be sufficient. If we talk about arrays, then, as a rough approximation, RAID 10, 1E, 5 configurations are suitable. I traditionally choose RAID 10 - for this option you need at least 4 disks.

To reduce the overall cost of equipment, you can get by with SATA disks, but not desktop ones, but empty and the cheapest, but enterprise-level ones. Since the reliability of these drives is an order of magnitude lower compared to classic SAS, RAID 10 will come in handy.

So, the terminal server configuration for 7 to 10 accounting employees (1C, Excel, browser, mail) is as follows:

Intel Xeon E3-1240 V2 @ 3.40GHz, 32GB RAM, 4*SATA in RAID10

1C terminal server is a system solution that allows you to significantly speed up the joint work of several users with the 1C program. Due to the nature of the program, its simultaneous use by several employees leads to slow loading of information and even data loss. In companies, such failures lead not only to inconvenience, but also to significant financial losses. Increasing the capacity of the local network does not produce results, since the problem lies in the 1C program itself, which repeatedly sends large amounts of unnecessary information from address to address. To redistribute the load and efficient work systems, it is recommended to install 1C terminal server.

Such a change in the network operation scheme will allow you to quickly access the 1C database without downloading it to the user’s work computer. In this case, work can be carried out in remote access. Each user receives an access password and can work under their own account from any computer without losing their personal settings of the 1C program.

How to choose a server for 1C 8.3 (8.2)

1C products can be quite resource-demanding. Terminal server 1C 8.3 (8.2) allows you to make the operation of this software complex more reliable and faster. You need to choose a terminal server for 1C 8.3 (8.2) based on how many users regularly work in the system, as well as based on the load on the server.

Creating a 1C server with terminal access allows you not to change user computers to more powerful machines. Also, the application and database can be accessed remotely. This gives users a wide range of options.

Installing 1C on a terminal server is a set of several simple operations. The software package is installed as a regular application. Setting up a 1C terminal server includes adding users to the system and allocating memory for applications.

For a terminal server to work effectively, it must be configured correctly. Basic parameters for working with the network and other characteristics important for configuration are indicated in the 1C terminal server configuration.

Recommendations for completing terminal servers from Trinity

The company has developed several options basic solutions for companies of various sizes. However, in each case it is necessary to select the complete package individually based on the requirements of the company and its current technical base.

Organizations with 30-50 users
With such a number of users, at least two servers are needed. One works with the database, the second with terminals. In some cases, a dedicated application server may be required. The number and volume of disk bays will depend on the specific company - its load, technical equipment and growth rates.

Organization with 50-100 users
In this case, you will need a terminal system of three links, in which 3-4 servers will operate. Terminal servers can be interchangeable in case of failure in one of them.

Reliable cluster configurations
Fault-tolerant systems are most reliable for companies where operational agility is critical. Cluster servers combined into one system can restart each other's processes in the event of increased load or failure of one of them. Such a scheme will require a supply of RAM and processing power; combining the components into a system is possible using Windows. The database requires backup copy, which is best placed on an external storage system. Having a storage system will make it possible to reduce costs on server performance.

For each of these solutions it is possible to select certain configurations. Models of servers and other components, depending on the number of users and the chosen scheme, can be quite economical.

The implementation of a terminal system will help in solving a whole range of problems:

• Improving the reliability of the 1C program. Failures in the operation of an individual user computer will no longer lead to downtime, because enter your account can be done from any device, even remotely.
• Possibility of saving time on maintenance. The new scheme allows for remote administration.
• Access to the database via the Internet will make it possible to create operational work with freelancers.
• Increasing reliability and safety of operation due to data redundancy and interchangeability of system components.
• There is no need to increase the productivity level of user machines, since all basic and energy-intensive operations are carried out on the main terminal.

Here we will look at how to configure 1-C via remote desktop connection(RDP), i.e. using a terminal server on the Windows Server 2003 operating system.

This procedure is for those who do not use special database servers designed for 1-c, but simply use the usual 1-c configuration located on the server and connect to it via a local network indicating the database path. This is mainly how they work in small offices, and when using this connection method, 1-C works quite slowly, and that is why I will describe the process of how you can increase the speed of the program in a fairly simple way.

So, first you must have a good powerful computer, and best of all, a real server with an installed operating system Windows system Server 2003 and higher. In it you must configure the terminal server, it is configured as follows:

Start->Administration->Manage this server ->add or remove a role ->click next ->select a special configuration ->opposite the terminal server you have “no”, just select and click next -> then a reboot will occur -> then create users to the group " Remote Desktop Users"and you can connect ( example more detailed installation and terminal server settings can be found in the article - Installing a terminal server on Windows Server 2008).

Now we set up the connection on the client computer, to do this you run “ remote Desktop» Start -> Programs -> Accessories -> Remote Desktop Connection ( RDP client). In the window that appears, in the field “ computer" or " server» write the IP address or name of the computer on which the terminal server and, accordingly, the 1-C database itself are installed.

After logging in you will be asked to enter “ user" And " password» ( You should have already created them on the server). Then, finally, that same remote desktop will open for you. First, find where you have the shortcut or exe file to launch 1c, copy the path, for example it will be D:\BIN\1cv7s.exe and save it. Then disconnect ( You always need to press start->exit system because... if you just close by X it will be incorrect).

Next, you launch the remote desktop again and click the “ options" and fill in the fields " user" And " password", so that you don’t have to enter it every time you connect. Then go to the program tab and check the box next to “start the program when connected” and paste the same path that you saved ( in our example D:\BIN\1cv7s.exe). Let's look at the pictures:

Now you can connect, and already at this launch you will start the 1-C program, but already on remote computer, i.e. server. All you have to do is configure the path to the database. But remember that we are on the server and, accordingly, the database is also on the server, and we will show the path locally, and not over the network.

If you do everything correctly, then you yourself will notice that the speed of 1-C will increase, since the client computer is no longer using its own resources, but the resources of the server. This method connection is great for small offices where approximately 50 people work in the 1-C program; to be honest, we simply haven’t tried it anymore because there are simply no people.