Force user to log off after being idle

Posted on 2007-10-08
Last Modified: 2013-12-04
Can i force a user to logoff when their terminal has been idle for some time. im interested in doing this for win2000 machines on sbs2003 domain. I dont want to use logon hours which is the only option i found in Domain Security settings.
Question by:Powerhousecomputing
    LVL 10

    Expert Comment

    What is the Terminal Server running? 2003 or 2000?

    I usually use this guide as a starting point, just to make sure I cover all the basics.

    I have only tried this on Server 2003 servers, so I'm not sure if all the settings are available on older OSs.

    This does include a section that limits logon sessions, you will find what you need in there - among a host of other lockdown settings!
    LVL 10

    Expert Comment

    OK I just looked through the guide, it doesn't cover your exact question, so here's what you need:

    Policy > Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Sessions >

    Here you'll find several policies you may want to configure, including:

    "Sets a time limit for active but idle Terminal Services sessions"

    I assume you're familiar with group policy, but let me know if you need further information.



    LVL 70

    Expert Comment

    if we are talking about terninal server session then you can set a limit in the terminal server sessions as described above

    If this a "normal" workstation rather than terninal service then these is no built in feature for this - however you can do it with some clever scripting see
    LVL 10

    Expert Comment

    Aha.. good point KCTS - I saw terminal and straight away thought terminal server... on another look, your answer is probably what the author was after...
    I haven't had any Windows 2000 for a long time now so I don't even know what group policies can be applied to them!!
    LVL 52

    Accepted Solution

    There is a simple screen saver for that: winexit.scr and tells you how to get and configure it.

    Featured Post

    Why You Should Analyze Threat Actor TTPs

    After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

    Join & Write a Comment

    No security measures warrant 100% as a "silver bullet". The truth is we also cannot assume anything but a defensive and vigilance posture. Adopt no trust by default and reveal in assumption. Only assume anonymity or invisibility in the reverse. Safe…
    Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    734 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    23 Experts available now in Live!

    Get 1:1 Help Now