Windows 7 Remote Desktop

Windows XP Remote Desktop

Originally from
This is placed here in case becomes unavailable.

The beta 2055 release of XP PRO SP2 let you run two or more sessions (one local console and one or more remote desktop) concurrently. But this functionality was removed in the Final release. This patch will enable two or more concurrent sessions in Windows XP PRO Service Pack 2 (SP2) or later if you have FAST USER SWITCHING enabled, and your windows is NOT in a domain.

Uninstaller is also included and can be found at windows Control Panel → Add or Remove Programs.

If you use above patch, close the Null Session Vulnerability or it will lead to possible exploitation of your computer. Better solution is to use the security policy to block both anonymous logon and anonymous network shares,39044847,39192649,00.htm. Using better solution to prohibit anonymous logon and share, adds following reg values. In short, Run secpol.msc > Local Policies > Security Options > Network Access: Do Not Allow Anonymous Enumeration Of SAM Accounts And Shares, select Enabled, and click OK. It will add following reg keys.

Windows Registry Editor Version 5.00


Alternatively, you can copy and paste above it in a file with reg extension and run it. It will add those reg keys for you automatically.

Internet Articles Re Concurrent RD

Another Option (Works Great)

This one originally from
This is placed here in case above becomes unavailable.

You should only use this dll on WIN XP SP2. (Not the 64-bit version).

One thing I am very annoyed about with SP2 is why they have added (in build 2055) and then taken away in the final Build (2180) Concurrent remote desktop and a physical user logged into the same machine….

So if you are now running the SP2 final, and would like too use this feature. Here is what you must do..

1. termsrv.dll - a cracked dll with no concurrent desktops limit.

2. Install.bat - an install script for the dll

3. enable Concurrent Remote sessions SP2.bat – a registry changing code.

4. uninstall.bat – if you want to cancel the changes – run this script.

1. Download this.

2. Extract the zip…

3. Double click on Install.bat.

4. Reboot.

That is all, you are set to go!

don’t worry – it is ok – it is a windows warning because you are replacing a system dll.

I can’t believe MS removed this feature from the final build of SP2

The termserv here is the same as the one that comes with the final version of SP2 but there is no limit to the number of concurrent remote desktops you can have.

  1. Every user on the computer can have only one concurrent desktop at a time – you can’t login twice with the same user name.
  2. You have to have fast user switching turned on.
  3. If you are using a domain on your computer (usually companies uses domains on local networks) – you need to run the “enable Concurrent Remote sessions SP2.bat” every time you restart the computer because some registry values that are needed change every boot. You can put the file in the path “C:\Documents and Settings\All Users\Start Menu\Programs\Startup” and then the first user that will log on will run the script. The script will change the registry only for a user with “administrator” privileges. So if you don’t want to give administrator privileges to all the users on the computer – you can use the “Windows Task Scheduler” and schedule a login task.

More info about the “Windows Task Scheduler” can be found here:

termsrv.dll is not the original file from SP2, it is a patched file and I don’t know how legal is it to use is – but I think it will be very hard to catch you – you don’t really install a software, only a dll, and you only “unlock” a hidden property of windows xp.

In order to check if you succeeded - connect to your own computer, do this like that:

The limitation of Windows's XP Remote Desktop client is that it refuses any connection from the

localhost ( to the localhost with the following error message: “The client could not

connect. You are already connected to the console of this computer. A new console session cannot

be established”. In order to be able to tunnel this through SSH, this limitation must be broken.

The first idea was to hack the client executable and remove the limitation but it's simpler than

that. It's possible that if you run the executable mstsc.exe from another operating system than XP,

the limitation does not exist. Drilling a bit into that, it is possible to run mstsc.exe on

Windows XP to the localhost by using application compatibility with older windows 9x.

1. Create a folder (For example c:\TSclient) on your XP box

2. Copy mstsc.exe and mstscax.dll from your XP's %systemroot%\system32 to this folder.

3. Right click mstsc.exe and go to the properties of it.

4. Select the Compatibility tab

5. Check “Run this program in compatibility mode for”

6. Select “Windows 98/ Windows Me”

7. Click on OK

8. Now connect execute “mstsc.exe”.

9. Connect to “localhost” computer name.

10. Login as a user different from your own – so you won’t be logged out….

- It doesn't work with the USIntl keyboard layout.

Other name for search engines:

Free terminal server

Use Windows XP as a terminal server

termsrv.dll patch

Unlimited termsrv.dll

Unlimited terminal server

Unlimited remote desktop users