RDP multiple XP sessions. How to enable multiple simultaneous remote desktop connections or sessions in Windows XP

In Windows 8 / 8.1, as well as previous versions of Microsoft client OS, only supported one simultaneous incoming RDP connection. This means that only one user (one session), local or remote, can simultaneously connect to Windows 8 through a remote desktop. In most cases, this is enough, but sometimes I would like to be able to simultaneously work several users at once in our own sessions. A good example can be a computer as a Media Center, when video is played in the console session, and at the same time you need to remotely work with the system without interrupting video on TV.

Council.Remote RDP access does not work at home (Home) Windows editions, you need to edit Pro or Enterprise.

When you try to open the second RDP session to a computer with Windows 8, a message appears that the system has already been logged in the system and its session can be completed.

Council. Pre-in the properties of the computer on the Remote Access tab (Remote), you need to add accounts for the desired users to the local Remote Desktop Users group. Local administrators remote RDP access is allowed by default. After turning on the RDP access to the system properties, Windows Firewall automatically turns on the rules allowing the incoming traffic to port 3389. Sometimes the presence of this rule should be checked manually.

For example, in the server version of Windows, two simultaneous administrative connections with individual sessions are supported (in the case of an organization based on Windows Server of the RDS terminal server, this number can be even more).

However, on the Internet, you can find a special patch that allows you to bypass this limitation. Thanks to this patch, several users will simultaneously connect to the RDP to a computer with Windows 8 / Windows 8.1.

Important. The use of this patch is essentially a violation of the license agreement and the terms of use of Microsoft products. Therefore, all the operations described below you perform on your risk.

So, the patch involves the replacement of the original system file % Systemroot% \\ System32 \\ Termsrv.dll (The library used by the Remote Desktop Services service).

• Windows 8 - TERMSRV.DLL-WIN8.Zip
• Windows 8.1 - TERMSRV.DLL-WIN8.1.Zip

Before replacing the system library, create a backup of the TERMSRV.DLL file with the command:

Copy C: \\ Windows \\ System32 \\ TERMSRV.DLL TERMSRV.DLL_OLD

Now, if something goes wrong, you can always return to the initial configuration, replacing the current file with the original TERMSRV.DLL_OLD.

Download the library archive for your version of Windows.

In Windows 8, you first need to change the following keys in the registry branch HKLM \\ SYSTEM \\ CURRENTCONTROLSET \\ CONTROL \\ TERMINAL SERVER \\:

• fDenytsConnections(DWORD) - 0 (The key allows on the computer)
• fsingLesessionPeruser. (DWORD) - 0

The same operation can be performed from the command line:

REG Add "HKLM \\ SYSTEM \\ CURRENTCONTROLSET \\ CONTROL \\ TERMINAL SERVER" / V FDENYTSCONNECTIONS / T REG_DWORD / D 0 / F REG ADD "HKLM \\ SYSTEM \\ CURRENTCONTROLSET \\ CONTROL \\ TERMINAL SERVER" / V FSINGLESSIONUUSER / T REG_DWORD / D 0 / F

Then go to the catalog C: \\ Windows \\ System32finding a file. termsrv.dll. and open its properties.

By default, the owner of this file is TrustedInstaller And even the administrator has no right to replace it.

Let us turn to the tab Security And click the button Edit.. In the Access List, find a group of local administrators and provide it with full rights to file ( Full Control) And save the changes.

The next step before replacing the library file, open the service management console ( services.msc.) and stop the service Remote Desktop Services.

Copy the TERMSRV.DLL file from the downloaded archive for its version of Windows in the catalog % Systemroot% \\ System32 \\ (with replacement).

Note. Archive for Windows 8.1. Contains two files 32_termsrv.dll. and 64_termsrv.dll., for the 32nd and 64-bit version of Windows 8.1, respectively. Unpack the archive and rename the file for your version of the system in TERMSRV.DLL

After replacing the file, run the Remote Desktop Services service and try to create two RDP sessions with a probated machine under different accounts. If you are all done correctly, two independent sessions of the remote desktop should be opened.

Council. It may be necessary to restart the computer.

Important! Using the probated version of Termsrv.dll has a number of shortcomings. The main of which is when installing the next update of Windows 8.1 / 8, this file can be replaced. Accordingly, it will be necessary to use the Hex editor to patch a new file using the Hex editor, or search on the Internet a ready-made modified file for your Windows Builder.

As a solution that is resistant to replacing the TERMSRV.DLL file when installing Windows Updates, you should use Open Open Source Solution RDP Wrapper Library(Available on Github), which does not rule the TERMSRV.dll file, and is a layer between the Terminal Services and SCM service. You can read more about the use of RDP Wrapper Library.

Windows XP Professional and Windows XP Media Center Edition (MCE) Have a connection service remote Desktop (RDP)which allows you to remotely connect the computer, access and control from another computer or host. However, cars on the operating system Windows XP. Allow simultaneous connect to a remote desktop Only one user who was connected to it, without several sessions remote Desktop Connections or support support.

Whenever the remote user connects through the client to remote desktop (RDC) To connect to the host Windows XP.The local user is turned off with the console lock, or without its permission. Remote DesktopUnlike the Terminal Services Server in Windows Server 2003 and Server 2008, it is designed for a disposable user, regardless of whether it is a local or remote user.

Here hack to unlock one limit which allows multiple simultaneous Remote Desktop Connection sessions in Windows XP Professional and Media Center Edition, using either a prolonged termserv.dll or an old probated termserv.dll assembly version 5.1.2600.2055, so that an unlimited number of users can simultaneously connect to a computer using a remote desktop.

1. Download a copy of the prolonged, which will remove the remote desktop connection restrictions disabled for your version of Windows XP:

Windows XP SP3: TERMSRV.DLL (version 5.1.2600.5512)

To obtain the Termsrv.dll information, the patch typically has the following HEX codes bits that are overwritten into the following values:

00022A17: 74 75
00022A69: 7F 90
00022A6A: 16 90

1. Restart the computer and download the information in safe mode by clicking F8. During the boot and select safe mode . This step is needed only if you are currently using Windows Terminal Services or remote Desktop ServicesThe file system protection must be skipped, otherwise the following error message appears to restore the original Termsrv.dll.

3. Purge B. % Windir% System32 and make a backup (or rename) termsrv.dll. .

4. Mix or delete termserv.dll. in folder % WINDIR% SYSTEM32 DLLCACHE.

5. Copy loaded termsrv.dll. in % Windir% System32 , % Windir% servicepackfiles i386 (if any) and % WINDIR% SYSTEM32 DLLCACHE .

6. Point download and run to merge the registry values \u200b\u200bin Registery, or you can start the registry editor manually and add the following registry options:

"EnableConCurrentSessions" \u003d DWORD: 00000001

"ALLOWMULTSSESSIMS" \u003d DWORD: 00000001

7. Click on the button Start -> Perform And enter the command gpedit.msc. , click ENTER To open the Group Policy Editor.

8. Purge B. Computer Configuration. -> Administrative templates -> Windows components -> Terminal services .

9. Turn off limit the number of connections and set the number of connections in 3 (or more). The setting allows more than one use of the computer simultaneously.

10. Follow Remote Desktop on the Deleted System Properties tab by selecting the switch Allow users to remotely connect to this computer. .

11.Cound fast user switching in Control panels -> user accounts -> Changing user login or shutdown .

12. Upload a computer as usual.

I note if you cannot replace or rewrite the TermServ.dll file - access is denied or file error, turn off the "Termine Services" in the "Services" section of the Administration Control Panel. In addition, each connected physical connection must have its own user account in the target computer, and authentication should be conducted with the appropriate username and password of credentials.

To delete and return to the original TERMSRV.DLL, simply delete the corrected version, as well as rename the backup back to the "Termsrv.dll". If the terminal services are included and operating, you need to do it in a safe mode,.

If the computer S. Windows XP. connected to the domain, to the local network, Windows There will be a value of Regkey "AllowMultiPletSessions" in "0" every time the computer will not be restarted. In order for a multiple or unlimited number of sessions of remote connection to the desktop, it is allowed in the AD domain environment, the data value for "ALLOWMULTSESSSESSIONS" that must be set to "1" with each system start. To change the value, just restart tS_Multiple_sessions.Bat. Each time you start the computer. Also put tS_Multiple_sessions.Bat. in C: Documents and Settings All Users Main Menu Programs Startup Folders so that it will automatically run to the first user with administrator rights. Another solution is to install an additional service or key definition in the registry branch HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Currentversion RunThrough which the batch file is automatically bootable, and this is useful if the computer will not register with anyone, but still requires an employee to allow unlimited connections to a remote desktop to work.

Another thing, if the user closes remote compounds Instead of completing a session when he or she tries to log in again, an error message appears with a TCP / IP event. To solve this problem, download and install Windows XP TCP / IP, restricting the connection and event ID 4226 patch, and install the connection at least 50.

This assembly is built on the original form of Microsoft Windows XP Professional SP3 Russian version, with all the updates! Multi-loading disc. FREE DOWNLOAD -

Hello. As you know everyone, on the client OS from Microsoft, only one user is allowed to work simultaneously. It is expressed in that if you connect to the remote desktop, and there is already an active user, then the warning is expressed that the active user will be disabled.

How to be if, for example, you want to connect remotely, and at the same time not to beat the current session, or simply organize several simultaneous connections for RDP.

How to do this on Windows 10 I'll show you today.

Here you can be confused, and do everything into manual - edit the registry, replace DLLs, etc., but the way I will tell much easier. There is a project for the name RDP Wrapper, which allows you to make a terminal server from Windows 10 literally for 2 clicks. By the way, on Windows 7 and on Windows 8, this method also works.

In general, download the archive, unpack it somewhere, and launch the command line on behalf of the administrator.

In it go to the folder where the archive archive was unpacked (who does not know - the CD command \\ before \\ file

And execute the command Install.Bat

Also included a utility to change some settings - rdpconf.exe.

Here you can pay attention to the possibility of easy-to-shift port on which our RDP server hangs, and a few more settings that you may be useful.

Now add an additional user for the test. Clicking Win + R (or right-click on the start - to perform) and type Lusrmgr.msc. We go to users.

We click on the new user, give him the name and password.

Everything can be connected now. By the way, you can connect from your own computer on the owl under another account, for this in the connection address you need to enter 127.0.0.2.

Windows 7 / Vista / XP Terminal Server (SP1 / SP2 / SP3) - Real decision. Terminal server To connect to a remote desktop Windows 7 / Vista / XP (SP1 / SP2 / SP3) At the same time multiple users.

Terminal server You can use to launch one application from remote computers or to your terminal Server on Windows 7 / XP / Vista /you can connect different old old computers such as 486 and Pentium 1, they will work as if operating system installed on them Windows Vista / 7 / XP with Office XP-2003-2007, 1Cand a bunch of different office programs.

Default Windows 7 / Vista / XP Does not support the work of several users at the same time. In order to allow multiple users to work simultaneously by RDP., it is necessary to replace the file C: \\ Windows \\ System32 \\ Termsrv.dll and make changes to the registry - to remove the limitation imposed on Windows XP / 7 / Vista.

Before making changes in Windows 7 / Vista / XPMake sure your actions do not contradict the legislation of your country and the license agreement, so you use the method or not to solve you.

How to make a terminal server from Windows XP / 7 / VISTA?

1. Create several users with administrator rights or regular user, be sure to set the password.

Make sure the option is enabled - quick switching between users (Control Panel -\u003e User Accounts -\u003e Changing User Log in)

2. Allow a remote connection - select "My computer" by right-clicking and open it "Properties". In the window that appears, go to the "Remote Sessions" tab. Item "Allow remote access to this computer" Confirm the checkmark. Select remote users (otherwise Remote Desktop. will work only for administrators) and click "OK"

3. Make sure the ability to connect to the remote desktop is running for one user.

Making a Windows terminal server XP / 7 / Vista

4. Download universal patch to create a terminal server:
- Windows XP SP2 SP3;
- Windows Vista SP1 SP2;
- Windows 7, 32bit (x86) / 64bit (x64).

5. Follow the file Universaltermsrvpatch - *. EXE which corresponds to the bit of your system and click Patch. To replace the file A C: \\ Windows \\ System32 \\ Termsrv.dll

6. Follow the * .reg file that matches your operating system to make changes to the registry.

7. Overload the operating system

8. Start -\u003e Run -\u003e GPedit.msc

For Windows 7.

Computer Configuration -\u003e Administrative Templates -\u003e Windows Components -\u003e Remote Desktop Services -\u003e Remote Desktop Session Node -\u003e Connections -\u003e

For Windows XP.

Computer Configuration -\u003e Administrative Templates -\u003e Windows Components -\u003e Terminal Server-\u003e Limit the number of connections

Installing "Enabled" and change the value of the number of allowed terminals.

9. Restart the computer

If you all fulfilled right, then terminal server Windows 7 / Vista / XP (SP1 / SP2 / SP3) Ready. Now you have to work remote desktop simultaneously for multiple users.

Advanced settings terminal server Windows XP.

1. As practice shows, the users of the terminal server are simply disabled, and the programs work further. You can set the time to disable the inactive session.

Start -\u003e Run -\u003e GPedit.msc
Computer Configuration -\u003e Administrative Templates -\u003e Windows Components -\u003e Terminal Server -\u003e Sessions -\u003e Set time limit for disabled sessions

Enable and specify the time

There are also other restrictions there, you can choose how you like

2. Run a single program for all remote users of the terminal server, without a desktop

Start -\u003e Run -\u003e GPedit.msc
Computer Configuration -\u003e Administrative Templates -\u003e Windows Components -\u003e Terminal Server -\u003e Run the Program when connected

Enable
\\ Bkc.remoteclient.exe.

Specify the working folder
C: \\ Program Files \\ BCOMZV "Ulocity \\ Vіddaki Klієnt Site Aweden

3. Run a single program for selected terminal server users, without desktop (ATTENTION, it even acts if you go locally, so I don't even know how to cancel it later, except to delete the user, and then create a new or using the LiveCD boot disk, (ERD-Commander's program) with a choice of registry downloads the operating system we need .

Start -\u003e Run -\u003e Regedit

Create a string parameter Shell and in the "Value" field specify the full path to the program file

4. Starting one program independently by the user of the terminal server, without the desktop

To start executing c.2 for all users , overload and then return the value as it was (not specified)

In the Windows client settings (connection to the remote desktop) from which you connect, in the parameters in the program tab, put a tick "when you connect to run the following program"

Specify the full path to the program and file name

Specify the working folder
C: \\ Program Files \\ BCOMZV "Ulocity \\ Vіddaki Klієnt Site Aweden

5. Starting the program when entering the system on the desktop

Add a shortcut to the startup folder
C: \\ Documents and Settings \\ user_name \\ Main menu \\ Programs \\ Busload \\

There is a very convenient opportunity to make from the usual Windows 7 semblance of a terminal server with the ability to connect and work on one computer to several RDP users. It may be relevant in a small office to work in 1C via RDP. Several people will easily be able to work on an ordinary computer.
The fact is that the remote desktop in server versionsWindows, the default supports two simultaneous connections to troubleshoot and control the computer. Other users can connect simultaneously until you have the necessary client access licenses for this server and the machine can cope with it, i.e. It has enough resources.

In order to allow multiple users to work with one computer at the same time, you need to remove this limit. To do this, the DeepXW command has created a universal patch. The patch makes changes to the TERMSRV.DLL file, which is located in% Systemroot% \\ System32 \\.

Fashion first

Patch supports:

• Windows XP SP2 SP3;
• Vista SP1 SP2;
• Windows 7;
• Windows Server 2008 SP1 / SP2.

Download and unzip the archive, then run the appropriate file with the administrator rights (right-click on the executable file, select "Startup from the administrator"). For 32-bit systems, UNIVERSALTERMSRVPATCH-X86.exe is used, for 64-bit universaltermsrvpatch-x64.exe.

A window appears, as in the picture above, where you can patch the Termsrv.dll to remove the restriction of the remote desktop sessions, or restore the source file at any time (path to the backup file: \\ Windows \\ System32 \\ Termsrv.dll.Backup). After applying the patch, restart the computer and you can start work.

To check the removal of the restriction, leave the open session of one user on the computer where you applied the patch, and from the other machine, try to connect to the computer remotely from another user. If everything went successfully, both users will be active in the system, each at its session.

Original: "http://www.techspot.com/guides/485-windows-concurrent-sessions/"

To date, there are 2 more ways to make from Windows 7 SP1 terminal. The first with a patch to the TERMSRV.DLL library, the second without. It is preferable to use the second way, but if something does not work, you can use the first. Now in more detail about these methods.
Method of the second

You can do everything manually, who understands it, can make it based on the contents of the archive. The CMD file describes all actions that will be manufactured with the system. For those who do not want to understand this, there is an Install.cmd script. To install a patch, you need to run it on behalf of the administrator

That's all. You can check, connect. You need to create user accounts, do not forget to allow the connection to the remote desktop:

Method Third