What should termsrv.dll do?

[fizzy]

What should termsrv.dll do?

My understanding is that I can be logged in locally and that someone can remote desktop and use the machine at the same time. Where as the stock termsrv.dll would only allw a single user to be working at one time. Is this correct?

[army20]

Yes it is correct, you can also have two (and more) remote connection at the same time. My favorite thing about it is that you can set a group policies that enable "do not require a permision to interact with user session" and spy what the console user (locally logged) do without him knowing.

[gamehead200]

Yes it is correct, you can also have two (and more) remote connection at the same time. My favorite thing about it is that you can set a group policies that enable "do not require a permision to interact with user session" and spy what the console user (locally logged) do without him knowing.

<{POST_SNAPBACK}>

But it requires hex editing the file!

[fizzy]

Yes it is correct, you can also have two (and more) remote connection at the same time. My favorite thing about it is that you can set a group policies that enable "do not require a permision to interact with user session" and spy what the console user (locally logged) do without him knowing.

<{POST_SNAPBACK}>

Is there any place you can point me to do this. This is EXACTLY what I am looking for. I am pretty policy/group policy illiterate...

We have 50 kiosks and are currently using UltraVNC to watch what the kiosk users are doing. We would like to be able to work on the kiosk in the background via remote desktop. If we could watch the active user with Remote desktop too than that is doubly great since IMO I find remote desktop to be light years better then UltraVNC/RemoteAdmin...

[fizzy]

Okay next question... Is there a way to do change the termsrv.dll in an already running configuration?

I ask because I took termsrv.dl_ and used expand.exe to expand to termsrv.dll. I then booted using winpe and copied termsrv.dll to \windows\system32 and \windows\system32\dllcache

I also made this registry change..

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core]

"EnableConcurrentSessions"=dword:00000001

I rebooted and when I remote desktop in, the local user is still kicked out?

Anyone have any suggestions?

[fizzy]

Okay I got the group policy snap in in the management console but I do not see "do not require permision to interact with user session" as an option anywhere. I am running windows XP

[army20]

Edited August 8, 2005 by army20

[army20]

Are you using The hacked termsrv.dll from here ?

Edited August 8, 2005 by army20

[fizzy]

Are you using The hacked termsrv.dll from here ?

<{POST_SNAPBACK}>

Short answer yes...

Longer answer none of the links in that post worked. So after reading through the posts I found a link to this

http://www.msfn.org/board/index.php?act=ST...=70#entry345572

So I d/l'ed from there and installed as previously noted..

[fizzy]

Thanks for the pic. I can see the setting now...

[fizzy]

FWIW I needed to install this on kiosks in the field where booting into safe mode was not an option here is how I did it (I was doing this via a Remote Administrator session over a dial-up connection)...

step 1 - use extract to extra termsrv.dl_ into termsrv.dll

step 2 - create the following batch file (call it "copies.bat" that is in the same directory as termsrv.dll

copy termsrv.dll %windir%\System32\termsrv.dll

copy termsrv.dll %windir%\ServicePackFiles\i386\termsrv.dll

%windir%\system32\dllcache\termsrv.dll

step 3- use unlocker to terminate the processes that are locking termsrvc.dll. What you do this you will get window saying a severe error has happened in windows and that windows will reboot in 60 seconds. So onto step 4 before your 60 seconds are up...

step 4 - run copies.bat.... The only reason we make the batch file is because you will be surprised how short 60 seconds is when you are fumbling around trying to make copies and delete files using windows explorer..

step 4a - let the machine reboot (or you can race to see how many remaining steps you can complete before your 60 seconds is up)

step 5 - import the Concurrent Sessions SP2.reg (documented else where)

step 6 - 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.

step 7 - Open up the Group Policy Editor: Start Menu > Run > 'gpedit.msc'. Navigate to Computer Configuration > Administrative Templa

tes > 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.

I had tried using tools like pendingmoves.exe to have termsrv.dll replaced on restart and several other things none of which worked. So I resort to unlocker...

Terminal Services on win2k3 allows me to switch between terminal services logins via terminal services manager. I have heard people mentioning tha tyou can do the same on xp. How do I? I have not found anything similar to a terminal services manager in XP.

thanks,

Fizzy