none
Loopback-replace

    Question

  • Group policy link order.

    If you have a GPO with only "loopback - replace" applied (it's a remote desktop server), along with 6 other GPO, applied to an OU, does the link order where the loopback policy is applied make a difference?

    For example:

    Applied Group Policy Objects
        -----------------------------
            Loopback - Replace
            Copy of User - Drive Mapping
            Copy of User - DFS Folder Redirection
            Copy of User - DFS Map User Folder
            Copy of User - Upload Drive (Z)
            Copy of User - Trust Local
            Default Domain Policy
            Local Group Policy

    -OR-

    Applied Group Policy Objects
        -----------------------------
            Copy of User - Drive Mapping
            Copy of User - DFS Folder Redirection
            Copy of User - DFS Map User Folder
            Copy of User - Upload Drive (Z)
            Copy of User - Trust Local
            Default Domain Policy
            Loopback - Replace
            Local Group Policy


    Thursday, July 14, 2016 8:18 PM

Answers

All replies

  • Hi,

    from my experience, it doesn't make a difference. As long as it is set somewhere along the way, loopback processing will take place.


    Evgenij Smirnov

    msg services ag, Berlin -> http://www.msg-services.de
    my personal blog (mostly German) -> http://it-pro-berlin.de
    Windows Server User Group, Berlin -> http://www.winsvr-berlin.de
    Mark Minasi Technical Forum, reloaded -> http://newforum.minasi.com

    In theory, there is no difference between theory and practice. In practice, there is.

    • Proposed as answer by DonPick Thursday, July 14, 2016 10:06 PM
    • Marked as answer by wwwillster07 Friday, July 15, 2016 7:14 PM
    Thursday, July 14, 2016 9:11 PM
  • Hi,

    I agree with Evgenij. Loopback does not care about the link order.

    By default, a user's policy settings come from the set of GPOs that are applied to the user object in Active Directory. During Group Policy processing on the client, the Group Policy engine assembles an ordered list of GPOs from the site, domain, and all organizational units for that user object.

    • Loopback with Replace—In the case of Loopback with Replace, the GPO list for the user is replaced in its entirety by the GPO list that is already obtained for the computer at computer startup (during step 2 in Group Policy processing and precedence). The User Configuration settings from this list are applied to the user.
    • Loopback with Merge—In the case of Loopback with Merge, the Group Policy object list is a concatenation. The default list of GPOs for the user object is obtained, as normal, but then the list of GPOs for the computer (obtained during computer startup) is appended to this list. Because the computer's GPOs are processed after the user's GPOs, they have precedence if any of the settings conflict.

    Loopback processing with merge or replace

    https://technet.microsoft.com/en-us/library/cc782810(v=ws.10).aspx

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 15, 2016 2:02 AM
    Moderator
  • > order where the loopback policy is applied make a difference?
     
    Some more info:
     
    Loopback is a computer setting, so it is applied during computer GPO
    processing.
     
    But it affects only (!) user GPO processing. Both are not related to or
    dependend on each other (although they are doing a similiar thing :-))
     
    > Applied Group Policy Objects
    >     -----------------------------
    >         Loopback - Replace
    >         Copy of User - Drive Mapping
     
    Impossible - if this is the computer part of RSoP, it will only list the
    "Loopback" GPO. If it is the user part, it will only list the "Drive
    Mapping" GPO.
     
    (Unless one of these GPOs contains settings in the other part, of course).
     
    Monday, July 18, 2016 1:27 PM