• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1717
  • Last Modified:

Auto Log off a RDP session

We have a messaging system consisting of Thin Clients connected to TV's.
Currently the Thin Client login automatically runs a Powerpoint presentation on the desktop.
What we want to do is either in the script or as part of a scheduled task on the RDP servers is have the unit automatically log off after 30 minutes. This way when the Thin Client automatically logs back in it will pick up any new revisions of the document and display them.

What would be the easiest way to do this?
  • 4
2 Solutions
kiwistagAuthor Commented:
Thanks, I am aware of that setup but after something more definable.
I'm more after a command(let) that may work, i.e.
shutdown /l

Open in new window

but off a timer since /t won't work with /l

There is a login script that is run on login and I was hoping to put it in there.
If there is no readily available answer then I may have to revert to the GPO
can you check with terminal server and publish with RDP file ?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

kiwistagAuthor Commented:
The Thin Clients are Windows .CE based so there are no RDP files.
kiwistagAuthor Commented:
The downside to a logon timeout as specified in a GPO is that the Thin Client knows when this has happened and pops up with a message stating that the session has timed out and logged off.
The only way to remove this message is interactively which of course means we have to remote onto the Thin Client (via Altiris) and OK the message.
A manual or shutdown /l logoff doesn't bring up any messages.

What I have done however is set a batch script to run on logon via GPO (User Settings > Policies > Windows Settings > Scripts) to run the timeout command then just "shutdown /l".
This then doesn't interfere with the user logon script.

Thanks for all your input.
kiwistagAuthor Commented:
Solution by submitter was useful, however did not resolve other technical issues.
I ended up finding a semi-solition from a mix if his answer and alternative possibilities.

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now