activate screensaver for many PCs

I need to activate a large number of screensavers on windows 2000 PCs , in a NON active directory environment.

currently:
I can start up MMC and activate the Local Computer Policy remotly on any PC and:
Local Computer Policy > User Configuration > Administrative Templates > Control Panel > Display >
and edit the 4 screen saver options

Saves visits to desktops, but this is going to lame with 100 PCs.

How can I export a user configuration and then import it to workstations from the commandline? (I plan on doing this via login batch script)

Marketing_InsistsAsked:
Who is Participating?
 
Debsyl99Connect With a Mentor Commented:
Hi

I'm not at a 2k pc with available resources right now so can't give you the solution exactly. Here's what to consider though:

First setup a win 2k pc as you want it (I only have acess to xp right now). Then export the relevant registry key - just easier than writing it yourself plus I'm on XP pro right now so can't guarantee you can copy the below and paste it into a notepad file then save as .reg file.

ie export the desktop settings to a registry file  (say you call it screen.reg - then edit to keep only the settings you need: ie screensaver settings only (this is for winxp right now) - timeout is in seconds  - this example is for 1 minute so adjust as you need.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Control Panel\Desktop]
"ScreenSaverIsSecure"="1"
"ScreenSaveTimeOut"="60"
"ScreenSaveActive"="1"
"SCRNSAVE.EXE"="C:\\WINDOWS\\System32\\ssflwbox.scr" (or whichever you want)

This should give you a relevant .reg file so long as you save it with .reg extension. Next you need a batch file to merge it with the client registry - test it first obviously!
A batch script would use for example:

regedit.exe /s C:\screen.reg                            - this is assuming screen.reg is saved in C:\ - use relevant path to screen.reg

Your next issue, and the hardest is how to get the reg file to merge with the existing registry with relevant permissions. Problem is with user logon scripts is they usually run under the permissions of the user account they apply to. This is fine where a user is a local admin. Often they won't execute where a user doesn't have relevant permissions to that part of the registry. (Wherein lies some of the beauty (if you can call it that!) of active directory)

Registry Scripting
http://www.windowsitlibrary.com/Content/314/1.html

Hope that's a start at least,

Deb :))

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.