Solved

How to use Group Policy to remove the "Lock Workstation" timer?

Posted on 2008-10-22
2
1,050 Views
Last Modified: 2008-11-03
I have seen several situations where people needed to shorten the amount of time it takes for a workstation to lock itself, however I am looking to do the opposite.  Several users will share a warehouse computer that is logged in...  they do not logout and will just share the one account to use the shipping program.  Although they may share the same login, they do not share each other's passwords.

I need to disable to lock timer, or set it to some crazy high time (999 hours, etc).  

I have used Group Policy to remove the ability for a user to lock the workstation, but I am unsure if this affects the systems "Auto-Lock" timer.

0
Comment
Question by:ccinfosys
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 4

Assisted Solution

by:Jerrod_W
Jerrod_W earned 250 total points
ID: 22780175
You can set the screen saver to however long you want it to go. Under GPO / User Config / Administrative Templates / Control Panel / Display / Screen Saver Timeout
0
 

Accepted Solution

by:
ccinfosys earned 0 total points
ID: 22780365
So the screen saver timeout also dictates how long a computer will wait before it locks itself and we get a "CTRL-ALT-DELETE" prompt to log back in?

I'll give it a shot.
0

Featured Post

10 Questions to Ask when Buying Backup Software

Choosing the right backup solution for your organization can be a daunting task. To make the selection process easier, ask solution providers these 10 key questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
Let's recap what we learned from yesterday's Skyport Systems webinar.
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…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

617 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