Re: User GPO not applying

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Florian,

You didn't confuse me, I started out that way! :-)

Thanks for the explanation! I'll play around with this and see if I can get
it working now. I'll be back if I run into difficulties.

Dave

"Florian Frommherz [MVP]" wrote:

Howdie Dave!

Dave schrieb:
When I run the Group Policy Modeling tool, it shows that this part of the
policy should be applied to that OU. However, when I run the Group Policy
Results tool, the Screen Saver settings do not show up and are not applied to
the computers in the Shared OU.

If you are saying that I can't apply this setting to the computers in this
OU in this way, then how can I set the Screen Saver options only for this OU?

Screensaver settings are under the "User Configuration" node, so they're
meant to trigger user objects in OUs of Active Directory. So when you're
creating a OU, put users into that OU and apply the screensaver policy
to it, you'll see the policy will get applied.

This is the default behavior of Group Policy application: "User
Configuration" settings will only be processed by user objects that are
in the OU (and SubOUs) you linked the policy to.

Pretty much the same way do "Computer configuration" settings behave -
they'll apply only to the computer objects that are in the OU (and
SubOUs) you linked the policy to.

That said, you've got two options from now:
(1) Put some user accounts into the OU you linked your screensaver
policy to. This would be recommended if you haven't organized your user
objects in AD and can move things around without breaking too much.

If you already have a static structure and want - for example - all
users who log on to those machines in the shared-OU to apply that
screensaver, you can use "Loopback Processing Mode". It is a Computer
Configuration policy which makes the computer objects in the OU "look
at" both the "Computer Configuration" settings configured for them as
well as the "User Configuration" settings that are enabled in their OUs
and SubOUs. Loopback helps you enforce a particular "User Configuration"
setting on certain machines for all users.

Somewhat clearer now? I'm sorry for confusing you. Feel free to post
back if you have any further questions.

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.

.

Relevant Pages

  • Re: Do Not Execute Group Policy for Admins Group
    ... The intent of policy loopback is to replace or merge user configuration ... The computer configuration settings from this list are applied to the ... > so that the group policy will only apply to a certain group of users ...
    (microsoft.public.win2000.group_policy)
  • Re: SBS 2003 GPO setting exclusion
    ... Workstations all need to support group policy preferences by OS and required ... Is that because it's a user configuration settings as opposed to a ... user configuration settings back onto the the computer as such.. ... setup a seperate Screensaver Policy? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 GPO setting exclusion
    ... Workstations all need to support group policy preferences by OS and required ... Is that because it's a user configuration settings as opposed to a ... setup a seperate Screensaver Policy? ... Created a new security group 'Screensaver Disabled' and added the ...
    (microsoft.public.windows.server.sbs)
  • Re: help with loopback gp verses ad group
    ... first gp will apply all settings to the computer and users, ... will reverse just the settings applied for the screensaver. ... >> loopback is for when one policy is overwriting another. ...
    (microsoft.public.windows.group_policy)
  • Re: GPO problems
    ... If policy loopback is set in the Computer Configuration of a GPO ... The computer configuration settings from this list are applied to the ...
    (microsoft.public.windows.group_policy)