Re: Seting screen saver exeuctable name in GPO has side effects

Shenan Stanley

Brian McCauley wrote:
> Setting the Group Policy item "Screen Saver executable name" to
> "SomeFilename.scr" whilst leaving the "Password protect the screen
> saver" not configured does not work as documented.
>
> According to both common sense and the documentation it should
> leave the "Password protect the screen saver" choice to the user
> but the actual effect is that the "Password protect the screen
> saver" checkbox is cleared and greyed out. (And the screen saver is
> not actually enabled).
>
> The reason for this is that half the system thinks
> "SomeFilename.scr" is not a valid screen saver whilst the other
> half thinks it is.
>
> The work-round is to specify the screen saver as
> "%SystemRoot%\system32\SOMEFI~1.SCR" and then it all works as it
> should.

What are you referring to? What specific 'documentation'?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way