How to Enable Concurrent Sessions in Windows 7 Service Pack 1 RTM

Feb 25 2011

Please Read

The script has been updated. The following now works properly:

  1. multi cmd line switch
  2. Home Premium
  3. Non-English Operating Systems, no need to change the script

Sorry for any inconvenience caused.

If you've been following MissingRemote for a while, you know one of our most popular series of guides is Enabling Concurrent Remote Desktop sessions. Continuing that trend we have an updated process below working with the RTM (Official Release to Manufacturing) version of Windows7 Ultimate, Professional, Home Premium and Enterprise Editions, x86 & x64 build 7601, Service Pack Build 1130.

One of the most popular articles ever at MissingRemote.com has been our guide on how to enable Concurrent Sessions for Windows Vista. For those unaware of what it is, enabling Concurrent Sessions allows you to Remote Desktop into a system that someone else is on, under a different user account, and access the system without kicking the user off. I, for example, use the feature to have MCE running on my Television, and then I remote into my main user account to access all my files without interrupting my MCE session. Special thanks to Mikinho for compiling the package below and making this all possible.

userscreensmall.jpg

***DISCLAIMER***

The following files and instructions are provided to you at your OWN RISK!! Understand that it is replacing important files, and as always, anything can happen. That being said, if you do have a problem, we have a fantastic community here to help you
rdp1

INSTALLATION INSTRUCTIONS (READ CAREFULLY)

1. First, Download the file attached below (you will need to be registered and logged in.

2. Once downloaded, extract the files into a directory (for the purposes of this guide, it will be assumed that the files have been extracted to the folder C:\Win7RDP )

3. Open Windows Explorer to the above folder

4. Right Click on "install.cmd" and select "Run as Administrator"

5. Wait for the script to run entirely. At the end, you should see something similar to the below...

rdp.png
 If you executed the command successfully, you should see this screen.

EXTRA ABILITIES

For 99.9% of folks, the above steps will be exactly what they are looking for. However, if you want to customize the abilities a bit, there are certain command strings you can run in addition. To do so,you will need to open a Command Prompt with Administrator Privileges(Start > Run > CMD > Right Click "Run As Administrator"). The other available options are: 

-? Show this help
help Save as -?
multi Enable multiple sessions per user
blank Enable remote log on for user accounts that are not password protected

For example, if you wanted to Enable multiple sessions per user, you would follow these steps:

1. Launch a Command Prompt with Administrator priveleges (Start > CMD > Right Click > Run as Administrator)

2. At the C:\Windows\System32 prompt type "cd\Win7RDP"

3. You should now be at the prompt C:\Win7RDP>

4. At the prompt, type: install multi

We hope you have enjoyed this guide from MissingRemote.com! If you have any questions, comments, concerns feel free to post in our forums link below.

Related Articles

Comments

very so much ,i need it ^^

Thank you so much for this patch!  Concurrent multi-user Windows is awesome.

However, the reason I got into this stuff in the first place is that I want to be able to change my music from another room.  I can do this with VNC, but as other users have noted, RDP does scaling better.  And maybe someday I can get Aero working over RDP since I have a very fast 5 GHz WIFI network.

Anyway, I created a second User called "Background" so I can log into that account without disturbing the primary one.  But if I log into Background and then do the whole "shadow console" command as administrator to gain control of the primary User, it works for a few seconds and BSoDs; i.e. kernel panic and reboot.

What can I do?  I want screen sharing like in Remote Assistance without the authentication and from any RDP client.  Is that so much to ask?

Or, what about a script to automatically log back into the account after the remote one disconnects?  (Not ideal, but better than nothing.)

Well, I thought for a while that the -console flag on the many RDP clients would help my situation.  Apparently not.  It seems that the console is the default option on non-server Windows OSes.

Is that the case?  Should I try to simultaneously enable multiple sessions per user and use the console trick?  Is shadowing possible in anyway with RDP like it is with VNC?  This is crazy!

There is no /console flag anymore.  It was removed in XP SP3/Vista SP1/W2K8 and replaced with the /admin flag which still won't do what you want.

btw, The console flag was removed since its initial purpose, connecting to session0, is no longer needed.  In Vista/Windows Server 2008 or higher session 0 is a noninteractive session that is reserved for services.

What you want to do is shadow the console session:

1- Set the below registry key.  It isn't needed but if you don't then the console session will need to approve your shadow request which isn't very easy to do on a dedicated HTPC

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]

"Shadow"=dword:00000002

2- RDP into the machine with either a different account (or if you use multi switch the same username will work, I just don't recommend it).

3- Shadow the console session via the below command (required administrative rights) or via Task Manager - Users tab

shadow console

Works perfect!!! Thanks a lot......

This is not working with the real service pak 1. it is telling me it is for version 7601, yet i checked the registry and it says 7601. what is the deal? am i retarted?

It would appear others are experiencing this error:

"Your operating system is not supported.

Only for Windows 7 Build 7601"

 

Any word on a fix yet?

paradoxgrowth wrote:

 

It would appear others are experiencing this error:

"Your operating system is not supported.

Only for Windows 7 Build 7601"

 

Any word on a fix yet?

 

I'm having the same issue.

Running Win7 x64 sp1 here. Used concurrent rdp patch before without any problems but after running this v2 patch i'm getting the same error.

Winver shows: version 6.1 (build 7601: Service Pack 1)

Rdpclip.exe is version 6.1.7601.17514

I didn't noticed any strange errors when installing SP1.

Any help would be appriciated.

 

:update:

I noticed a different value in registry compared with batch file:

My productname is: Windows 7 Ultimate N

batch file stats that it needs to be Windows 7, could this be the problem?

:fixed:

I added under versioncheck the following entry:

IF /I NOT "%EDITIONID%" == "UltimateN" 

just before IF /I NOT "%EDITIONID%" == "Ultimate" 

Patch applied succesfull

I second this - this change also worked for me. Please consider adding "UltimateN" to the list of supported versions.

excellent work - thanks much!

worked great

win7sp1x64ult

thanks!

Same problem as everyone above regarding only build 7601 being supported even though I am on build 7601. Also the fix in the previous couple of posts did not seem to apply in my case as the product name, version, build etc were all correct.

In the end I booted into safe mode and renamed current termsrv.dll and copied over the new one. (Note annoyance with having to reset security permissions on old file as it required a"TrustedInstaller" to rename the file.) All now works ok. Not sure about the rdpclip file, I didn't bother with that and it still seems to work without any probs.

Can anyone advise if that file is necessary?

Thanks

rdpclip (aka RDP Clipboard) is only needed if you want to be able to use the shared clipboard on Home Premium.

Unfortunately it didn't work for me. Ran the script as administrator and it completed successfully but after reboot I still don't see the option to allow remote desktop connection under Remote Settings, only remote assistance. I'm running Win7 Home Premium 32bit with official SP1.

it does not change the GUI, so you still won't see those choices. But RDP is enabled - try connecting to it from another machine. Worked fine for me. Win 7 x64 Home Premium.

I have attempted a few time to run the patch but keep coming up short. The first time I get the cannot find 64 bit terminal and the second a success. Though when I attempt to connect I am forced to log off the other user. 

Running Windows 7 Ultimate Build: 7601 Sp1

 

Source Folder is C:\Dev\W7-SP1-RTM-RDP\, Windows is 64-bit

 

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

processed file: C:\Windows\System32\termsrv.dll

Successfully processed 1 files; Failed processing 0 files

Stopping Remote Desktop Services

The following services are dependent on the Remote Desktop Services service.

Stopping the Remote Desktop Services service will also stop these services.

 

   Remote Desktop Services UserMode Port Redirector

 

The Remote Desktop Services UserMode Port Redirector service is stopping..

The Remote Desktop Services UserMode Port Redirector service was stopped success

fully.

 

The Remote Desktop Services service is stopping.

The Remote Desktop Services service was stopped successfully.

 

        1 file(Drunk copied.

 

The 64 version of termsrv.dll is not present

 

Use switch -? to show help.

 

Press any key to continue . . .

 

 

 

=============================================

Second

Source Folder is C:\Dev\W7-SP1-RTM-RDP\, Windows is 64-bit

 

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

processed file: C:\Windows\System32\termsrv.dll

Successfully processed 1 files; Failed processing 0 files

Stopping Remote Desktop Services

The following services are dependent on the Remote Desktop Services service.

Stopping the Remote Desktop Services service will also stop these services.

 

   Remote Desktop Services UserMode Port Redirector

 

The Remote Desktop Services UserMode Port Redirector service is stopping..

The Remote Desktop Services UserMode Port Redirector service was stopped success

fully.

 

The Remote Desktop Services service is stopping.

The Remote Desktop Services service was stopped successfully.

 

######################################

# Patched Already ,Config Editing... #

######################################

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

 

Updated 1 rule(Drunk.

Ok.

 

Starting Remote Desktop Services

The Remote Desktop Services service is starting.

The Remote Desktop Services service was started successfully.

 

Pausing 5 seconds to give service time to start listening

Checking if Service is listening on port 3389

Hey guys, I ran the script after updating my build and it worked wonderfully.  I went ahead and enabled multi users.

Is there a way that I can see, on the display, on the server what I doing when controlling remotely.

Basically I am trying to control xmbc from my laptop but I want the display to be off the server I have remotely connected too. 

Did I mess up in installing multi?

Please help, seems like you guys have a lot of knowledge and I would really appreciate a point in the right direction. I am trying to avoid having a wireless keyboard sitting on my coffee table just to run media off my server on to my TV.

 

I appreciate it

jockmonkey wrote:

Hey guys, I ran the script after updating my build and it worked wonderfully.  I went ahead and enabled multi users.

Is there a way that I can see, on the display, on the server what I doing when controlling remotely.

Basically I am trying to control xmbc from my laptop but I want the display to be off the server I have remotely connected too. 

Did I mess up in installing multi?

Please help, seems like you guys have a lot of knowledge and I would really appreciate a point in the right direction. I am trying to avoid having a wireless keyboard sitting on my coffee table just to run media off my server on to my TV.

 

I appreciate it

 

Yes, login into another administrator user in your PC with remote desktop.

go to cmd and write "qwinsta" (without " "), it will show active sessions and IDs

 

then write "shadow 0" (0 its session ID you want to control). That way you will control it and whoever is on it can see it.

 

PD: It will ask whoever is on PC if he want to give you the control, you can disable this changing group policies and such... (i mean, you can disable warning and take control of any session without permission of the user, you'll need it if no1 its on the PC)

using "shadow console" is a little easier, you won't have to worry about what the session is.

the registry key to bypass the warning\prompt is listed earlier in the thread.

one question, i've connected to my home PC, i cant enable "only one remote session" because it will disable "singlesessionperuser".

 

But i have a problem, when i closed session sometimes, i reconnected and when i connect again i will have another session opened, and cant shadow old remote one (its inactive).

Any idea how to do it? (i mean, get back to my original inactive session instead of openning a new one)

And thanks, didnt know you could do it with "console"

 

PD: Nevermind, solved it, i closed the new session and opened remote desktop again, and it re-joined my old session, altho sometimes this wont work (altho it would be fine to know how to manage it).

Black_ice_Spain; Michael welter-

The remote command prompt will not recognize 'qwinsta'

 

running windows home ed with this hack

 FYI, not that it should matter at the moment but, I am running different OS- server(pc)being accessed/ and laptop(mac) accessing

Neither qwinsta.exe or shadow.exe is availabe on Home Premium.  You have three choices:

1- Use the Task Manager to Remote Control a session.  To do so launch Task Manager; Under the Processes tab hit "Show processes from all users" (this gives you administrative rights needed to shadow; Under the Users tab right click the user you want to shadow and hit Remote Control
2- Search for the executables under %SystemRoot%\winsxs and copy them to %SystemRoot%\system32
i.e.
CD %SystemRoot%\winsxs
DIR /s shadow.exe
3- Find the files on the internet (I don't suggest it since #2 is easy enough)

 

First let me say much thanks for this script. I am running x64 Home Premium.

 

For choice 2:

Shadow.exe is in the winsxs directory however it is in the command line tools subdirectory. Copy shadow.exe to the Windows/System32 directory and the shadow command line works!

i only tried on win7 professional, you can try downloading qwinsta manually from internet if you can find it (in case your error its because home edition doesnt come with it). <-- With remote command prompt i mean open remote desktop and inside of it open "cmd.exe", client OS shouldnt make a difference.

 

Anyways you dont need it, as michael said above, "shadow console" also works (console its the identifier of current active session on physical location of the PC)

works like a charm Wink

question: why is the default to allow blank user passwords?  the earlier version prompted for this.

its not enabled by default, the "1"in scripts it makes it look like it, but wont login with blanks =).

Thanks! Worked great on Windows7 Pro (7601) with official SP1 - Dutch.

I can't get it to work on Win7 Ultimate x64 SP1:

Quote:

OS Name: Microsoft Windows 7 Ultimate 
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free

 

Quote:

Your operating system is not supported.
Only for Windows 7 Build 7601
Press any key to continue . .

The script worked great!  Thank you so much for your hard work!

 

Windows 7 Home Premium SP 1 here (x64) here (standard US English version).  

*** Thanks a billion ***

I changed the script as insturcted and no luck. it says it patched okay but i get the log off screen when i try to have others log in. using w7 enterprise and ultimate. will missing remote be coming out with an offical patch?

I changed the script as insturcted and no luck. it says it patched okay but i get the log off screen when i try to have others log in. using w7 enterprise and ultimate. will missing remote be coming out with an offical patch?

Fantastic work, this code works like a charm.

Much appreciated!!

I use an french seven sp1 and the script didn't work out of the box.

There is no "Administrators" group but "Administrateurs"

Once i replaced all of them the script worked like a charm. thanks a lot.

How do you go about unistalling this? 

 

Rename %SystemRoot%\system32\termsrv.dll.7601.1130.bak to termsrv.dll, replacing the existing version.

I'm not sure what you mean by "replacing the existing version. I renamed it termsrv.dll and now I have:

termsrv.dll 

termsrv (2).dll 

You can delete termsrv (2).dll.  Instead of replacing you hit yes to a prompt on whether to rename the existing file.  Basically same thing.  You are back to the untouched version now.

It's still not acting like it did before. It use to kick the client user off and log me on. Is it because I added the Multi?

Downloaded the file "W7-SP1-RTM-RDP-v2.zip" on 3/24, and follow the instruction in the "MissingRemote.com.txt".  The "termsvr.dll" for Windows 7 Sp1 Ultimate 64-bit is patched and updated successfully with a new Modified Date of 2/25/2011.  Now, multi-RDP sessions are on just like it supposes to be.  Mike Garcen and the MissingRemote team, great job and THANK YOU!

win7 ultimate sp1 : worked perfectly, thanks

Does not work for me (win7 enterprise sp1). For some strange reason, my termsrv.dll files are located in winSxS folder so copying to System32 does not have any effect. These are the paths:

c:\Windows\winsxs\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7600.16385_none_ea94336f6df51e09\termsrv.dll

c:\Windows\winsxs\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.17514_none_ecc547376ae3a1a3\termsrv.dll

The file in the second path is "untouchable" - I can't delete it, rename it, take ownership of it (even if I stop terminal services).

 

This is the result of the script (earlier I manually stopped terminal service). After the script concurrent multi-user logging does not work - when my friend tries to log in on his account I get prompt that my session will be disconnected in 30 seconds, or something like that.

 

Source Folder is G:\Remote Desktop Hack\W7-SP1-RTM-RDP\, Windows is 64-bit

Taking ownership of C:\Windows\System32\termsrv.dll

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

More help is available by typing NET HELPMSG 3521.

        1 file(Drunk copied.
Copying "G:\Remote Desktop Hack\W7-SP1-RTM-RDP\64_termsrv.dll" to "C:\Windows\System32\termsrv.dll"
        1 file(Drunk copied.
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

Updated 1 rule(Drunk.
Ok.

Starting Remote Desktop Services
The Remote Desktop Services service is starting.
The Remote Desktop Services service was started successfully.

Pausing 5 seconds to give service time to start listening
Checking if Service is listening on port 3389
  TCP    0.0.0.0:3389           Simplex:0              LISTENING
  TCP    [::]:3389              Simplex:0              LISTENING
Service is listening
Done
Press any key to continue . . .

Michael,

Any hope of enabling audio on home premium? (or is there a file I can swipe off one of my win7 ultimates to enable the functionality?)

thanks

-jim

 

hi. i've just purchased a netbook running windows 7 starter build 7600. it's only now i learned that it is not capable of fast user switching. can anyone help me with this dilemma? i wish to switch to another user without logging off my account. please tell me if this is possible. i await your advise. thanks in advance.

I had the previous patch working fine. I also had the beta sp1 which i recently deleted and installed the rtm sp1 which of course broke the previous patch. I'm  using windows 7 professional sp1 build 7601. When i attempt to do this patch it just says Its only for build 7601. Am I missing something?

Working for me. THANKS

Working for me. THANKS

dont work for me. i got an error

your operating system is not supported

only for windows 7 build 7601

press any key to continue..

i have a windows 7 ultimate build 7601 sp1 than k you in advance

I hope this isn't a dumb question but is there any way of getting sound? Sorry I'm new at this.

hi!

 

It doesnt work, i had W7 Ultimate Ver 7600.

it says it only workd for 7601 is there a previous patch?

 

THANKS!

 

and for Server 2008?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Website design by Yammm Software
Powered by Drupal