Concurrent Remote Desktop Sessions in Windows XP SP2
vishnu, Tue, 2004-11-09 09:35
I mentioned before that Windows XP does not allow concurrent sessions for its Remote Desktop feature. What this means is that if a user is logged on at the local console, a remote user has to kick him off (and ironically, this can be done even without his permission) before starting work on the box. This is irritating and removes much of the productivity that Remote Desktop brings to Windows. Read on to learn how to remove that limitation in Windows XP SP2 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:
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! :-) Other links of interest:
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!
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 :-)
parent | reply
|
TopicsRecent blog posts
|
||||||