So for the sake of testing, make sure you use different time values for things so that you can tell if something was triggered by power settings, screen saver, GPO, etc. Don't use standard times, pick things like 2, 8, etc., and make it easy on yourself. :)
-- There are 10 kinds of people in the world... those who understand binary and those who don't. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Wednesday, September 6, 2017 2:35 PM To: [email protected] Subject: Re: [NTSysADM] Group Policy - Enforce screensaver and password On Wed, Sep 6, 2017 at 2:05 PM, Kennedy, Jim <[email protected]> wrote: > So did your power settings only partially kick in...like 10 minutes to > dark...30 to lock...and you only waited 10? Dark kicked in at 10. Most of my PCs are set to never go to sleep (AFAIK - I haven't been too finely detailed on the workstation setups). > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Michael Leone > Sent: Wednesday, September 6, 2017 1:51 PM > To: [email protected] > Subject: Re: [NTSysADM] Group Policy - Enforce screensaver and > password > > On Wed, Sep 6, 2017 at 1:13 PM, Webster <[email protected]> wrote: >> How about testing it on a test user account so you will know exactly what >> happens??? It is a user policy setting so you can restrict it to a single >> user account for testing. > > I am testing it. :-) That's why I asked - I set it to enforce a password > screensaver, but then didn't set a screensaver (as the user). > And the situation happened as I described - monitor went dark (power), but > clicking on anything put me right back into the session, no password. That's > what I need to find a way to avoid ... > > >> >> >> Webster >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Michael Leone >> Sent: Wednesday, September 6, 2017 11:03 AM >> To: [email protected] >> Subject: Re: [NTSysADM] Group Policy - Enforce screensaver and >> password >> >> On Wed, Sep 6, 2017 at 11:38 AM, Wolf, Daniel <[email protected]> wrote: >>> Don't specify a screensaver. It will just lock the machine with the screen >>> off. >> >> OK. So what if the user doesn't choose a screensaver. Then nothing happens, >> right? No screensaver, and - more importantly - no password needed to unlock >> the PC (presuming the display turns off, for power saving). I got the >> impression that this is what he is trying to prevent. Doesn't want people >> just walking away from a PC, and leaving it unlocked, for anyone to walk up >> and do nefarious things ... >> >> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Michael Leone >>> Sent: Wednesday, September 6, 2017 10:26 AM >>> To: [email protected] >>> Subject: [NTSysADM] Group Policy - Enforce screensaver and password >>> >>> I've had a "suggestion" from my CIO. :-) He would like to use GP to enforce >>> that all domain computers have a screensaver (set to like 15 minutes), and >>> that the screensaver is password enabled. He didn't seem to care which >>> screensaver, as long as one is set. >>> >>> (these are all Win 7 PCs, BTW) >>> >>> I see the options in User Config/Policies/Admin Templates/Control >>> Panel/Personalization that I can Enable Screen saver and password protect >>> the screen saver. But if I read it right, I either have to specify which >>> screen saver to use, or depend on the user to pick one. >>> >>> So what happens if I choose >>> >>> Enable screen saver: ENABLED >>> Password protect the screen saver: ENABLED screen saver timeout: 900 >>> seconds >>> >>> and the user does *not* set a screensaver? If I use the above settings, do >>> I really also need to force a specific screen saver, so that I can be sure >>> that at least a passworded screen saver is set? >>> >>> What do the rest of you do? I'm assuming at least some of you enforce >>> passworded screensavers. >>> >>> Thanks for any advice. >>> >>> >> >> > >
