Wednesday 5 February 2014

How to apply screen saver through group policy in Active directory 2008 R2 Domain

Applying screen saver is an easy task you only have to apply the following steps.

Please be care full that your screen saver file is not a big one as it may chock your network if it have a big size and users system start to download at the same time.

(1) You have to create your screen saver *.scr file (DomainScreensaver.scr). you need tool to create .scr file.
now place this "DomainScreensaver.scr"  in a folder like "\\servername\foldername" share it. on sharing tab add everyone and give read permission.
on security tab add everyone and give (read and execute, list folder contents, read) permissions.
 
(2) You also have to create your logon script so while a user logging to his/her system the screen saver file (DomainScreensaver.scr) will be downloaded to user system. For which you have to create the .bat file

How? (open notepad file and type
 
md "C:\ScreenSaver"
 and save this file as Screensaverphoto.bat

It will download the content(DomainScreen saver.scr) from share location i.e \\servername\foldername to user’s system C:\screensaver.

 (3) share the folder (\\servername\foldername) which contain the screen saver(Screensaverphoto.bat) and give read rights to everyone on this folder.
 

Now you are going to create/configure GPO, So follow these steps
(1) Start à Group Policy Management.

(2) Create a group policy “SS Client”.

(3) Right click on it and select Edit.

(4) Go to user configuration windows settings à Scripts (Logon/logoff)

(5) Double click on logon à show files—go to screensaverphoto.bat file location.

New kept this location/folder ( \\domain.com\sysVol\domain.com\{FD692A-----}\User\Scripts\Logon )   open.
(6)
Go to the location where you have created “screensaverphoto.bat” file and right click on this file and select copy. now close this folder and go above location (mentioned in step 5) and past it there (\\domain.com\sysVol\domain.com\{FD692A-----}\User\Scripts\Logon )
(7) Now go to Logon properties window and click on Add button

And select the “Screensaverphoto.bat” file.
And click OK.

(8) Now go to User configuration à Administrative templates

Control panel à Personalization

(a) Click on Enable Screen Saver and select Enabled.
 
(b) Click on Password protect the screen saver and select Enabled.

(c) Click on Screen saver timeout select Enabled and mention time like seconds 90 etc.

(d) Click Force Specific screen saver C:\screensaver\DomainScreensaver.scr (it will copy screensaver on this location on client system)

Now your GPO is ready, so you need to apply it.
Go to the desired OU in Group policy management and right on that OU.
select link an existing GPO and select "SS Client" GPO and click OK.
you can also enforce etc.

And that's it. Done

Troubleshooting.
you can check on any client screen saver is not applying.
(1) you can use GPresult /r to check that the GPO is applied or not
(2) you can use rsop.msc to check that which settings are applied on your client system.
(3) to check that the screen saver file is downloaded to client system or not go to location (C:\screensaver) that screen saver file is downloaded or not.
(4) you can run the command (xcopy \\servername\foldername\ C:\ScreenSaver) that it is working fine or not.
(5) Command GPresult with different switches will also help to troubleshoot
(6) if you have accessed a system with RDP, then you may be unable to see the Screen saver. So will be better to check on a system on which you have logged in locally. 

2 comments:

  1. Nawaz

    This is a great guide and thanks for putting it together. I followed your guide and i encountered a challenge at the end, my scr doesn't run. The folder is created on the local drive on clients and i know what you are thinking my .scr!! However the .scr can execute if user intervenes(i.e play). What do you think i may have missed, given i followed your guide to the the letter

    ReplyDelete
    Replies
    1. Thanks Mzatz, its good that it helped you at some point. some time you would face this issue but on some clients not on all clients. you would have different clients (Windows 7, 8, 10. so you are facing this issue on all OS?, or on specific?.

      Delete