OK,
not "None" We run a wide open facility (University) and
they want the option to use what ever screen saver they
want. We (Tech support) want to require a screensaver PW
but want to allow them the freedom to select what
screensaver they want just not allow them to select "none"
Don't know if it will work for W2K, but the following
worked for me a few years ago with NT4:
1.) Pick a default screensaver and give it a name like "Default.SCR".
2.) Create a policy that locks the user into using Default.SCR and
with the timing and security values you want.
3.) Create a networked folder full of alternate screen savers.
Make it read-only for the users and make sure they can execute
the files in that folder.
4.) Write yourself a little Delphi or C++ app to do the following
1.) Show the user that list of the available alternates.
2.) Run one of the alternates if the user double-clicks on it.
(.SCR files are really just renamed .exe files after all.)
3.) If the user decides that a particular alternate is what he
wants as his screen saver:
1.) Replace Default.SCR on the user's machine with a copy
of the file he selected.
2.) Save a file screensaver.ini in the user's profile
containing the original name of the user's selected
screensaver.
5.) Add to the logon script something to check the user's profile
for screensaver.ini, and if that file exists to look in that file
and replace default.scr on the local machine with a copy of the
appropriate screensaver from the folder created in step (3) above.
My role in the process described above was limited to writing a
little Delphi app for step (4). IIRC, there is a switch you use
with a screensaver to tell it to run in a demo mode. Somebody
else implemented the rest of the process. Between the two of us
and the necessary testing/approval process, paperwork, bureaucratic
crap, etc probably $10000 worth of IT labour went into that stupid
little project just to appease one "manager" who wanted to be able
to select his own screensaver while IT still needed to fulfill a
security requirement for password protected screensavers if people
went away from their machines for a while.
There is probably a better way work around the inability to
get rid of the "none" option, but that is how we were told to
do it.
