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

Windows auto logoff using only Group Policy?

Hello.  I am wondering if there is a way to use only Group Policy on a SBS 2003 domain controller to automatically logoff users after xx minutes of inactivity?  I am familiar with the winexit.scr application, however that wouldn't be pratical in this situation as about 25 users randomly access up to 15 different computers throughout the day.  

I've seen numerous article about this issue, but none seem to be real clear on how you can create a Group Policy to do this on a SBS 2003 server?

Thank you in advance for your help!  
0
Rainman13
Asked:
Rainman13
  • 2
  • 2
1 Solution
 
Mike KlineCommented:
Yeah the screen saver policy or password protect screen saver is the common method

You can try using steady state which has its own template.  Take a look at this question that MVP Laura Hunter helped with a few years ago

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_22815237.html

From the steady state PDF that was talked about in that thread

" By adding the SCTSettings.adm template into these tools, you gain
access to account restrictions and settings that are appropriate for user accounts
on shared computers.

The SCTSettings.adm Group Policy template included with
Windows SteadyState also includes the capability to set idle and mandatory
logoff timers, if Windows SteadyState is installed on your computers."

I haven't used this adm in production but it may be worth investigating.

Thanks

Mike
0
 
Rainman13Author Commented:
Excellent thank you.  I will take a look at this and advise!
0
 
Rainman13Author Commented:
Unfortunately, I don't have the ability to install this on one computer and create the Group Policy template to get a feel for how long this would take to setup an install for 15 computers.  

Looks like the Windows steady state installation (and preconfiguration tasks on each computer) could take 30 minutes to 1 hour / desktop while the group policy part maybe 2~ hours and then another 1 - 2 hours for testing.  

What is your assessment of the time required?

0
 
Mike KlineCommented:
Configuring the policy shouldn't take 2 hours but the testing troubleshooting is usually the part that end up taking the most time
0

Featured Post

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.

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