In principle, the sequence of steps is not very different from installing Terminal Server on Windows Server 2008 R2, but there are some significant differences. So:
0. What you need:
- A computer (server) with Windows Server 2012 installed on it and administrator rights on this server.
- A valid Terminal Server CAL purchased through one of the existing licensing programs. (In this article I will use the agreement number found on the Internet for the Enterprise Agriment program. At the time of this writing, the workers were numbers: 6565792, 5296992, 3325596, 4965437, 4526017.)
- Access to the Internet for activating the licensing server and installing licenses (activation by phone is also possible).
1. Installing Remote Desktop Services
Launch Server Manager. It can be launched from the shortcut on the taskbar, or by running the command servermanager.exe(To do this, press the key combination Win + R, in the window that appears in the field “ Open» ( Open) write the name of the command and press " OK»).
In the menu, in the upper right corner, select “ Control» ( Manage) - « Add roles and components» ( Add Roles and Features) .
Will start " Add Roles and Features Wizard» ( Add Roles and Features Wizard)... Click " Further» (Next) on the start page.
Leave the switch on " Installing Roles and Features» ( Role-based or features-based installation) and again press “ Further» (Next).
We select the server from the server pool on which the Terminal Service will be installed. In my example, this is the given local server. Click " Further» (Next).
We celebrate the role of “ » ( Remote Desktop Services) in the list of roles and click " Further» (Next) .
We leave the components as they are. Without noticing anything, click " Further» (Next) .
We read the description of the Remote Desktop Service and click " Further» (Next).
Now you need to select the role services to install. At least it will be useful to us " Remote Desktop Licensing» ( Remote Desktop Licensing) (we also agree to the installation of additional components by clicking on " Add components» ( Add Features) in the appeared wizard)
and " » ( Remote Desktop Session Host) (again agree to the installation of additional components by clicking on " Add components» ( Add Features) in the window that opens). Having marked the required role services, click " Further» (Next).
All the parameters for installing the role are defined. On the last page, set the flag “ Automatically restart the destination server if required» ( Restart the destination server automatically if required), confirm the choice by pressing " Yes» ( Yes) in the window that appears and click " Install» ( Install) to start the installation of the service.
If everything went well, after rebooting, we will see a message about the successful installation of all selected services and components. Click " Close» ( Close) to complete the wizard.
2. Defining a licensing server for Remote Desktop Services.
Now let's run " "(RD Licensing Diagnoser). This can be done from the server manager by selecting in the upper right menu “ Funds» ( Tools) - « Terminal Services» — « Remote Desktop Licensing Diagnostic Tool» ( RD Licensing Diagnoser) .
Here we see that there are no licenses available yet because the licensing mode for the RD Session Host server is not set.
The licensing server is now specified in local group policies. To start the editor, run the command gpedit.msc.
The Local Group Policy Editor will open. In the tree on the left, open the tabs:
- « Computer configuration» ( Computer Configuration)
- « Administrative Templates» ( Administrative Templates)
- « Windows components» ( Windows Components)
- « Remote Desktop Services» ( Remote Desktop Services)
- « Remote Desktop Session Host» ( Remote Desktop Session Host)
- « Licensing» ( Licensing)
- « Remote Desktop Session Host» ( Remote Desktop Session Host)
- « Remote Desktop Services» ( Remote Desktop Services)
- « Windows components» ( Windows Components)
- « Administrative Templates» ( Administrative Templates)
Let's open the parameters " Use Specified Remote Desktop Licensing Servers» ( Use the specified Remote Desktop license servers) by clicking 2 times on the corresponding line.
In the window for editing policy settings, move the switch to " Included» ( Enabled). Next, you need to define a licensing server for Remote Desktop Services. In my example, the licensing server is on the same physical server. Specify the network name or IP address of the license server and click " OK» .
Next, we change the policy settings " Set Remote Desktop Licensing Mode» ( Set the Remote licensing mode). We also set the switch to " Included» ( Enabled) and specify the licensing mode for the RD Session Host server. There are 2 options:
- « Per User
- « Per Device
In order to understand how these modes differ, consider a simple example. Let's say you have 5 licenses. In the mode " Per device»You can create an unlimited number of users on the server who can connect via Remote Desktop only from 5 computers on which these licenses are installed. If you select the " Per user”, Then only 5 selected users will be able to enter the server, regardless of which device they are connecting from.
We select the mode that is most suitable for your needs and click " OK» .
After changing the above policies, close the editor.
Back to the snap " Remote Desktop Licensing Diagnostic Tool» ( RD Licensing Diagnoser) and we see a new error indicating that the licensing server is listed but not enabled.
To start the licensing server, go to " » ( RD Licensing Manager). You can find it in the Server Manager, the tab " Funds» ( Tools) - « Terminal Services» - « Remote Desktop Licensing Manager» ( Remote Desktop Licensing Manager) .
Here we will find our licensing server, with the status “ Not activated» ( Not Activated). To activate, click on it with the right mouse button and select “ Activate server» ( Activate Server) .
The Server Activation Wizard starts. We press " Further» (Next) on the first page of the wizard.
Then we select the connection method (" Auto» ( Automatic connection) by default) and click " Further» (Next).
Enter information about the organization (these fields are required) and then click " Further» (Next).
Enter additional information about the organization (optional) and click again " Further» (Next) .
The license server is activated. Now the licenses should be installed. To do this, click " Further» (Next) leaving the flag " Run the license installation wizard» .
3. Installing Licenses on the Remote Desktop Licensing Server
Then we select the licensing program you need. In my example, this is “ Enterprise Agreement"". We press " Further» (Next) .
We indicate the product version, license type and number of licenses in accordance with your licensing program. We press " Further» (Next) .
Well, we are waiting for the completion of the license installation wizard with a message that the requested licenses have been successfully installed.
In the licensing manager, we make sure that the server is running, and also see the total and available number of installed licenses.
And finally, we return to " Remote Desktop Licensing Diagnostic Tools» ( RD Licensing Diagnoser) and we see that there are no errors, and the number of licenses available to customers corresponds to what we entered in the previous step.
This completes the installation of Terminal Server on Windows Server 2012.
So! Having installed Windows, go to the Administrator. If everything is done correctly, we see the "Manage Your Server" window and no (!) Activation messages.
Add the "Terminal Server" role
The list of "roles" (now it is called that ;-) of our server is empty. Add a role to our server. The computer simulates the search for something there on the local network, and offers us to choose: m / y the role that we need in HIS opinion and the one that is needed in YOUR opinion. Since we no longer believe in an artificial mind and other fairy tales, and our opinion is somehow more dear to us, then we choose: Custom.
In the list of roles that appears, select Terminal Server, and click Next. Press Next again, and after OK - confirming our own readiness to restart the computer.
After rebooting, go under Administrator, and tell the installation of the terminal server Finish. Now: in the Managing your computer window there is a role: Terminal Server. Although it is said below that: "Since no terminal license server was found, the terminal server will issue temporary connection licenses, each of which will expire within 120 days."
This situation does not suit us in any way, 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.
Terminal Server Activation:
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, say Activate server. Select the connection type Automatic. We enter our personal data (name, organization, surname, country - strictly those that were entered during the installation of Windows). I left the following page (E-Mail, address) blank. Click Next and wait.
Activation must be successful. It is unclear, what is the point, Microsoft put in this activation? What is it for, except for collecting statistics? After successful activation, you will be prompted to add licenses. Let's continue.
This will launch the Client Access License (CAL) Activation Wizard, 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 I was asked for a magic number.
Now you need to specify the product - Windows Server. License type - per Device. The license was installed perfectly. Close the Terminal Server Licensing window.
Setting up the server
From the Administration folder, pull out the Computer Management and Terminal Server Manager shortcuts to the desktop. It is not necessary, but it is much more convenient.
We go to Computer Management, create a group / user groups 1c.
To do this, go to Administration → Terminal Services Configuration. Remove the restriction "Restrict each user to one session" in the Server Setting. In the Connections list, select connections and configure their Properties:
Client Settings tab:
We replace the user settings for 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;
- Deny forwarding of LPT, COM, Audio ports.
Permissions Tab:
- We add the created 1c user groups and set them the rights: Guest Access + User Access, I set the full one.
Close Terminal Services Configuration. Then we do the following:
- We go to My computer.
- Talking Propetries on drive C:
- Go to the Security tab
- Talking Advanced ...
- Remove the rights that allow the Users group to create folders and files.
Go to Control Panel → System. "Automatic Updates" tab. Disable all automatic updates completely.
Go to Administration → Local Security Settings → Account Policies → Password Polisy. Set "Maximum password age" = 0 - it's more convenient this way.
We go to Computer Management, add ourselves as a user.
Don't forget:
- Password never expires
- Add yourself to 1c user groups.
- Uncheck "Require user`s permission" on the "Remote control" tab
We 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 Desktop Control".
Although, even on XP it should be reinstalled: the client in Win2003 Server will still be newer.
The client is located in the folder: C: \ WINDOW \ SYSTEM32 \ CLIENTS \ TSCLIENT. it 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, the following settings should be applied:
General Tab:
- fill in the fields computer, username, password
- domain (if a network with domains - domain name, if without domain names - server name)
Client window for connecting to a Windows terminal server
"Screen" tab:
- desktop - full screen;
color palette - 16 bit.
"Local Resources" tab:
sound - do not play;
keys - only in full screen mode;
automatically connect to disks and printers - As you please.
"Additional" tab:
- speed - modem 28.8 - 1 tick must remain - graphics caching.
Now these settings can be saved to a file with the RDP extension. Pay your 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 that, with the exception of a 1c password, they will need to type a password on Windows.
How to deal with this password is up to you. It is possible to assign 1 password to all, 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 come in handy for remote connection and session administration.
With your connection configured 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. Better to put only the most necessary, since the speed of work with the server depends on the number of programs and the load.
I would limit myself to installing the following software on the server:
- Total Commander;
- WINRAR;
- XP RUS;
- Software to help the database (for example, MUSKUL).
All software 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, it remains to go to "C: \ Documents and Settings \ Administrator" and "C: \ Documents and Settings \ All users" and correct 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 for storing future databases. It contains subfolders for the corresponding user groups, into which we transfer the 1c base from the old place.
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.
- Add rights for the corresponding 1c user group (which owns this base). We put all the checkboxes, except for:
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 permissions to the file C: \ Program Files \ 1cv77.ADM \ BIN \ 1CV7FILE.LST ...
- right click -> Propetries -> Security -> Advanced
- add rights for the 1c-Admins group: We put all the checkboxes, except for: Full Control, Delete, Change Permissions, Take Ownership
When you first start 1c, you may be faced with the fact that 1c did not want to perceive its own metal security key. At startup, he thinks for a long time, and later writes: "The security key was not found" - and falls out.
However, I have not heard about such problems from other people. Installation of the HASP driver emulator will help you. However, this is a different story!
Leave your comment!
Installing Terminal Services
We enter the server with administrator rights.
Open "Server Manager" -> Roles -> Add Role:
In the list of available server roles, select Terminal Services:
In the list of "Role Services" check "Terminal Server" and "Terminal Services Licensing". These services are sufficient to support basic functionality.
It is advisable to install a terminal server prior to installing custom applications. We are warned about this in the next step:
Authentication method. "Require authentication at the network level" - this option provides increased security, but in this mode users with outdated clients (rdp 5.x and below), as well as users connecting through Explorer (remote desktop web connection), will not be able to connect to the server. To support all versions of clients, select the Do not require network authentication option.
Licensing mode. It is advisable to decide in advance on the licensing mode: "per user" or "per device". User licenses are effective if the organization has a large number of mobile users who need access to the server both from the corporate network and from a remote one (home, another office). Device licenses are effective when users are tightly bound to their workplaces.
Groups of users. Here you can immediately specify the groups or individual users who will be allowed access to the terminal server. You can do this later by simply adding the desired users to the Remote Desktop Users group.
Configuring a license server. If the server is not included in the domain, then there are no particular options:
Overview of selected options before installation. Please note that the system warns us that after installation, the enhanced security option of Internet Explorer will be disabled. Moreover, enhanced security will be disabled only for regular users (it will not be disabled for administrators). After you finish installing Terminal Server, be sure to turn it back on.
The next step is to activate the terminal server.
Terminal Server Activation
Open Start -> Administrative Tools -> Terminal Services -> "Terminal Services Licensing Manager". Select the license server from the list. We make a right click, and in the menu, select the "Activate server" item:
The Server Activation Wizard starts:
In the next step, we select the connection method. You can safely choose "Auto-connect":
Information about the organization. Enter the name, surname and organization name:
Additional information. You can fill in, or you can ignore:
After a few seconds, your server will be successfully activated:
Now you can proceed to installing licenses. It should be noted that after activating the license server, there is no need to immediately purchase and install licenses. In the absence of full-fledged licenses, the server works in demo mode. Users are issued temporary licenses for 120 days.
Installing licenses
Launch the license installation wizard. This can be done immediately after activating the license server by selecting the appropriate option, or by opening Start -> Administrative Tools -> Terminal Services -> "Terminal Services Licensing Manager" -> Select your license server -> Right Click -> Install Licenses.
Enter the agreement number:
Select the product version, license type (must match the previously selected license server license type), number of licenses:
We check the installation of licenses in the licensing manager:
Terminal Server is ready to go.
What's the difference between Remote Desktop and Terminal Server?
Remote Desktop on Windows Server is the same RDP, but only for administrators. This tool is available immediately after server installation and does not require additional installation. A maximum of two administrators can remotely connect to the server at the same time.
Terminal Server - needed to connect ordinary users in an amount limited only by purchased licenses, well, and by the server's performance.
Where can I change the general connection settings?
Open Server Manager -> Roles -> Terminal Services Configuration -> Right Click on RDP-TCP -> Properties:
How do I allow a new user to access Remote Desktop?
Open Server Manager -> Configuration -> Local Users -> Users. Open the properties of the user who needs access, the Group Membership tab. Add the Remote Desktop Users group:
Are there settings that do not apply to everyone, but to individual users?
Yes, see user properties, tabs: "Remote Control", "Terminal Services Profile", "Sessions".
Is it possible to create several independent connection sessions under one account?
It is possible, but by default this option is disabled (to save resources). Open Server Manager -> Roles -> Terminal Services Configuration -> Change Settings (on the same page). Double clicking on an option opens a window where you can make changes:
How to use the remote session control feature?
Remote control is only possible for administrators. And most importantly, for this function to be available, the administrator must be connected to the server via a remote desktop. If you are sitting directly at a computer (console session) and want to log into a user session connected to the same computer, then here you will be disappointed.
What port does RDP use by default and how can I change it?
The default port is TCP 3389. You can change it by editing the registry. Open a branch
HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ TerminalServer \ WinStations \ RDP-tcp
and change the parameter PortNumber.
Let's consider one more case of interaction between the server and the client. It will be about the so-called "server-terminal" architecture. Its meaning is that absolutely everything happens on the server: the operating system is running, application programs are running, files are being opened. In order for terminal clients to connect to a server computer, a terminal server program must be running on it, and such connections must be allowed in the security settings.
The user, on the other hand, works at the terminal - the client, which displays what is happening on the server on its screen and transmits commands from the keyboard and mouse in the opposite direction. Only the terminal program is running on the client. The most famous example of such a program is Remote Desktop- a standard tool included with any version of Windows (Start → All Programs → Accessories → Remote Desktop Connection).
Let's make a reservation right away: remote control of a computer, connection to a remote desktop, and a terminal-server scheme are one and the same. The only difference is in the goal: do you want to configure, administer a remote computer, or are going to work on it while sitting at another computer.
Let's start with the simplest application of this scheme. For example, in the office on a computer, working applications are installed, resource-intensive, expensive and very specific. All your working documents are also located there. From time to time there is a need to see or do something while at home or somewhere else. Of course, you can install the same applications on a laptop (we will modestly keep silent about licenses), but what about the documents? You will have to constantly monitor changes, copy the latest edited versions from computer to computer - confusion is inevitable. If we are talking about an accounting program like 1C, the problem becomes even more complicated.
What can be done? The solution is standard, although for some reason many have not even heard of it.
- Allow remote control on the computer in the office.
- Configure routing on the gateway so that clients can connect to this computer over the Internet. If the client is on the same local network, this step is skipped.
- Connect from laptop to office computer.
To enable remote control in Windows 7, in the System window (Start → Control Panel → System) select the link Additional system parameters... A dialogue will open System properties... Go to the tab in it Remote access and set the switch Remote Desktop in one of two positions allowing remote connection to this computer (Fig. 8.13).
By default, users with administrator rights already have the right to remotely control the computer. However, for everyday tasks, it is highly recommended to create a limited account and work only under it. Therefore, the account you usually work under must be added to the Remote Desktop Users group.
- To allow a standard user remote control, click Select users ....
- A dialog box will open Remote Desktop Users... Press the button in it Add... In the child window that opens, enter the name of your "everyday" account.
- Click the button OK in this and all previous dialog boxes. This completes the configuration of the server computer.
By default, the system does not allow remote logins for users with a blank password. This makes sense: by enabling remote access, you open a wide gateway for unauthorized logins from outside, including from the Internet. If you want to use Remote Desktop, your account, like the administrator account, must be protected with passwords. Preferably, not the most simple ones!
Now let's connect to the remote desktop. On another computer, such as a laptop, start Remote Desktop Connection: Start → All Programs → Accessories → Remote Desktop Connection. In the window that opens, click the button Options to display all the tabs and settings (Fig. 8.14).
In field A computer enter the IP address or name of the computer you want to connect to. In field User specify the name of your account on the server computer. In the tab Screen the parameters of displaying the remote desktop during the session are configured: resolution and color depth. In the tab Local resources selects which devices on this computer will be connected to the remote computer as if they were connected directly to it. For example, if the Printers check box is selected, the server will be able to print to a printer that is physically connected to your laptop.
Click the button To plug... You will be prompted for a username and password. As a result, you will see the desktop of the remote computer in the terminal window. If full screen mode was selected in the settings, the image will be expanded to full screen. The fact that you are now working on a remote computer will be reminded only by a small connection bar at the top edge of the screen.
To save the created connection, open the dialog again Remote Desktop Connection, check the options and in the tab General press the button Save as…... Specify the path and file name - connection settings will be saved as a file with the RDP extension. After double-clicking on such a file, the connection with the saved parameters will be launched immediately. If in the settings on the tab General the checkbox was checked Allow me to save credentials, you only need to enter the username and password for the first time - the system will "remember" them. If the check box is cleared, the username and password must be re-entered each time.
In "desktop" versions of Windows, there is a limitation: only one user can work on a computer at a time. It doesn't matter if he is logged in locally or via Remote Desktop. As soon as you connect to the remote desktop, the local session will be disconnected: a welcome screen will appear on the monitor screen. Conversely, if you now log on locally, your remote desktop session will be terminated immediately.
The solution to the initially set task - to use one computer from another - does not interfere. While you work on your office computer remotely from a laptop, the local user is resting. When you disconnect the session, it can continue working. Actually, the creators of Windows intended it that way.
Sometimes a more difficult task arises - to provide remote work of several users at the same time. For example, you need to make it so that several employees from the branch can work in parallel with programs on one of the computers in the head office. The possibility of simultaneous operation of several remote users is provided in server operating systems - Windows Server. The principle is practically the same, its implementation is slightly different. Most likely, you will entrust the setup to a computer specialist, so we will limit ourselves to listing the stages.
- The configuration wizard instructs this server to play the role of a terminal server.
- The server creates accounts for each of the remote users.
- Permissions are assigned for each of these users.
- Terminal Licensing Service is activated and configured.
Simultaneous logon of multiple users can also be enabled on "desktop" versions of Windows. How to turn Windows XP or Windows 7 into a "terminal server" is easy to find on the Internet. The procedure is not entirely legal, as it violates the terms of the license. True, the regulatory authorities rarely pay attention to the fact that you have unlocked the possibility of simultaneous terminal access - they are more interested in the presence of a sticker on the case and title documents.
Where do Terminal Access and Remote Desktop Diagrams come in handy?
We have already considered two cases: working from home and connecting branch employees. Here are two more examples.
For aesthetic reasons, you have decided to install small, elegant nettops or thin clients in your workplaces. In this case, a terminal server is a must! The company uses some resource-intensive and expensive application, such as CorelDRAW, AutoCAD, Grand Smeta, etc. Several employees need it, although not at the same time. Since you have a license for one workplace, the program is installed on one computer. Of course, you can "sit down" on it in turn, but it is more convenient to simply connect to this computer from different workstations via a remote desktop.
A terminal server can be a solution to the problem for organizations where the number of users is large, but the computing power of workplaces is insufficient. Also, the configured server solves the problem of administration and installation of the 1C client.
How to set up a terminal server for 1C
For the stable operation of 1C, it is necessary to prepare a fleet of very powerful computers and servers. As the number of users and the depth of implementation of 1C products grow, the appetites for configurations increase. Sooner or later, the possibilities for improving the performance of servers, client machines, and network parameters will run out and you will have to look for other solutions to the performance problem with clients. Terminal server for 1C is one of the working ways to simplify the life of administrators and reduce the requirements for terminal clients.
Using a terminal server for 1C
If you do not use terminal servers, users' computers independently perform calculations for which information is transferred from the database to clients. This process does not depend on the type of database. This type of work requires a serious investment in order to achieve a decent level of performance on the server and workstations.
When working with a terminal server, the client computer plays the role of only a keyboard and a monitor. The network only has to transmit signals from the user's keyboard to the server and display the result of the entered commands from the keyboard back. In this regard, the requirements for their characteristics are significantly reduced. There is no need to purchase and regularly update terminal clients and provide a high-speed connection to the server.
With the growing popularity of 1C programs and an increase in the areas in which this software is being implemented, more and more companies use the 1C terminal server. Saving on technology is far from the only reason why many organizations are leaning towards the option of working with 1C using a server.
Terminal server advantages
In addition to savings due to the reduction in the cost of working clients and the network, the operation of terminal servers allows:
- Increase the computing speed of 1C software and reduce the load on the network. This is critical if you have a file-based database setup. Terminal Server will be faster even with minor operations;
- Ensure the safety of data when the connection between the terminal client and the server fails. After all, not data is sent, but their display. In the event of a failure, clients can simply reconnect to the server and resume from the point at which the network failure occurred. This advantage of terminal servers is important, since 1C programs are sensitive to failures and power outages at workplaces;
- Increase the security of information in the database. It is much more difficult to make a copy of the database from the terminal server under the client, and users connect to the server under unique logins and passwords;
- Simplify the IT structure in the company, which will save time for system administrators.
In addition, the capabilities of server operating systems from Microsoft allow staff administrators to configure the ability to connect terminal clients to the 1C server, so setting up a 1C server is such an important issue.
Installing a terminal server for 1C
For example, let's install a terminal server for 1C in Windows Server 2012:
- You need to go to the connection properties on the server and register the required IP address;
Let's set up a server for 1C
Now we need to configure client user access to the server. For this:
- Install 1C on the server;
- Open Administration. Go to "Computer Management". Go to the "Local Users" section and select "Users". Create a new user on the server;
- In the window that opens, fill in the fields "User", "Full name", "Description", "Password" and "Confirm password";
The terminal server is configured and client computers can connect to it.
Connecting to a terminal server
Connection to the configured 1C terminal occurs via the RDP protocol. Microsoft systems have a built-in tool called Remote Desktop Connection. To find this tool, go to Start - All Programs - Accessories:
In the window that opens, you must specify the parameters:
- In the "Computer" field, enter the address of the terminal server;
- In the "User" field, you must specify the name under which you want to log into this server. Naturally, for this, the user must be allowed remote control;
- In the next window, you will need to enter the user password to access the server.
If the settings are made correctly and the data is entered correctly, a window will unfold, in which you will see a slightly modified desktop.
Further work does not differ from the situation in which 1C is installed on your computer.
