[gai-jin]

Concurrent sessions -- I understand the advantage of being able to log in from a remote terminal and also log in at the local term at the same time. Are there any other uses for this that I'm missing?

Gai-jin

[gai-jin]

Also, if one puts this cab in the source dir, is it also required that wfp be disabled, or will wfp not be a factor if this is in the source for the windows installation?

[Jazkal]

gai-jin, on Aug 8 2004, 09:25 PM, said:

Also, if one puts this cab in the source dir, is it also required that wfp be disabled, or will wfp not be a factor if this is in the source for the windows installation?

If you put it in the source (i386), make sure and add the reg file to your unattended. But yes, that's all that's needed.

[gai-jin]

Which reg file?

This key?

HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCSetting",0x00010001,0xffffff9d

?

[Jazkal]

Can anyone tell me where I can get the info I need?

What I'm looking to do:

I want to figure out how to patch the build 2180 version of the termsrv.dll to allow concurrent sessions, using the build 2055 version of the file as a reference.

What tools/methods do I need to learn/use to figure this out. Any help or suggestions are appreciated.

Thanks



EDIT:

Quote

Which reg file? 

This key?

HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCSetting",0x00010001,0xffffff9d

Yes, that one.

[bilemke]

@Jazkal

I wish I knew too.. Your going to need some very good skills with a debugger to try and find it, if it is possible at all.

That, or soemone else finds it first and shares the knowledge

Then we can just download a file or do some small hexediting hopefully.

[Jazkal]

bilemke, on Aug 11 2004, 02:13 PM, said:

Then we can just download a file or do some small hexediting hopefully.

That's what I'm shooting for, but someone has to do the work upfront, and I don't mind putting in the time. I just need someone to point me on the way.

[OCedHrt]

Try setting AllowMultipleTSSessions to 1 at the same place as EnableConcurrentSessions. Seems to be a new reg key in the 2180 dll that is not in the 2055 dll.

[Jazkal]

OCedHrt, on Aug 11 2004, 03:52 PM, said:

Try setting AllowMultipleTSSessions to 1 at the same place as EnableConcurrentSessions. Seems to be a new reg key in the 2180 dll that is not in the 2055 dll.

I'll give that a try once I get home. Thanks for the info.

UPDATE:
Just tested it on a friends workstation here, and it didn't work. We added both of the regkeys and rebooted.

[OCedHrt]

Darn :/ Well I'm pretty clueless as to what to do as well There are some timebomb stuff in the old build though so careful with using that one.

[Jazkal]

OCedHrt, on Aug 11 2004, 05:13 PM, said:

Darn :/ Well I'm pretty clueless as to what to do as well There are some timebomb stuff in the old build though so careful with using that one.

Anything specific?

[gamehead200]

Does anyone else have event 1006 in their system event logs as an error with the hacked file?

[prathapml]

Nopes! Not me.
Been on XPSP2 since 7 days, not hacked TCPIP.SYS, rebooted very few times, and run P2P apps a _lot_.
And I only see lots of 4226 and 1007 - no 1006 *ANYWHERE* in the event log (all sections searched).

[snakeey]

Hi everyboby, i am new to here, nice to meet all of u (i came from Hong Kong, please don't mind my bad english)

I followed the step in order to make my winxp which just upgraded to sp2 rtm build to have the concurrent sessions, i found that the step is not quite clear enough, here is what i have done (please notice that i am not clean installation from a unattened cd):

1. Extract the attached termsrv.dl_ (which posted by the administrator at the start of this thread) and overwrite to c:\windows\system32 (for my case, even i booted to safe mode, when overwrite this file, it said it is using by the system, so i boot by win98 boot disk to dos and overwrite it)
2. Click: Start - Run
And type: regedit
Go to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core
Right-mouse-click on the right pane and create a new DWORD: EnableConcurrentSessions
Double-click the value and type: 1
3. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Double-click DWORD: AllowMultipleTSSessions and change the value to 1

that's all
here, thank you everybody for this hack

Attached File(s)

•  termsrv.dl_ (98.08K)
  Number of downloads: 208

[Chrysalis]

yeah I have decided not to replace my file as I rarely use remote desktop to my machine, if there was a patched 2180 file I would replace but I think there is a risk using the old version.

[REDONDOS]

This doesn't work for me!

On XP Pro SP2 I used latest Replacer version to change termsrv.dll for the old, concurrent sessions-enabled, file. Then applied the registry changes and rebooted.

Enabled remote desktop and tried to log in with the same user that I was logged in with from mstsc, but this made the Welcome Screen appear. Then logged back on, remote desktop connection closed automagically, and tried to log on with some other account through remote desktop... same problem.

Does this really enable me to be logged in and actually using the computer from 2 different locations at the same time? Because it isn't working...

Thanks.

[gamehead200]

REDONDOS, on Aug 15 2004, 05:40 PM, said:

This doesn't work for me!

On XP Pro SP2 I used latest Replacer version to change termsrv.dll for the old, concurrent sessions-enabled, file. Then applied the registry changes and rebooted.

Enabled remote desktop and tried to log in with the same user that I was logged in with from mstsc, but this made the Welcome Screen appear. Then logged back on, remote desktop connection closed automagically, and tried to log on with some other account through remote desktop... same problem.

Does this really enable me to be logged in and actually using the computer from 2 different locations at the same time? Because it isn't working...

Thanks.

Let's say I login with user A locally... I cannot login with user A remotely, or else I will be kicked off locally. You must login with user B remotely so that user A does not get kicked off. That is how it works!

[REDONDOS]

REDONDOS, on Aug 15 2004, 03:40 PM, said:

...Then logged back on, remote desktop connection closed automagically, and tried to log on with some other account through remote desktop... same problem...

Already tried that.

Also, I tried a couple of the new uxtheme.dll files around the forums, but none of them seemed to work, can you please point me to the right post?

Thanks.

[nolookingca]

snakeey, on Aug 12 2004, 12:45 PM, said:

[snip] here is what i have done (please notice that i am not clean installation from a unattened cd):

1. Extract the attached termsrv.dl_ (which posted by the administrator at the start of this thread) and overwrite to c:\windows\system32 (for my case, even i booted to safe mode, when overwrite this file, it said it is using by the system, so i boot by win98 boot disk to dos and overwrite it)
2. Click: Start - Run
And type: regedit
Go to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core
Right-mouse-click on the right pane and create a new DWORD: EnableConcurrentSessions
Double-click the value and type: 1
3. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Double-click DWORD: AllowMultipleTSSessions and change the value to 1

[snip]

you need to do a search in your windows folder. There may be more copies of the file.

@Redondos: I've used the file included here for a while without problems: http://www.msfn.org/...showtopic=23719

[jcarle]

Anyone figure it out yet?