Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 301
  • Last Modified:

Group Policy deployed ScreenSaver

I created a screen saver and deployed it via Windows 2003 group policy.  All the computers are able to pull it over correctly.  But the computers are not idle and the screen saver is starting on the computers.  The idle time is setup for 300 seconds.  They will be typing into a program and it will just start the screen saver.  

Any ideas on what could be causing this?
0
atwist
Asked:
atwist
  • 6
  • 4
  • 2
1 Solution
 
BigC666Commented:
howdy,

on one machine check the local idle time, it may not be updated

hope that this helps
0
 
MSGeekCommented:
run gpresult on a workstation and let us know what you get back.. MSGeek
0
 
atwistAuthor Commented:
MSGeek - What value are you looking for?  It is getting the correct policies applied?
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
atwistAuthor Commented:
BigC666 - How would I check the idle time on a local machine?
0
 
BigC666Commented:
goto control panel->display->screensaver idle time is in the middle of the panel

hope that this helps
0
 
MSGeekCommented:
atwist..looking to see what policies are being appliedand in what order.
0
 
atwistAuthor Commented:
BIGC666 - didn't realize that is what you were asking.  That value is set to to the same as the group policy setting.
0
 
atwistAuthor Commented:
Well I found out today after switching the screen saver back to the scrolling marque included with windows that the problem no longer exists.  So how can a screen saver created cause the problem?  As windows controls the idle time not the screen saver.

msGeek - the local computer policy is applied first then the group policy.
0
 
MSGeekCommented:
Group Policies superceded LOcal Policies, there is no need to edit local seurity policies.  IF this custom screen saver is not local to the workstation that may cause your problem.  MSGeek
0
 
atwistAuthor Commented:
yeah the custom screen saver is on a network share.  I will try copying over to the individual computer and see what happens.
0
 
atwistAuthor Commented:
It looks like it works correctly now when the screensaver is on the individual computer.
0
 
MSGeekCommented:
atwist.. glad I could help.  Thanks, MSGeek.
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.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 6
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now