Tony Interesting indeed. I have never used this way. Do you think it would work for a terminal server environment?
Deb From: <[email protected]> on behalf of Tony Burrows <[email protected]> Reply-To: <[email protected]> Date: Friday, September 8, 2017 at 10:49 To: NT Sys Admin <[email protected]> Subject: Re: [NTSysADM] Group Policy - Enforce screensaver and password I recall something about this method being deprecated in the future and Microsoft is pushing people to use the Machine inactivity limit setting instead. Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies / Security Options > Other > Interactive logon: Machine inactivity limit. After the number of seconds of inactivity set in this policy, the computer will lock. No other settings are needed to get this to work. You could set the screensaver policy too if you want but it isn't needed. Regards, Tony On Thu, Sep 7, 2017 at 9:59 AM, Kurt Buff <[email protected]> wrote: > On Thu, Sep 7, 2017 at 5:25 AM, Michael Leone <[email protected]> wrote: >> > >> > On Wed, Sep 6, 2017 at 2:25 PM, Kurt Buff <[email protected]> wrote: >>> >> >>> >> Below is a picture of what we do. We just lock the screen. Doesn't matter >>> if the user chooses a screensaver or not - the screen locks after 900 >>> seconds (too long in my opinion, but it quelled the screaming). >> > >> > >> > AH HA. That's the sort of thing I was looking for. That command does lock >> the screen, no need to worry whether a screensaver was set or not. So while >> it's not a "real" screensaver, it does serve the ultimate purpose (locking >> the machine, and requiring a password to unlock). >> > >> > Thanks so much! This seems to be working in my testing. > > > Glad to hear it. I can't remember where I found it, but it was a good > day when I did. > > Kurt > >
