Professional Documents
Culture Documents
A much touted feature in SP2 (Service Pack 2) since then removed was the ability to do just this, have a user logged
on locally while another connects to the terminal remotely. Microsoft however removed the feature in the final
build. The reason probably is that the EULA (End User License Agreement) allows only a single user to use a computer
at a time. This is (IMHO) a silly reason to curtail Remote Desktop's functionality, so we'll have a workaround.
Microsoft did try out the feature in earlier builds of Service Pack 2 and it is this that we're going to exploit here.
We're going to replace termserv.dll (The Terminal Server) with one from an earlier build (2055).
To get Concurrent Sessions in Remote Desktop working, follow the steps below exactly:
1. Download the termserv.zip file below and extract it somewhere. (You have to be registered to see
the file)
2. Reboot into Safe Mode. This is necessary to remove Windows File Protection.
3. Copy the termserv.dll in the zip to %windir%\System32 and %windir%\ServicePackFiles\i386. If the
second folder doesn't exist, don't copy it there. Delete termserv.dll from the dllcache folder: %windir
%\system32\dllcache
4. Merge the contents of Concurrent Sessions SP2.reg file into the registry.
5. Make sure Fast User Switching is turned on. Go Control Panel -> User Accounts -> Change the way
users log on or off and turn on Fast User Switching.
6. Open up the Group Policy Editor: Start Menu > Run > 'gpedit.msc'. Navigate to Computer
Configuration > Administrative Templates > Windows Components > Terminal Services. Enable 'Limit Number
of Connections' and set the number of connections to 3 (or more). This enables you to have more than one
person remotely logged on.
7. Now reboot back into normal Windows and try out whether Concurrent Sessions in Remote Desktop
works. It should!
If anything goes wrong, the termserv_sp2.dll is the original file you replaced. Just rename it to termserv.dll, reboot
into safe mode and copy it back.
The termserv.dl_ file is provided in the zip is for you slipstreamers out there. Just replace that file with the
corresponding file in the Windows installation disks.
I've added in extra information from the comments below... thanks for all who researched! :-)
Please note that I haven't tried out any of the links above. YMMV.
If anything doesn't work with my procedure above though, post a comment here and I'll try to help!
For me the terminal server service won't start, and when I try to start it manually I get:
Could not start the Terminal Services service on Local Computer. Error 193: 0xc1
Are you sure that this old DLL works with the most current update for SP2? Any ideas for a long-term solution to
account for Microsoft's updates?
Explain...
Submitted by vishnu on Sun, 2004-11-21 12:11.
What do you mean by "most current update"? I have autoupdate turned on and it works for me.
A long-term solution (perhaps) would be to install Win2003. It can support one console session and two remote desktop
sessions concurrently with the default licensing schemes. This after all, is just a hack.
Things to do
Submitted by vishnu on Wed, 2005-01-05 20:01.
Things to do:
2. Try following the steps exactly one more time. May help.
Since this is a hack... I don't know exactly how to debug, just that these steps worked for me.
Maybe...
Submitted by agga on Mon, 2005-01-10 02:19.
Maybe you should add a note, that you can only start downloads while logged in as a registered user... i searched a while ;-)
» login or register to post comments
Done :-D
Submitted by vishnu on Mon, 2005-01-10 20:05.
Done :-D
I thought
Submitted by vishnu on Wed, 2005-01-19 20:17.
I thought that was what I was explaining here :-D
Dosent work on Windows Media Center for me FIXED! see next msg..
Submitted by JohnWPB on Thu, 2005-01-20 15:35.
I have Windows Media Center installed on my PC I am Remoting into. I have 2 Airpanels in the house to control the lights,
jukebox ect, with the software on that machine. I followed your instructions letter for letter, and also experience the same
thing that circuitfive has, it still boots the first person out when a 2nd connects.
I was under the impression that WMCE was simply XP Pro with SP2 built in, along with the media center software. Shouldnt
this work on a WMCE machine?
My Mistake!!!!
Submitted by JohnWPB on Thu, 2005-01-20 16:55.
I got it to work fine and I THANK YOU for such a great Hack!!!! Hopefully my stupid mistake will help others: I was using the
SAME account to log into RD as I was using on the machine at the time! You MUST create another account and log into the
server with different user names for this to work. I can't beleive I did this, but it dosent supprise me doing this at 6:30 in the
morning actually :)
On another note, I had my Airpanel, as well as this computer BOTH logged into the server and both connections were working
flawlessly. So it is capable of having two remote machines connected to the server, or having one remote machine, and one
local log on at the same time. You can have no more than 2 consecutive logons at one time to the server machine though.
After doing the hack as instructed here, I found the same thing.. I could have 2 RDC's, or one RDC and one local in use.
So, you may want to add the information from the link above here. Specificaly:
d. Open up the Group Policy Editor: Start Menu > Run > 'gpedit.msc' Navigate dow in the tree to: Computer Configuration >
Administrative Templates > Windows Components > Termina Services. Double-click the item in the list on the right entitled
'Limit number of connections'. Enable it, and set the number of connections to 3 (or whatever you need). Click 'OK'.
Thanks
Submitted by vishnu on Thu, 2005-03-03 19:50.
Thanks! This is interesting, and it works :-)
I tried to increase the number of connections to 10, but only 3 connections at the same time are possible. But i need 6
connections ...
Frustrated with XP
Submitted by bradw41 on Tue, 2005-05-24 01:53.
I have been unable to get 2 concurrent sessions to work on Windows XP SP2. I have followed the directions exactly. It works
when the computer is in a workgroup. But when I add it to a domain, it no longer works. Any ideas.
Yes JohnWPB!
Submitted by trulypaladin on Sat, 2005-01-22 01:03.
I was going to post that message that you can't remotely logged onto the computer with the same account. You have to
create a different account for the concurrent session to work. One other thing though, Windows 2002/2003 Server do allow
users with the same account to remotely connected onto the same server at the same time. Why can't XP do the same?
Sheesh.
Login
Submitted by pkonderla on Tue, 2005-02-01 01:13.
Login under Mozilla(Firefox) is unsuccessful - maybe I may set different security.
It works for me
Submitted by vishnu on Tue, 2005-02-01 18:13.
I'm using Firefox.
1. The registry file provided in the zipfile makes a new entry at:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core
Instead of the ControlSet001, use CurrentControlSet
2. Make sure that you don't have a copy of termsrv.dll in your dll cache directory (ie. C:\windows\system32\dllcache) and if
you do, just delete it.
Hmm
Submitted by vishnu on Mon, 2005-02-14 23:57.
I don't think this can be done :-(
Think so
Submitted by vishnu on Tue, 2005-02-15 00:00.
Yes, audio can be mapped over. See the Remote Desktop Connection properties.
No
Submitted by vishnu on Mon, 2005-02-14 23:59.
This isn't possible with the current hack.
Yes
Submitted by xlynx on Mon, 2005-05-02 10:18.
I have confirmed you can get 1 more session, making a total of 3 remote sessions or 2 remote and one console. Run
gpedit.msc and navigate to Computer Configuration -> Administrative Templates -> Windows Components -> Terminal
Services. Change "Limit the number of connections" to Enabled and set the value to 3 or more.
Yup possible
Submitted by vishnu on Tue, 2005-05-03 02:32.
That was an outdated reply, the above article has already been changed to reflect this information.
Same here. Tried everything, not allowing multiple users. I am running MCE 2005 SP2. Not sure if that makes a difference.
I haven't tested this hack with MCE, since I don't have a copy of the OS to test it on. To my knowledge, only one person has
reported success installing the hack on MCE.
Firefox isn't related to this at all... that guy was talking about login issues with this website (I blv) I do not know why this is
not working for you, it's working for many people... try following the steps above EXACTLY once more with a CLEAN install.
On one system, I had to reboot twice for this to take effect :-/
» login or register to post comments
Thread of other users who figured out the RDP concurrent logon:
http://www.msfn.org/board/index.php?showtopic=23619
http://www.sala.pri.ee/#termiserv
Prerequisites:
Make sure Fast User Switching is enabled and machine is not apart of a domain
Steps:
4. Delete %windir%\system32\dllcache\termsrv.dll
"EnableConcurrentSessions"=dword:00000001
8. From remote machine do a Remote Desktop Connection to target system and login with credentials from 2nd user
Congratulations, it shouldn't prompt you with the "need to logoff other user" message anymore!
P.S. What HTML tags should I use to get hyperlinks to work when posting?
Use a?
Submitted by vishnu on Thu, 2005-03-03 19:53.
Shouldn't <a> work?
in a domain ?
Submitted by 4lexandra on Sat, 2005-03-12 02:57.
Do you know if there is a way to do this when in a domain?
Nope
Submitted by vishnu on Sat, 2005-03-12 12:35.
I haven't tested this, but from the reports I've received, no.
Remote Control
Submitted by lee on Sat, 2005-03-19 21:25.
Hey everyone this a great hack, and a great thread. I have got 2 remote users and the administrator account (for a total of 3
sessions) all running on the same PC using two wyse 1125se thin clients off of Windows Media Center 2005...very cool. My
wife unfortunately isn't nearly as computer savy and when she has a problem...I've got to get off the couch. I've noticed that
by going to System Security and selecting the Users tab I have the ability to send messages to other users, I can disconnect
them if I like and I also have the ability to control their sessions remotely, much in the same way that I do on a daily basis at
work on a 2003 server. I can do everything but remote control. I get the following error Session (ID 4) remote control failed.
I've tried changing the policy in group policy editor but it's still a no go, anyone have any ideas? This is also great if I'm at
work and she needs help with something, I can just rdp in and then take control of her session and fix it for her. thanks again
ghitch for this great thread aaron
» login or register to post comments
Fixed it.
Submitted by lee on Sat, 2005-03-19 21:44.
I had it right the first time with group Policy editor, I simply forgot to have the other user log off and then log back on, the
policy is instated on logon. Just open up group policy editor (gpedit.msc) and select \computer configuration\administrative
templates\windows components\terminal services\ and the value is "Sets rules for remote control of terminal services user
sessions, edit that value to whatever you want. I set it to control without permission, and the next time my wife gets on I'm
going to mess with her a little bit: ) ok ok i know it's a little mean but it sure will be funny....lol be sure to log off and log
back on after you change the policy!!!!
Thanks SO MUCH...
Submitted by mads0078 on Thu, 2005-03-24 08:39.
This is great work with no probs
Yes, it is possible! 1. Fo
Submitted by seaVgull on Wed, 2005-03-30 20:12.
Yes, it is possible! 1. Follow the steps described in this howto above. 2. Set the "Fast User Switching Compatibility" service to
start _automatically_. 3. Every time your system starts you have to set [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon] "AllowMultipleTSSessions"=dword:00000001 You can make it via domain polices or whatever you
like. Personally I use a task for nncron scheduler: #( TSS Time: START-TIME Action: START-APP: regedit.exe /s "C:\Program
Files\TSS.reg" )# where TSS.reg consists of the above registry key. 4. Enjoy! :v))) p.s. By the way, concurrent connections
from the _same_ user are also possible. Go to Start Menu > Run > 'gpedit.msc' > Computer Configuration > Administrative
Templates > Windows Components > Terminal Services > Restrict Terminal Services Users to a single remote session. Set it to
"Disable". Do not forget to read the explain of this parameter. Also I recommend to learn other policies in this template. You
may find lots of useful things :-)