how to prevent RDP session to win 7 computer that is already in use?

Posted on 2014-02-04
Last Modified: 2014-02-13
using win 7 pro.
the scenario being that the computer is being used locally but also remotely by another user. the remote user RDPs and kicks off the local user. is there anyway in GP or other to prevent that from happening at all but still allow the RDP if the computer isn't in use.
Question by:CCLCLS
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
LVL 54

Expert Comment

ID: 39834128

When in use, the user remoting in gets a message that somebody is logged on and will not be let in until 30 seconds have passed. During that time, the user at the console can deny him access. If he doesn't deny, his session is not ending, but just being disconnected =suspended. So please describe more detailed what your problem is.

->How should anyone determine if the computer is not in use if somebody is logged on?
You could only set an idle timer that logs off all users if the computer has not done anything since 30 mins or so. So that could be a solution: tell the remote user he should cancel his connection if he gets the message that someone is logged in and guarantee him that the logout-on-idle will keep the computer free if idling for 30 mins. The latter can be achieved by winexit.scr or scheduled tasks.

Author Comment

ID: 39834164
if local user walks away for 31 seconds or more then they come back and are confused and lost and don't understand what happened....then they login or reboot the pc interrupting the rdp user....

so no setting that instead of giving 30 seconds if local user is logged it iinstead it just doesn't allow it at all....

sorry billjohnson is logged in and using the computer so you cannot rdp at this time. good bye......

Expert Comment

ID: 39834289 bill johnson logs on and forgets to log off, effectively blocking all rdp access to that machine until some1 gets hold of him or restart the machine?

But you are right, there need to be some que-system for RDPing to a shared machine, Haven't seen one though.
Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

LVL 54

Expert Comment

ID: 39834804
> then they login or reboot the pc interrupting the rdp user....
Sorry, but that is not what would happen. If they return, they can logon again. Before succesful logon, they will see a message that another user is using this computer and that now this user needs to consent to their logon (or that they will be logged on in 30 secs). So the users will know what is going on by reading. If the users are unable to read the text, they will be confused but it's their own fault.

" logs on and forgets to log off, effectively blocking all rdp access to that machine" - no, that's simply untrue. Since vista (and in7/8/8.1), the behavior is not like that. Try it.

Expert Comment

ID: 39834844

" logs on and forgets to log off, effectively blocking all rdp access to that machine" - no, that's simply untrue. Since vista (and in7/8/8.1), the behavior is not like that. Try it.

I meant that it would be true if new RDP users could not log off/ push out existing RDP connections. That is, the new functionality would introduce unintended new problems.
LVL 29

Accepted Solution

serialband earned 500 total points
ID: 39836465
Not on Windows 7 or XP or 8.  Those are all client systems.

What you seem to need is a multiple user RDP.  You should get server 2008 or 2012 if you can afford that.  The only way to get that on Windows XP, 7, or 8 is with an unsanctioned hack.  I would not suggest against that in a work environment.

To get the behavior other commenters describe, you need to enable fast user switching.  This will not prevent you from kicking off the local user, but it will not force a log out.  The local user can log back in immediately and kick the other user off.  It's not a full solution, but it at least prevents the local user from losing work from a forced logout.

Enable or Disable Fast User Switching
To enable Fast User Switching, you must also enable the Use the Welcome screen option. This feature cannot be used if your computer is a member of a domain. To enable Fast User Switching:
     1. Log on to the computer as an administrator.
     2. Click Start, click Control Panel, and then click User Accounts.
     3. Click Change the way users log on or off.
     4. If it is not already selected, click to select the Use the Welcome screen check box.

         NOTE: The Use Fast User Switching check box is unavailable until you click to select the Use the Welcome screen check box.
     5. Click to select the Use Fast User Switching check box, and then click Apply Options. Quit the User Accounts tool.
Taken from:

Author Closing Comment

ID: 39856429
no good answer I guess
LVL 54

Expert Comment

ID: 39856494
You don't need to close this question just because automatic reminder e-mails from experts-exchange come in. Keep it open and feedback undtil you are satisfied.
So, what's next?

Featured Post

Create the perfect environment for any meeting

You might have a modern environment with all sorts of high-tech equipment, but what makes it worthwhile is how you seamlessly bring together the presentation with audio, video and lighting. The ATEN Control System provides integrated control and system automation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A safe way to clean winsxs folder from your windows server 2008 R2 editions
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
This Micro Tutorial will give you basic overview of the control panel section on Windows 7. It will depth in Network and Internet, Hardware and Sound, etc. This will be demonstrated using Windows 7 operating system.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question