OK, I ran this on my Vista Ultimate x64. It ran fine. However, I have an issue that I am pretty sure is fixable, but I'm not sure how:

('m going to avoid terminology that I might not understand - Right now, the scenario is that I use the machine locally at home, and my wife sometimes also logs on locally with her own username. I like to remote in from work and check emails etc. Previously, if I was remoted in, and my wife logged in locally on her username, it kicked me out. Alternately, if she was logged in locally first and I then remoted in, it would boot her out. Sometimes it would warn, sometimes not, but anyway - neither behavior was desired.

What it does now is better, but not perfect: I am logged in at home. I lock the machine since I nearly always have it doing something, and go to work. My wife logs in on her username locally and does whatever. Fine. When I remote in from work, she is not disturbed. Good. If I'm logged in remotely, and she logs in locally, I'm not disturbed. Also good. Definitely improved.

However, when I remote in, it doesn't connect me to my existing session. Rather, it creates a new session. This is undesirable - some of the apps I have running in my initial session don't support multiple instances (azureus, firefox) and while I can kill that session from task manager, that's not a good solution for others (multi hour video encoding, 3d rendering).

The ideal behavior would be that I'm only allowed one session, which is how it worked previous to this patch. How can I make this happen - I'm pretty sure with the group policy editor, but I'm not sure what the correct number of sessions would be for this. Thank you for any advice you might offer!

If you originally logged in remotely it should reconnect. If you originally logged in locally, that is a console session not a remote desktop session. Those are 2 different animals and it will not "reconnect" remotely because terminal services is not involved in a console (local) session.

---

Go Griz!!!

on the issue of console vs. non console sessions.

If one is using this dll/reg hack, can one attach to the console session?

I'm used to using rdesktop from linux to attach to my displays and with Server 2003, I was able to attach to the console or alternate session with ease (-0 option for console).

However, with this dll/reg hack, it doesn't work.

any ideas?

I'm on Vista 64 Ultimate.

Actually when you connect to a Windows 2003 Server console you don't join the session in progress, you terminate the existing console session and start a new one. If someone is logged on locally to Windows 2003 Server they will be kicked off when you connect using a console session remotely. You want to connect to an existing console session remotely and "take over" that session. As I mentioned before a console session and a remote session are two different critters. I don't know of any way to do what you want, but I will watch this thread to see if anyone can solve your problem.

---

Go Griz!!!

Actually, I was able to get the desired behavior on Ultimate x64 ( see like 3 or 4 posts up - when I remote into home from work, i get the same session as i was on at home, and my wife can be on without being disturbed) using group policy editor.

1.) run gpedit.msc
2.) Go to local computer policy, computer configuration, Administrative Templates, Windows Components, Terminal Services, Terminal Server, Connections
3.) Change "Restrict Terminal Services users to a single remote session" to "enabled"

Works for me, your mileage may vary.

Let me explain what I want.

I know that when I remote into the console session, the console on the machine itself will be locked.

That's fine. I usually do that remotely.

I also want to be able to login (as myself) into a non console session (for instance, I've remoted into console, started a video player by accident and wasn't able to kill it, so I remoted it again into a non console session, brought up task manager and killed it).

So why the restrict to single session could work, it wouldn't be full solution.

temporary ugly solution is to create a secondary user that I can log in also from to a different session.

I hope this thread isn't dead.  I just updated to SP1 and went to repatch to get RDP working again, and things haven't gone so well...

1. First, I didn't realize I needed the SP1 updated dll, so I first applied the old batch file script.  The result?  No RDP, and my new linksys extender stopped working as well.
2. I found the SP1 version, and tried to run that BAT file (premium.bat as administrator), but it failed several times -- the terminal services service would not stop on its own. 
3. I disabled the service, rebooted, and ran the SP1 BAT file.  It seemed to be successful, but of course it could not start up the service or find the part 3389 listening.
4. I re-enabled the service, and it's listening at 3389, but still nothing is working (RDP or extender)
5. I've since re-run the SP1 BAT file, and it works 100% (no errors, all expected responses -- stops and starts the service as expected, and displays the two responses for 3389 listening). 

Still, neither RDP nor my extender are working.   In fact, RDP gives me an immediate 'error' now when it used to take its time to come back with an error.   Remote Desktop Connection app finds "no terminal services" found when I do a browse.

I've cross-posted this as a new post as well in the forum, but I wanted to see if any subscribers to this thread could help someone who's in trouble (?)!

Thank you in advance,
Jon

Please, anyone?   I'm really concerned about my situation.  I have no extender service, and no remote control ability. 

JonDeutsch:

I hope this thread isn't dead.  I just updated to SP1 and went to repatch to get RDP working again, and things haven't gone so well...

1. First, I didn't realize I needed the SP1 updated dll, so I first applied the old batch file script.  The result?  No RDP, and my new linksys extender stopped working as well.
2. I found the SP1 version, and tried to run that BAT file (premium.bat as administrator), but it failed several times -- the terminal services service would not stop on its own. 
3. I disabled the service, rebooted, and ran the SP1 BAT file.  It seemed to be successful, but of course it could not start up the service or find the part 3389 listening.
4. I re-enabled the service, and it's listening at 3389, but still nothing is working (RDP or extender)
5. I've since re-run the SP1 BAT file, and it works 100% (no errors, all expected responses -- stops and starts the service as expected, and displays the two responses for 3389 listening). 

Still, neither RDP nor my extender are working.   In fact, RDP gives me an immediate 'error' now when it used to take its time to come back with an error.   Remote Desktop Connection app finds "no terminal services" found when I do a browse.

I've cross-posted this as a new post as well in the forum, but I wanted to see if any subscribers to this thread could help someone who's in trouble (?)!

Thank you in advance,
Jon

Jon

I am sorry I have been busy.  I do not have any imidiate solution for you.  I am going to try recreating your problem using a virtual machine.

Install Vista
Run the V1 patch
Install SP1
Run the V1 patch
Run the V2 patch

I will let you know how it goes.

 

Thank you scuffs.

On the advice in another thread, I took explicit ownership of the v2 patched dll for the group administrators.   I also gave the terminal server user full control of termsrv.dl as well just in case.

The only noticeable difference I see now is that when I try to remote desktop, my client and server both "think about it" for a good 20 seconds before erroring out.  Prior to this, it was instantaneous, and the error said that there were no remote desktop servers on the lan. 

The continued really bad news is that the extender still will not connect -- which is now my #1 priority.   Are there any logs I can dig up that would help you/someone  identify what the problem is with the extender connectivity?

Any info greatly appreciated!
Thanks,
Jon

scuffs:

Jon

I am sorry I have been busy.  I do not have any imidiate solution for you.  I am going to try recreating your problem using a virtual machine.

Install Vista
Run the V1 patch
Install SP1
Run the V1 patch
Run the V2 patch

I will let you know how it goes.

Hi Scuffs,

Any luck getting time to try this out?   And, everyone, if nothing works (which doesn't make sense since it works for others), should I simply go back to my restore point prior to upgrading to SP1?

Thanks,
Jon

Can someone do me a big favor and PM me [or email me:  jrdeutsch (at) yahoo.com] the original termsrv.dll and rdpclip.exe files from the Vista SP1 installation?

Because of the order of the things I did, I have lost the original files, so I am unable to revert back to where I started prior to applying the patch.  It seems like the only thing I can do at this point is to revert back to the original SP1 files so I can get my extender working again.

In addition, are the reg file updates something I need to roll back as well manually?  Is there an "undo" script available?  That reg import looks huge... looks like a lot to manually undo.

But at this point, I would do anything to avoid a re-install of my Vista system that has been otherwise running reliably for 20 months straight.

Can anyone lend a hand? 

Thanks,
Jon

I still have no extender ability.  I tried to back to a restore point, but Vista removed my restore points prior to my SP1 upgrade and RDC hack.  So, I did the next best thing:

I uninstalled and re-installed SP1.

Didn't work.  Still no extender functionality.  Is there anyone here who knows what registry settings could/would be creating this problem?  It's directly related to the premium.bat batch file, but I do not know where to start to diagnose.

This is the error I'm getting in the event viewer:

"The RDP protocol component "DATA ENCRYPTION" dectected an error in the protocol stream and has disconnected the client."

Any insights?
Thanks,
Jon

The original information from the first post.

On Sept 1st Raevmiza let us know that the hack did not work on the Beta.  For kicks I played around with it today and now I am posting my results.

Instead of telling you what doesnt work and why I will just tell you what I have done.  This is the new sp1 beta dll hex edited to incorperate the fix.  I used it and ran the following commands.

I disabled terminal services.  Stopping them did not work, I had to disable the service to get it to stop.

I right clicked on c:\windows\system32\cmd.exe and ran as administrator
 takeown /f C:\Windows\System32\termsrv.dll
 icacls C:\Windows\System32\termsrv.dll  /G administrators:F

I renamed the current dll to termsrv.dll to termsrv.old
I renamed the new dll copied it in then renamed it again to termsrv.dll (copying it in without renaming it caused the dll to revert instantly.)
I then restarted the service after turning it back to automatic.

I could not log in remotely without the user getting logged off, so I rebooted.  After reboot the DLL was missing and terminal services worked but only with 1 log in at a time.

I will add more when I know whats happening.  The only thing I am adding is the edited dll from SP1 install, and a little knowledge about what doesnt work.

Does anyone have any ideas?