Login with RDP, without bumping current session.

[SquonkSC]

Warning! This is only for advanced users, and at your own risk.

Normally when you log in to a remote computer with RDP (Remote Desktop),
the current session on that computer is automatically logged of.

I found a site named "Missing Remote" and they made a script to prevent that, thus enabling concurrent sessions.

With their script it is not only possible to log on to a remote computer, without bumping the current user,
it's even possible to log in with the same account as the current user without bumping it.


When can this scenario be handy?

Well, suppose someone is watching a recorded show on your HTPC, and you want to log in?
Now you can, without the person watching the show even knowing you logged in.
You can even plan a new recording without interrupting the current user.

You can do maintenance on the machine while your wife is writing an email, or your kids are doing their homework.
They won't even know you're there.
-------------------------------------------------------

The guys at missing remote made such a good tutorial, I won't bother to write one here.

The only thing they forgot to mention, but is pretty obvious, is that you need to run the script on the remote machine you want to log in to.

Another thing I noticed is that with the RTM version you type "install multi"
and when you use the build 7100 version you have to type "install -multi"

I have only tried the RTM version and that worked with "install multi", so the " - " in the 7100 version might be a typo.
If you use the " - " and when login in still bumps the current session, just run the script again but this time without " - ".



This is the link for Win7 RTM 7600.16385 both x86 and x64
Missing Remote

This is the link for Build 7100 RC both x86 and x64
Missing Remote


All credits to this article go to the guys at "www.missingremote.com"

 

[johngalt]

Agreed. This makes things a lot easier to work with.

I have my network set up to allow incoming RD sessions to my desktop, so I can access files for classes if I ever need to (now I am really out of excuses)....but this would make it handy if I needed to get access to the machine while someone is on....

Great find!

Stickified

 

[Kari]

This really is super news. I just can not figure it out, the idea goes way over my head. Two simultaneous sessions, logged in with same credentials? Works, though. Tested with two W7-laptops.

Tip of the day!

Kari

 

[SquonkSC]

Thanks guys.

I'm quite pleased with it to.

My wife has dictatorial control over the HTPC, she's as much a TV addict as I am SF addict. lol

This makes life easier and marriage more stable.

 

[Kari]

Please guys, correct me if you think this is wrong: If I configure my firewall so that RDP can use alternative ports, could I have two RDP sessions simultaneously from two different computers?

Please don't call me an idiot when answering, that name is reserved to be used exclusively only by my ex-wives.

Kari

 

[zigzag3143]

Warning! This is only for advanced users, and at your own risk.

Normally when you log in to a remote computer with RDP (Remote Desktop),
the current session on that computer is automatically logged of.

I found a site named "Missing Remote" and they made a script to prevent that, thus enabling concurrent sessions.

With their script it is not only possible to log on to a remote computer, without bumping the current user,
it's even possible to log in with the same account as the current user without bumping it.


When can this scenario be handy?

Well, suppose someone is watching a recorded show on your HTPC, and you want to log in?
Now you can, without the person watching the show even knowing you logged in.
You can even plan a new recording without interrupting the current user.

You can do maintenance on the machine while your wife is writing an email, or your kids are doing their homework.
They won't even know you're there.
-------------------------------------------------------

The guys at missing remote made such a good tutorial, I won't bother to write one here.

The only thing they forgot to mention, but is pretty obvious, is that you need to run the script on the remote machine you want to log in to.

Another thing I noticed is that with the RTM version you type "install multi"
and when you use the build 7100 version you have to type "install -multi"

I have only tried the RTM version and that worked with "install multi", so the " - " in the 7100 version might be a typo.
If you use the " - " and when login in still bumps the current session, just run the script again but this time without " - ".



This is the link for Win7 RTM 7600.16385 both x86 and x64
Missing Remote

This is the link for Build 7100 RC both x86 and x64
Missing Remote


All credits to this article go to the guys at "www.missingremote.com"

Really nice. Glad I happened to find it. You might want to think abt making a tutorial abt it

Ken

 

[rsvr85]

I do a lot of remote connecting to an XP lappy on my network.
I'm assuming this won't work for XP?
Does anyone know how to do this for XP?

 

[zigzag3143]

I do a lot of remote connecting to an XP lappy on my network.
I'm assuming this won't work for XP?
Does anyone know how to do this for XP?

If you dont mind using a third party app team viewer works fine. You could also do it in VM, and probably in win 7.

Ken

 

[rsvr85]

So if i use Team Viewer it won't logout anyone currently logged into XP? (I'll be connecting from 7)
I'm already using 7 to do the job but it's annoying for the missus it keep logging her out when i need to do something quickly on it.

 

[SquonkSC]

I do a lot of remote connecting to an XP lappy on my network.
I'm assuming this won't work for XP?
Does anyone know how to do this for XP?

If I were you I would post this question at the site of the makers. (see my initial post)

Greetz

 

[SquonkSC]

So if i use Team Viewer it won't logout anyone currently logged into XP? (I'll be connecting from 7)
I'm already using 7 to do the job but it's annoying for the missus it keep logging her out when i need to do something quickly on it.

Teamviewer is not really a alternative for this method, because it will be visible to the one on the remote computer.

Greetz

 

[rsvr85]

If you dont mind using a third party app team viewer works fine. You could also do it in VM, and probably in win 7.

Ken

I'll give Team Viewer a go in a VM to see if it meets my needs, thanks for the suggestion.

If I were you I would post this question at the site of the makers. (see my initial post)

I'll post my question in the forums on missing remote, see how i got on there.
It'd be really handy if i can get it to work with XP. Thanks for the heads up on this one squonksc

 

[SquonkSC]

I'll give Team Viewer a go in a VM to see if it meets my needs, thanks for the suggestion.



I'll post my question in the forums on missing remote, see how i got on there.
It'd be really handy if i can get it to work with XP. Thanks for the heads up on this one squonksc

You're welcome.

Good luck

 

[Kari]

Squonksc & Ken,or anybody, any ideas of how to configure ports; I want to test this stupid idea of mine to make remote sessions from two different machines simultaneously to one Win7 system.

Kari

 

[SquonkSC]

Squonksc & Ken,or anybody, any ideas of how to configure ports; I want to test this stupid idea of mine to make remote sessions from two different machines simultaneously to one Win7 system.

Kari

I think you only have to add the alternative port in the RDP rule of the firewalls.

But I will experiment with it tomorrow to give you a more educated answer.

greetz

 

[freesbee]

I do a lot of remote connecting to an XP lappy on my network.
I'm assuming this won't work for XP?
Does anyone know how to do this for XP?

Yes! I know how to, and I do it anytime. I'm not talking about VNC or similar stuff: I know really how to do the same that works perfectly on Win7 after following this guide.

There was a file termsrv.dll in WindowsXP RC3 that allowed this .
Then, when publishing final release of WindowsXP the file was modified and multiple/concurrent TS sessions were possible only on Terminal Server OS (MUCH more expensive ).

BUT :roflmao: :roflmao: :roflmao:

some wise guy kept the RC dll and searched for the 2 registry keys that were changed. So if you substitute the dll and change the registry keys back to the original, then you will have a TS on WinXP Pro (I tested up to SP3 x86).

Guess who was that guy!!! :devil2: :devil2:

NOW

it's not a problem for me to post the file (or write a tutorial), but I'm afraid that would violate MS Licencing policies because of the old release of file termsrv.dll

Please, administrator, tell me what I should do

 

[Etihtsarom]

Hello,
It looks like the tool does not work any more. Can some one confirm this on their system for me?

 

[SquonkSC]

Hello,
It looks like the tool does not work any more. Can some one confirm this on their system for me?

Nope, still works.

Have you downloaded the right one for your Win7 build?

There are different versions for different builds.

 

[freesbee]

Confirmed

Dear Ragzarok,

I have experienced a malfunctioning on another Win7 7600 x64 system. I cannot tell you the reason why I had two different behaviors on two systems that were apparently identical, but I could figure out what was happening.

The script was setting all the registry keys correctly, but it was not copying the dll files in the proper path. So just try to run the script with the options that you need, then stop the RDP service(s) and manually copy the files

32_termsrv.dll -> %WINDIR%\system32\termsrv.dll
64_termsrv.dll -> %WINDIR%\SysWOW64\termsrv.dll

Start the RDP service(s) and in my case everything was fine.

Now I'm going to verify the argument of following post, because it seems to me that when I tested I could logon multiple cuncurrent users (I'm not sure, it was couple of weeks ago).

Hope this have helped

 

[Etihtsarom]

Hello,
It looks like the tool does not work any more. Can some one confirm this on their system for me?

Nope, still works.

Have you downloaded the right one for your Win7 build?

There are different versions for different builds.

Well here is the situation:

If the server has 2 users A and B and if A is logged in, the client can only log on with B's credentials without interrupting A's session. This has worked fine since the RC, I just thought the hack was supposed to allow the client system to log on using A's credentials as well. This is, however, not the case. Just wanted to clarify what it is that the hack does.