Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

understanding screen saver

Status
Not open for further replies.

NurseIS

MIS
Sep 3, 2001
46
US
Health care environment - where screen savers are absolutely required; plus they have to be set to 1 minute interval yet be available for quickest access.

Of course, users control the screen savers. If they get tired of the 1 minute savers, they increase the interval. Then wham! Privacy inspections occur and one non-compliant workstation would cause a fail rating. I've been reading the threads here for solutions. Have had little help in the NT manuals.

What are the possible ways to manage client screen savers on the network side?

Can any or all of these be done....(?)
* set a default screen saver that becomes THE scr saver for any user acct on that PC regardless of scr saver being defined in user's profile
* preferred (hope) would be a way to control scr savers from central network; policy editor, logon script - ???
* set default scr saver that will be used if user does not set one up
* fix interval at 1 minute; user unable to change interval
* saver not locked; the PCs are shared 24 X 7 and users do leave work without logging off
 
You could disable access to the control panel, and display settings to all users except administrators. That way you could set up the screen saver the way you want, and then no users would be able to go in and change the settings. This would mean implementing policies to do this.

Hope this helps...

mot98..[peace]

"Where's the beer?"
 
You could create a custom executable with all of the properties mentioned to run from a "call" statement in the login script. The user would be able to use Task Manager to shut it down but they would have to do it every time they logged in. This would also totally bypass the screensaver issues.

...just a thought during lunch... A+, N+, MCP
 
Policy Editor can lock down access to the display properties. We also used a 3rd party app called ScreenLock. It was pretty cool. It could tell you when someone failed to unlock the screen succesfully. If memory serves, it's a fairly inexpensive shareware product.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top