Concurrent remote desktop
Taken from netfirms.com
You should only use this dll on WIN XP SP2. (not the 64 bit version).
Concurrent_Remote_sessions_SP2.zip
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. Extract the zip…
2. Double click on Install.bat.
3. Reboot.
Limitations:
Every user on the computer can have only one concurrent desktop at a time – you can’t login twice with the same user name.
You have to have fast user switching turned on.
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:
http://www.iopus.com/guides/winscheduler.htm
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 (127.0.0.1) 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. I noticed 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.
Procedure:
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….
Notes:
- It doesn’t work with the USIntl keyboard layout.
