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).

And, as mentioned, test on someone first.

[image: Inline image 2]

On Wed, Sep 6, 2017 at 8:26 AM, Michael Leone <[email protected]> wrote:

> 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.
>
>
>

Reply via email to