Re: Group Policy loopback processing mode - ???

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Me (z_at_z.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 09:28:45 -0700

NICE! I do in fact have a couple of uses for it! Thanks!

On Mon, 20 Sep 2004 13:14:49 +1000, "Mark Renoden [MSFT]"
<markreno@online.microsoft.com> wrote:

>Hi
>
>Policy loopback is used when you want to change the User Configuration
>settings that would normally apply to a user (based on their location in the
>AD - OU heirarchy) when they are logged onto certain computers. A good
>example of this is Terminal Servers. You might want one set of User
>Configuration settings to apply when a user is at a generic workstation, but
>a different list of settings when they're in a Terminal Server session.
>
>To clarify how policy loopback works:
>
>1. When the computer boots, the list of GPO's for the computer is gathered
>based on it's location in the Active Directory. This is it's SOM or Scope
>of Management. The list includes GPO's linked to OU's at each level in the
>heirarchy from the OU in which the computer resides all the way up to the
>domain.
>
>2. The computer configuration settings from this list are applied to the
>computer provided it has permissions to the GPO's.
>
>3. When the user logs in, different behaviour occurs according to the policy
>loopback settings:
>
>A. Loopback off - the SOM for the user is calculated and then user
>configuration settings applied according to user permissions. The location
>of the user account in the AD decides entirely which user configuration
>settings are applied.
>
>B. Loopback merge mode - the SOM for the user is calculated as in A. The
>user configuration settings from this SOM are applied but at a lower
>precedence to the user configuration settings in the computer SOM. Once
>again, user permissions allow or prevent application of these setting
>regardless of whether they came from the user or computer SOM.
>
>C. Loopback replace mode - the SOM for the user is not considered. The user
>configuration settings are applied from the GPO's in the computer SOM
>provided they have user permissions.
>
>Kind regards

Relevant Pages

  • Re: Loopback issues
    ... To explain loopback: ... This is it's SOM or Scope ... The computer configuration settings from this list are applied to the ... >> 1 GPO applied, with Loopback Processing enabled and set to replace.SUS ...
    (microsoft.public.windows.group_policy)
  • Re: Loopback Processing
    ... As long as loopback is set in one GPO, ... why does it still apply the User Configuration settings. ... it's SOM or Scope ...
    (microsoft.public.windows.group_policy)
  • Re: Group Policies Examples
    ... A good document with examples of group policy implementations can be found ... Policy loopback works as follows: ... This is it's SOM or Scope ... The computer configuration settings from this list are applied to the ...
    (microsoft.public.win2000.group_policy)
  • Re: GPO Loopback
    ... Loopback is used in any situation where you would like the user ... >> Configuration settings on a per-machine basis. ... >> SOM or Scope of Management. ... >> configuration settings applied according to user permissions. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Loopback Processing and Deny Apply in ACL
    ... get applied at logon in regards to loopback policy's and setting the deny ... > To clarify how policy loopback works: ... This is it's SOM or Scope ... The computer configuration settings from this list are applied to the ...
    (microsoft.public.win2000.group_policy)