Discussion Locked

ScreenSaver Settings

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are attempting to implement a mandatory screensaver settings. But what we are noticing is that although the HKCU shows the desired screensaver settings, the ScreenSaver Tab shows other settings (and these are the ones the system apparently uses). How do we get both to correctly reflect our desired settings. We have trying both Scripts (KIXTART) and GPO's. Thanks.

4 replies

by cg it

Try this on a test server/workstation setup.

For a W2K 2003 Server with Active Dirctory installed, log in on the DC using the administrators account. Click start, choose run. Type in mmc to open the MMC console. Click on Console in the upper left corner, choose ADD/Remove snapin. Click the Add tab from the add standalone snap-in window. From the list, choose Group Policy then click add. In the Select Group Policy Object, click browse and choose default domain policy. Click Ok. This will load in the defaul domain group policy snap in.

With the default Domain Group Policy MMC open, in the left pane under console root, you should see "Default Domain Policy {your server.yourdomainname.XXX} Policy with computer configuration and User Configuration. Expand User Configuration.

by cg it

Expand Administrative Templates, expand control panel, expand display. In the right pane you will see "Policy" & "Settings" under which will be the different policies for display. If you want to enforce a screen saver, enable "Activate Screen Saver" AND Activate [configure] Screen Saver Executable Name". Both must be used. To ensure users cant change the policy, you can enable the Disable Display in the Control Panel, Hide settings Tab Hide Screen Saver Tab depending upon your policy regarding users ability to change display settings. Disable Display in Control Panel will remove users ability to run Display in the Control Panel. For an explanation of a policy, double click the policy , click on the explain tab.

by cg it

close the MMC snap in and save the Console settings.

Group Policy refresh interval is 90 minutes so workstation already logged on won't see the change immediately. Log off and reboot a logged on workstation for the policy to take effect.

This Configuration will apply to ALL Domain Users which is why you do this in a test environment. Once your verify that domain users who log in have this policy applied, you can go back and undo the changes to the default domain group policy. The create your OU, add users to that OU, create your Group Policy Object, then apply that to the OU. Verify that the desired configuration you want applies correctly to those users you want it applied to. Once you have successfully created you GPO and applied it to the OU{s} you want to have theses settings, you can then make the changes in the production environment.

by rfw63050

Thanks. We actually had found that it it does appear to be working as we desired. Thanks again!

This discussion is closed to new replies.