I have been trying to give my network more flexible security. We are new to a Domain and Active Directory so we would like to make it smooth for our users. This is what I'd like : ScreenSaver comes on at 10min, Display Sleeps at 20min and Screen Locked at 30min (20min after screen saver comes on.) I have tried the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon - ScreenSaverGracePeriod (REG_SZ) and it works if the value is less than 60 then it works, but it will lock the screen (requiring password) after 60 seconds even if I enter a number larger than 60. (ie 90, 300, 600, 1200 all lock at 60) Is there any way to accomplish what I would like.

Hi, Based on my knowledge, the upper limit for this key is still 24 days (2,147,483) but as per the security guidelines it is recommended to keep it to 255. This doesn’t mean that we cannot set it beyond 255. http://support.microsoft.com/kb/929135 Note: Clean Boot is a step of troubleshooting, we can go back to normal by running MSCONIFG. I suggest that you may try to produce this problem in Clean Boot and let me know the result. If the issue persists, I would transfer this thread to a senior engineer.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Sorry, I have been out. I will try to work on it this week, I have tested this on 4 different computers, but I will try a clean boot.

I have booted into Clean Mode, and the system still locks (Requiring Password entry) after 60 seconds, even though I have the registry key set to 120. When I exit the screen saver prior to 60 seconds it returns my desktop as expected. The only item that is still enabled in services is Symantec Endpoint Protection. I will uninstall SEP and see if it makes any difference.

I have uninstalled SEP and I still only get 60 seconds of ScreenSaverGracePeriod.

Hi Linn, you mentioned that the computers are members of a domain? I believed that you there may be a policy setup on the domain (in Active Directory) overriding the screensaver, display sleep and computer sleep settings. I would check to make sure those policies, if any are changed to your preference.

I have tested both on and off the domain. I am the domain administrator, I have created all the Policies and I do not think any are effecting this. The most recent tests were on a NON-Domain laptop. Fresh install of Windows 7 Pro SP1, IE9, Office 2007, All updates.

Please transfer this thread to a senior engineer. The Grace Period will not grant more than 60 seconds, but does work at anything lower than 60 seconds. I have completed tests with fresh windows 7 pro 64bit SP1 install, clean boot, and on production machines.

Has there been any update on the screen saver grace period only working upto 60 seconds?

Hi Linn, I have the same problem; please let me know, if there is any solution, you came to know by now. Thank You!

I have not found a solution, I am under the impression that MS is working on it per zhen tan's post. But at this time, I'm letting my users decide how they want to run their screen saver, and lock, and power savings... I'm still interested in a true solution.

Have you tried group policy http://technet.microsoft.com/en-us/library/ee617164(v=ws.10).aspx Using the screen saver to lock the system when it is not being used It is possible to enforce a system lock after a defined interval. This requires the following two policy settings: Password protect the screen saverScreen saver timeout Changes to legacy Group Policy settings In Windows 7, many legacy Group Policy settings have been removed or located so that domain administrators can find all of the relevant options in one place. The full path of this node in the Group Policy Management Console is: User Configuration\Administrative Templates\Control Panel\Personalization Available policy settings: Name Explanation Requirements Prevent changing color scheme This policy setting is removed in Windows 7. If you enable the Prevent changing window color and appearance policy setting, you can prevent users from changing the colors and system metrics of your windows. Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP Prevent changing theme This policy setting allows you to prevent users from selecting a different theme or saving any of their customized themes. If you enable this policy setting, the theme gallery in Personalization in Control Panel does not function. At least Windows XP Professional or Windows Server 2003 family Password protect the screen saver This policy setting allows you to lock the system. If you enable this policy setting, the system locks at a user-defined interval. This policy setting is effective even when no screen saver is selected. Note If you want to control the time interval, use the Screen saver timeout Group Policy setting. At least Windows 2000 Service Pack 1 Screen saver timeout This policy setting allows you to specify the amount of idle time that must elapse before launching the screen saver. If you enable this policy setting with the Enable screen saver policy setting, you ensure that the system lock will work even when no screen saver is selected. Note The system will lock at a user-defined interval. If you want to control the time interval, use the Screen saver timeout policy setting. At least Windows 2000 Service Pack 1

http://www.sevenforums.com/tutorials/106343-screen-saver-timeout-period-set-change.html

You are missing the point. I can enforce the ScreenSaver Timeout. It's the GRACE Period we're looking to set. This is the time between the screen saver launching and the computer being locked. Technotes say it can be set from 0 to 2,147,483 seconds, but I'm finding in Windows 7 Pro it is only working from 0 to 60 seconds.. I want the screensaver to launch, then allow 20 minutes of time to pass before the computer is locked. This will allow my users to use the rest room, grab some coffee, answer the phone...without having to log back in each time. Most of our computers are in a secure locations so other users gaining access is not a big concern.

http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/639e88eb-c9c3-4a8e-951e-4c6b5a852b6f/

Hi Linn and all the others out there! I just found this article at Microsoft's support http://support.microsoft.com/kb/2685088 I did not try it yet, but by description it should solve the problem. P.S.: ... seems to work ...

Hi Linn and all the others out there! I just found this article at Microsoft's support http://support.microsoft.com/kb/2685088 I did not try it yet, but by description it should solve the problem.