CCLCLS
asked on
how to prevent RDP session to win 7 computer that is already in use?
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.
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.
ASKER
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......
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......
...so 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.
But you are right, there need to be some que-system for RDPing to a shared machine, Haven't seen one though.
> 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.
@ola_erik
" 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.
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.
@ola_erik
" 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.
@McKnife
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.
@ola_erik
" 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.
" 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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
no good answer I guess
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?
So, what's next?
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.