From LedHed's Wiki
Jump to: navigation, search
m
 
(5 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
  <Domain>
 
  <Domain>
 
     │
 
     │
     ├───<Workstation OU>
+
     ├───<Computer OU>
 
     │        │     
 
     │        │     
     │        └─<span style="color:red">(GPO 1) = Computer Settings 1, User Settings 1)</span>
+
     │        └─<span style="color:red">(GPO 1) = Computer Settings 1, User Settings 1</span>
 
     │            │
 
     │            │
     │            └───────[LedHed-PC1]
+
     │            ├───[LedHed-PC1]
 +
    │            │
 +
    │            └───[Server]
 
     │             
 
     │             
 
     │
 
     │
 
     └───<User OU>
 
     └───<User OU>
 
             │  
 
             │  
             └─<span style="color:green">(GPO 2) = Computer Settings 1, User Settings 1)</span>
+
             └─<span style="color:green">(GPO 2) = Computer Settings 2, User Settings 2</span>
 
                   │
 
                   │
 
                   └───────[LedHed]
 
                   └───────[LedHed]
Line 42: Line 44:
 
<span style="color:red">Computer Settings 1</span><br>
 
<span style="color:red">Computer Settings 1</span><br>
 
<span style="color:green">User Settings 2</span><br>
 
<span style="color:green">User Settings 2</span><br>
 
  
  
 
== Loopback Processing ==
 
== Loopback Processing ==
Loopback Processing changes the default behavior described above.
+
Loopback Processing changes the default behavior described above.<br>
 +
There are two modes '''''Replace''''' and '''''Merge'''''<br>
 +
=== Replace Mode===
 +
With Loopback Processing enabled in REPLACE mode, when User [LedHed] logs on to Computer [LedHed-PC1] the following GPO settings are applied:<br>
 +
<span style="color:red">Computer Settings 1</span><br>
 +
<span style="color:red">User Settings 1</span><br>
 +
As you can see <span style="color:red">User Settings 1</span> replaced <span style="color:green">User Settings 2</span>
 +
 
 +
=== Merge Mode ===
 +
With Loopback Processing enabled in MERGE mode, when User [LedHed] logs on to Computer [LedHed-PC1] the following GPO settings are applied:<br>
 +
<span style="color:red">Computer Settings 1</span><br>
 +
<span style="color:red">User Settings 1</span><br>
 +
<span style="color:green">User Settings 2</span><br>
 +
 
 +
In this mode both <span style="color:red">User Settings 1</span> and <span style="color:green">User Settings 2</span> are applied, but if there is a conflict between these policies, then <span style="color:red">User Settings 1</span> takes priority.

Latest revision as of 01:29, 2 February 2013

Overview

Group Policy Example

<Domain>
   │
   ├───<Computer OU>
   │        │    
   │        └─(GPO 1) = Computer Settings 1, User Settings 1
   │             │
   │             ├───[LedHed-PC1]
   │             │
   │             └───[Server]
   │             
   │
   └───<User OU>
            │ 
            └─(GPO 2) = Computer Settings 2, User Settings 2
                 │
                 └───────[LedHed]

Legend

Name Object Type
[LedHed-PC1] Computer
[LedHed] User


Standard Group Policy Processing

In the above example there are two Group Policy Objects (GPO).

GPO 1
GPO 2

Each GPO has two settings, Computer and User.

Group Policy applies Computer Settings to Computer Objects and User Settings to User Objects.

Under normal circumstances when the User [LedHed] logs on to Computer [LedHed-PC1] the following GPO settings are applied:
Computer Settings 1
User Settings 2


Loopback Processing

Loopback Processing changes the default behavior described above.
There are two modes Replace and Merge

Replace Mode

With Loopback Processing enabled in REPLACE mode, when User [LedHed] logs on to Computer [LedHed-PC1] the following GPO settings are applied:
Computer Settings 1
User Settings 1
As you can see User Settings 1 replaced User Settings 2

Merge Mode

With Loopback Processing enabled in MERGE mode, when User [LedHed] logs on to Computer [LedHed-PC1] the following GPO settings are applied:
Computer Settings 1
User Settings 1
User Settings 2

In this mode both User Settings 1 and User Settings 2 are applied, but if there is a conflict between these policies, then User Settings 1 takes priority.