Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / January 2004

Tip: Looking for answers? Try searching our database.

Remote desktop client

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lugn - 23 Jan 2004 11:11 GMT
When a remote desktop client session timeout becuse it is idle to long, can i get the client to close down without notification or messege boxes at the client side?
Ivan Leichtling [MSFT] - 23 Jan 2004 18:16 GMT
You can do this only if you create your own ActiveX control container
for the terminal services client activeX control.  This is a big task
to fix such a small issue.

>When a remote desktop client session timeout becuse it is idle to long, can i get the client to close down without notification or messege boxes at the client side?

This posting is provided "AS IS" with no warranties, and confers no rights
Jenny - 31 Jan 2004 07:01 GMT
There is a workaround.
Skip the policy settings for idletime
Write a script that uses Query User to find out who's idle and for how long and use tskill to close down the client
You can use msg to send your own message to the client
Finally just schedule the script

Jenny Larse
Sweden
Jenny Larsen - 31 Jan 2004 07:06 GMT
There is a workaround to the problem
Skip the policysettings for idletime
Write a script (vbs) that uses query users to find out who is idle and for how long and end the session with tskill.
Schedule the script.

Jenny Larsen
Sweden
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.