Those that uses RDP would know that a proper disconnection or logoff of a session is necesaary. But with WDP there is no such power options. Just the good old click on X to close connection.
Hopefully in the RTM version this will get rectified.
Those that uses RDP would know that a proper disconnection or logoff of a session is necesaary. But with WDP there is no such power options. Just the good old click on X to close connection.
Hopefully in the RTM version this will get rectified.
Yes, it has been annoying me. Oh well. Having multiple favourites in an easy to access location is nice.
From an IT Support point of view this is a top 5 must have feature . I waiting to see how this is rectified, could it be this DP version a Starter versionbut RDP exists so how can it?
Hi there
While this needs to be fixed --surely from an IT point of view it's up to the REMOTE connection to chuck a user off / log out when a connection has been idle for so many minutes.
Can you imagine logging in to a Production type ERP system say SAP for example and then leaving your terminal logged on and going away for an hour or so.
Just my take on this
Incidentally the Power options on W8 include sleeping the computer after so many mins, turning off monitors / Disks etc etc.
Go to Power options in control panel -- switch to desktop view once you've got into the control panel.
Cheers
jimbo
That depends. Most workplaces should probably have a policy in place that would check on BOTH ends if a connection is idle and disconnect it, but for more personal / recreational use, and for professional operation, it would make sense to have a more easily accessible disconnect option.
I know that by right clicking the top of the screen and pressing the X button, the server will disconnect, but I wasn't actually aware that it didn't have the option to log off the remote computer... Perhaps this is something that could be done server-side?
You mean the enduser logging off the remotely connected session of his or her machine? If so when and how would that person know when to do it, and usually when a computer is remote accessed the screen is locked and a non admin account would have issues unlocking it. As for RDPing to a server, logging off is mandatory after finished so that other support staff can remote in especially when the max rdp session has been reached.
Hi there
You obviously haven't understood the post
I Said the REMOTE system should know when to disconnect the user --nothing to do with the person who actually logs on.
All the remote system needs to do is to see how long a connection has been idle and if it exceeds a pre-determined time - say 10 mins on a production system it just disconnects the connection --doesn't even NEED to know who the remote user is .
Cheers
jimbo
What do you mean by remote system, the computer you are remoting to?
This is about logging off an RDP session after you have used it, in the appropriate manner. Enduser are effected if you disconnect the session not logging off properly. As said before you do not leave your RDP session to expire after a period of time on it's own. This is not IT practice.
Hi there
I would have thought that was fairly obvious -- you are talking about RDP so presumably that means YOU as the user (Client) are logging on to a remote computer which in effect is acting as a SERVER (even if it's only another computer running a basic Windows OS).
The computer you are trying to log on to is the REMOTE orr "Server" side computer and this should have enough logic in it to disconnect an idle connection.
The computer you are currently using is known as the Local or Client computer.
Cheers
jimbo
Hi there
I would have thought that was fairly obvious -- you are talking about RDP so presumably that means YOU as the user (Client) are logging on to a remote computer which in effect is acting as a SERVER (even if it's only another computer running a basic Windows OS).
The computer you are trying to log on to is the REMOTE or "Server" side computer and this should have enough logic in it to disconnect an idle connection.
The computer you are currently using is known as the Local or Client computer.
The Local computer doesn't have of course to log you off but the remote server should log off after a period.
It definitely IS standard practice when connecting to remote servers such as ERP systems (SAP etc) or even your online Banking system to time users out after a certain period of inactivity -- and if you say this is NOT standard I.T practice I'd hate to have your consultants running my servers !!!!!
Cheers
jimbo
| Similar Threads | ||||
| Thread | Forum | |||
| Power Options Menu - Add or Remove Sleep or Hibernate in Windows 8 | Tutorials | |||
| Possible Installation/Upgrade Options | Installation & Setup | |||
| Possible Installation/Upgrade Options | General Discussion | |||