|
Home > Archive > 70-217 > November 2002 > Loopback processing order exceptions
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Loopback processing order exceptions
|
|
| me? I dunno... 2002-11-25, 1:14 am |
| I don't really understand the particulars of either the merge or Replace options for this setting.
does anybody have an explanation in their own words for the scenario's that would result in either of these options being used? | |
|
| quote:
Originally posted by me? I dunno...
I don't really understand the particulars of either the merge or Replace options for this setting.
does anybody have an explanation in their own words for the scenario's that would result in either of these options being used?
 
explain please....... | |
| me? I dunno... 2002-11-25, 3:01 am |
| Page 403, MOC 70-217training kit.
It says that these settings would be of use at kiosks, laboratories etc, but really doesn't go into the particulars of what difference they make, and the merge and replace modes they talk about are not explained sufficiently for me to understand.
What are the modified processing orders?
Is this a tool to further secure the workstation, or a convenience for users? | |
| jeff_j_black 2002-11-26, 5:45 pm |
| From: http://support.microsoft.com/defaul...kb;en-us;231287
Merge Mode:
In this mode, when the user logs on, the user's list of GPOs is gathered normally by using the GetGPOList function. The GetGPOList function is then called again, using the computer's location in Active Directory. The list of GPOs for the computer is then added to the end of the GPOs for the user. This causes the computer's GPOs to have higher precedence than the user's GPOs. In this example, the list of GPOs for the computer is added to the user's list.
Replace Mode:
In this mode, the user's list of GPOs is not gathered. Only the list of GPOs based on the computer object is used.
Merge basically loads defined user settings, then loads the computer settings, merging them. Computer settings are applied last to they would win out in case of conflicting settings.
Replace mode bypasses loading user settings.
Remember that computer policy is applied when the computer starts up, user policy is applied when the user logs on. The loopback processing re-applies the computer policy after the user logs on.
The kiosk example is not the best to ponder. Think about logging on to a terminal server. On a terminal server you want the users to only see particular programs and resources, regardless of what policy is being applied to the user, so the loopback would enforce the computer policy after the user logs on. Merge would allow some user settings to be processed, but enforce all computer settings. Replace would bypass any user settings entirely and enforce computer settings. | |
| me? I dunno... 2002-11-26, 11:46 pm |
| Makes sense |
|
|
|
|