On Fri, Sep 11, 2009 at 1:21 PM, Sean Martin <[email protected]> wrote: > I have a couple of OUs containing Computer Objects that need > the same auto lock settings, except I don't want to disable > access to the screen saver settings.
Auto lock settings *are* the screen saver settings. How can you both need those auto lock settings, and not need them? If you're thinking you'd like auto-lock to be the default but allow users to override if they want, that's not how Group Policy works for... well, almost everything. GP generally makes a setting mandatory. For most things, there's no mechanism for the default vs mandatory distinction, unfortunately. On Fri, Sep 11, 2009 at 2:04 PM, Sean Martin <[email protected]> wrote: > My goal is to allow users (just technical staff) logging into > these specific servers the ability to disable the auto-lock > function entirely. You can apply the auto lock/screen saver settings to users rather than computers, and filter the technical staff out of that GPO, so that all other users will get the auto-lock settings. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
