GPO to automatically lock system

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

We rolled out a GPO to automatically lock systems after 15 minutes of idle
time. For the most part, this worked perfectly. However, we did run into a
few snags.

There are some systems where users log in to give presentations. Since this
GPO is tied to users, the policy kicks in and they have to unlock the system.
This is giving them fits.

Has anyone found a way to make this a computer setting rather than a user
setting? It would make it much easier since I could just assign deny
read/deny apply to the computer account.

Any info would be helpful.

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

You could apply loopback processing to those computers in a separate OU with
screen saver lockout disabled in the Group Policy for that OU. Loopback
processing applies the user configuration for the Group Policy that the
computer is in via either replace or merge with usual user configuration
settings. The links below will help. --- Steve

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/abe2b1a9-975f-4b2f-b771-9e6a903e97db.mspx
http://support.microsoft.com/default.aspx?scid=kb;en-us;231287

"The Frustrated Monk" <TheFrustratedMonk@discussions.microsoft.com> wrote in
message news:9FD03FCC-591B-497C-B3A8-C2A81C466C1A@microsoft.com...
> We rolled out a GPO to automatically lock systems after 15 minutes of idle
> time. For the most part, this worked perfectly. However, we did run into a
> few snags.
>
> There are some systems where users log in to give presentations. Since
> this
> GPO is tied to users, the policy kicks in and they have to unlock the
> system.
> This is giving them fits.
>
> Has anyone found a way to make this a computer setting rather than a user
> setting? It would make it much easier since I could just assign deny
> read/deny apply to the computer account.
>
> Any info would be helpful.