GPO "Screen Saver executable name"

[Guest]

My company is implementing a standard screen saver across all machines -
Windows XP and Windows Vista.

Setting the GPO for vista "Screen Saver executable name" seems to behave
differently on Vista in the case when the .scr file does not exist.

If the .scr file does not exist on an XP system, the Computer Locked dialog
is displayed after the specified screen saver timeout value. This is
acceptable.

If the .scr file does not exist on a Windows Vista machine, nothing happens.
The system does not lock itself after the specified screen saver timeout.
This is not acceptable.

Is this behavior on Windows Vista expected? Is this a bug?

Thanks, Brian

 

[Synapse Syndrome]

My company is implementing a standard screen saver across all machines -
Windows XP and Windows Vista.

Setting the GPO for vista "Screen Saver executable name" seems to behave
differently on Vista in the case when the .scr file does not exist.

If the .scr file does not exist on an XP system, the Computer Locked
dialog
is displayed after the specified screen saver timeout value. This is
acceptable.

If the .scr file does not exist on a Windows Vista machine, nothing
happens.
The system does not lock itself after the specified screen saver timeout.
This is not acceptable.

Is this behavior on Windows Vista expected? Is this a bug?

It's probably another oversight by the programmers. Have you considered
putting the .scr file, that the GPO points to, on a central server? Not
sure it will work, but it might do.

ss.