Remote desktop client

[Guest]

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]]

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

 

[Guest]

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

 

[Guest]

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