none
Screen Saver GPO doesn't work on random machines

    Question

  • Short version:

    If the .SCR file is there and it looks like the GPO is applied, why do some computers not run the specified screen saver?

    Long version:

    I've got a not-your-normal screen saver situation. I normally set the screen saver on my client computers via a GPO applied to my domain.  Maybe it works on all of them. I don't know, but no one complains.

    During the holiday, we rollout a holiday screen saver, but only to computers in our HQ - because these are the only people that will likely be attending the company holiday party.  For this, I deploy the .SCR file via SCCM and then apply another GPO to the two computer OUs for the HQ office.  It works on most computers, but I've got other that don't get the holiday screen saver.  NOW the users care about their screen saver (or lack there of). 

    I've checked a number of these computers.  They have the .SCR file in System32 (SysWOW64 on 64-bit computers).  RSOP shows that the settings are being applied via GPO.  Still no holiday screen saver.

    I went so far as to check scrfile in the Registry to verify that Windows knows what to do with a .SCR file - AutoCAD changes the .SCR association. 

    My problem is further compounded by shrugs I get when I ask the affected users if the normal corporate screen saver worked before.

    Monday, November 30, 2015 5:01 PM

Answers

  • I'm doing loopback processing so I can assign this GPO to users.

    I've resolved my issue.

    After canvassing users, I discovered that while the screen saver does execute on 64-bit machines, my problem computers seem to be exclusively 64-bit systems.  I abandoned storing the screen saver in the 32-bit system folder and created a ScreenSaver folder under Windows and modified my group policy.

    Now I'm hearing from users that the screen saver is running on their computer.  Some of them are reporting that now that they think about it, they've never had a screen saver.

    If the 64-bit systems where confused about the path, I don't understand why they weren't all confused.  In any event, I've copied the normal corporate screen saver to the ScreenSaver folder and will update the GPO when it's time to take the holiday screen saver down.

    • Marked as answer by JT65 Thursday, December 3, 2015 4:15 PM
    Thursday, December 3, 2015 4:14 PM

All replies

  • For this, I deploy the .SCR file via SCCM and then apply another GPO to the two computer OUs for the HQ office.

    How exactly did configure this? Screen saver setting is a user-based policy setting, you should apply the GPO to user object instead of computer object.
     
    What happens if the user logs on to another machine? And what happens if a different user logs on to the faulty machine?
     

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Wednesday, December 2, 2015 3:21 AM
    Moderator
  • I'm doing loopback processing so I can assign this GPO to users.

    I've resolved my issue.

    After canvassing users, I discovered that while the screen saver does execute on 64-bit machines, my problem computers seem to be exclusively 64-bit systems.  I abandoned storing the screen saver in the 32-bit system folder and created a ScreenSaver folder under Windows and modified my group policy.

    Now I'm hearing from users that the screen saver is running on their computer.  Some of them are reporting that now that they think about it, they've never had a screen saver.

    If the 64-bit systems where confused about the path, I don't understand why they weren't all confused.  In any event, I've copied the normal corporate screen saver to the ScreenSaver folder and will update the GPO when it's time to take the holiday screen saver down.

    • Marked as answer by JT65 Thursday, December 3, 2015 4:15 PM
    Thursday, December 3, 2015 4:14 PM