I did manually select a screensaver but still nothing.ĪHA. it did go through on the PC (the settings are all changed and the registry keys are added) BUT. I did like you said, added the policy and the registry keys. Make sure the timeout is the same as what you set in in the Policy section, or results will be inconsistent. This policy is not available on pre Windows Server 2012 as stated. Make sure you look at the spelling - "ScreenSaverIsSecure" is the only key with the second 'r' in the spelling. Using Windows 10 computers on a Windows Server 2008 domain, the machine inactivity timeout on the computers is set to 180 seconds and cannot be changed from the local group policy editor. Registry settings enforced under User>Preferences>Windows>Registry, setting the keys "ScreenSaveActive"=1, "ScreenSaverIsSecure"=1, "ScreenSaveTimeOut"=however many seconds. Policy settings are under User>Policy>Admin>Control Panel, setting the "Enable Screensaver", "Password Protect" and "Screensaver Timeout" options. I allow the user to select their own screensaver (some like the pretty pictures!) If they choose "None", it just locks & requires their password.īut yes, I enforce the screensaver to be "on" and I set the time to lock it by, both under Registry and Policy.
0 kommentar(er)
