Hello TS, is there a patched DLL for this (Vista SP1 x64) yet that you know of?

 

Thanks

gggggggg

check out this topic which focuses on the SP1 and both dll files are in there i think. http://thegreenbutton.com/forums/thread/242509.aspx

I'm hoping my post wont be ignored...

But, I'm would like to know if it's possible to auto-execute an application after you unlock the desktop of the console PC (after you type in your username & password).

This is when a PC's console has been automaticaly locked after exiting an RDP session.

If so.. how can I do this?  I'm guessing I need to put this in the registry somewhere for the app to start automatically.

hmm - Why is your screen locking? If you correctly setup concurrent RDP sessions the screen will not lock while you are connected (you can be watching tv and connected via remote desktop).

 

Remember you have to use 2 different accounts (one for console - watching tv, and one for remote administration).

I have a TV user setup that automatically logs in and launches MCE on startup (very much like an appliance). I use the local administrator account to connect and make any administrative changes (install apps, defrag etc).

 

 

I only use one profile... way too many application configuration settings associated with that profile.  Plus, there are some apps I need access to that are already running on the desktop.

whatuusay1:

hmm - Why is your screen locking? If you correctly setup concurrent RDP sessions the screen will not lock while you are connected (you can be watching tv and connected via remote desktop).

 

Remember you have to use 2 different accounts (one for console - watching tv, and one for remote administration).

I have a TV user setup that automatically logs in and launches MCE on startup (very much like an appliance). I use the local administrator account to connect and make any administrative changes (install apps, defrag etc).

 

 

Hmm - this might not have been the best thread to try to find a solution. This thread was for concurrent RDP sessions.

 

Thanks!

This is a great thread!  Does anyone out there know if there is a similar hack to enable concurrent sessions on XP Pro 64-bit as well?

To my knowledge no it was never done.  If you send me the dll I will take a look, I might be able to figure it out.

Hey Guys,

  Someone care to explain a little further for Noobs like me.

If I have 1 computer running a media center (Shouldn't need to be Vista Media Center I don't beleive) and I don't want to have a keyboard/mouse attached I should be able to remote via laptop under a different user name and start D.L's, Change Dir, Clean up messes all while having the media center still loaded (and being used) on the TV?

  So essentially the computer hooked to the TV is never really being touched at all.  It can sit and look pretty so long as it is on.

  Again once a file has been D.L I should be able to put it into a directory that the media center monitors and vola it will be updated on my media center (TV)?

  Now that would kill the need to have 2 computers (woot !!!) 1 - media center 1- d.l , storing, etc.

-Nw-

Anyone notice that all of the available hacked termsrv.dll files for concurrent sessions do not work after some very recent windows updates.  I tried on XP x64 and Vista x64 and for both the TermService service would not start saying "Error 5: Access is denied"  Anyone got a new hacked version?

just to confirm your tip worked for me, I took the rdpclip.exe froma a Vista Business SP1 installation.

thank you!

yeah guys, i think there is a NEW ISSUE with some of the windows updates.

I had the non-sp1 Vista hack working perfectly for about 6 months

I installed some recent updates (BUT NOT SP1) and now it seems to not work any more....this happened this past weekend i guess but i didn't notice it until today.

when i try to run the process again, it seems the RDP client that would listen on 3389 just won't start

I tried manually starting the 2 terminal services services and still, netstat -a does not show it (yes i have it on port 3389 in registry)

surely there is something new going on here with relationship to vista updates and it's just beginning to be seen... however, i am not sure a new dll is going to do much since the issue appears to be that the service won't start?

anyone got more info?

Don't mean to just "bump" this thread, but I need people to report back on this one too. I'm holding off installing my latest Vista updates, 890380, 938464 and 954154, until I get more info. This could be an unfortunate seriousness if it is true.

@ionizer: did you try and re-install the patch again?

tskx.

Yes.  I tried reinstalling the patch, the problem is, the patch wont work because the terminal service is not listening on port 3389 now.

No matter what I do, reboot 15x, manually start the service, manually copy over the termserv.dll, it won't listen anymore.  Could it just be some issue I am experiencing?  I suppose...but it was working fine for 6 months and then suddenly this weekend it stopped.

I went ahead and updated to Vista SP1 and tried the SP1 patch, still, same results.

I also (before installing SP1) went ahead and did a system restore before the time it was last working, which was Friday (b/c I RDP home from work) and it still wasn't working, so it's possible it was a patch before then that DIDNT REQUIRE A REBOOT but which upon reboot (this weekend) did cause something.  Maybe I didn't go back far enough, i dont know, or maybe there is just some specific issue I am experiencing.

I ran sfc /scannow to replace corrupt files, but it was late last night and I have yet to try to run the patch again after that and re-apply.

BTW, here is the log of what happens:  The copying of the file is irrelevant because I manually copied it over beforehand:

 

Source Folder is D:\testing4\
Taking ownership of C:\Windows\System32\termsrv.dll

SUCCESS: The file (or folder): "C:\Windows\System32\termsrv.dll" now owned by th
e administrators group.
Granting Administrators rights
processed file: C:\Windows\System32\termsrv.dll
Successfully processed 1 files; Failed processing 0 files
Stopping Terminal Services
The Terminal Services service is stopping.
The Terminal Services service could not be stopped.

        1 file(s) copied.
Copying D:\testing4\termsrv.dll to C:\Windows\System32\
The process cannot access the file because it is being used by another process.
        0 file(s) copied.
Importing Registry Keys
Enabling RDP
The operation completed successfully.
Setting fSingleSessionPerUser to 1
The operation completed successfully.
Setting LimitBlankPasswordUser to 1
The operation completed successfully.
Configuring Remote Desktop in Windows Firewall

Starting Terminal Services
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

Pausing 5 seconds to give service time to start listening
Checking if Service is listening on port 3389
Service is not listening
Done
Press any key to continue . . .

I'd also like to add that I can manually stop the Terminal services and have the whole process seem to work fine, except it STILL doesn't listen:

 

Source Folder is D:\testing4\
Taking ownership of C:\Windows\System32\termsrv.dll

SUCCESS: The file (or folder): "C:\Windows\System32\termsrv.dll" now owned by th
e administrators group.
Granting Administrators rights
processed file: C:\Windows\System32\termsrv.dll
Successfully processed 1 files; Failed processing 0 files
Stopping Terminal Services
The Terminal Services service is not started.

More help is available by typing NET HELPMSG 3521.

        1 file(s) copied.
Copying D:\testing4\termsrv.dll to C:\Windows\System32\
        1 file(s) copied.
Importing Registry Keys
Enabling RDP
The operation completed successfully.
Setting fSingleSessionPerUser to 1
The operation completed successfully.
Setting LimitBlankPasswordUser to 1
The operation completed successfully.
Configuring Remote Desktop in Windows Firewall

Starting Terminal Services
The Terminal Services service is starting.
The Terminal Services service was started successfully.

Pausing 5 seconds to give service time to start listening
Checking if Service is listening on port 3389
Service is not listening
Done
Press any key to continue . . .