Re: Loopback GPO filtered to specific workstations.
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Thu, 27 Apr 2006 06:12:45 -0700
Using security group filtering with a group defining the machines that
should use this loopback policy does cause those machines to see in
the computer policies that they should use this policy for loopback
processing. What you have done to this point is fine.
But, then no user account ever pass the security group filtering and
so the loopback processing is never invoked.
You need to filter on both the machines that should do the loopback
processing with this GPO and the user accounts that should be subject
to the settings via the loopback processing.
"David Gould" <DavidGould@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AB83B0A9-A085-497F-9468-20F958ED8B7D@xxxxxxxxxxxxxxxx
Hi
I've been trying to get a loopback policy to work, but been struggling...
I've an OU that contains all workstations. I've created a GPO (linked to
the
OU) that contains a user configuration setting to disable the screen saver
with the loopback merge setting.
I've removed the 'Authenticated Users' groups and created a GPO filter
group
and added a couple of test machines to it. The idea being that if a user
logs
on to one of the test machines the screen saver is disabled - regardless
of
any screen saver settings applied to the user.
Problem is that it only appears to work (i.e. the machine screensaver
settings are applied) if I don't use the filter group, and leave it with
'Authenticated Users'.
Can someone tell me if a loopback GPO can be filtered, or provide any
suggestions as to what I might be doing wrong?
Appreciate any ideas.
Best Wishes
David.
.
- Prev by Date: Re: Can't change NTFS permission
- Next by Date: Group Policy Application
- Previous by thread: redirect favorites, start menu & personal folders
- Next by thread: Re: Loopback GPO filtered to specific workstations.
- Index(es):
Relevant Pages
|
