Moving the mouse or touching the keyboard "wakes" up the monitor and computer in seconds. Power management, standard in Windows and Mac operating systems, can put inactive monitors and computer systems (CPU, hard drive, etc.) into low-power "sleep" mode.
I'd like to know why Windows 10 isn't treating the screensaver timeout setting the same as Windows 7 is.Modern computers are designed with energy-saving components and come with advanced power management.
I'm trying to figure out now the best way to go about this. I saw none there, or in the Event Viewer, and I even confirmed the screensaver lockout setting is set in the registry. I ran RSOP just as he did and looked for an errors.
His problem ended up being the screensaver timeout option GPO wasn't being applied because it conflicted with another GPO in his environment. I saw a forum post that someone had a very similar situation as me. On Windows 10 it seems as if Windows is ignoring the screensaver timeout option when logged in as an extended timeout user and the power options are the only settings that are being used. And when an extended lockout guest/service account logins in, the screensaver timeout GPO keeps the machine from locking. The machines get their computer power policies for when regular users/students login. There is an OU in our AD that has some extended timeout guest accounts that has a user policy applied that turns on the screensaver and sets the screensaver timeout option to the highest value that it can. First off, how the GPOs are setup now is the machines get a power policy that is relatively run of the mill with setting that turns off the display after 10 minutes of inactivity. After digging into this all afternoon today I made some observations.
0 kommentar(er)
