I have read the article already its really more of a confirmation that the above is either right or wrong that i was looking for
Main Topics
Browse All TopicsI have looked into loopback policy mode and found the below posting, am I correct in saying enabling loopback policy mode is really nothing more than telling a user policy that if it encounters a computer policy in place on any machine that the computers settings should replace the user settings if "replace mode" mode is seltected and merge the settings when "merge mode" is selected allowing the machine to win over user settings if a conflict occurs. All corrections are welcome !!
An example of loopback processing will be
you are in a school environment and you have a Math classroom with 20 computers in its own ou,
but you do not want any users who login to these machines to be able to run the calculator program.
That policy is found under the USER section here User Config > Administrative templates > system > 'don't run specified applications'
If we were to set this policy just as a normal user policy and apply it to an OU with the students in it then no matter what computer the students log into they will receive this policy and cannot run the calculator program.
Instead you set the user policy section as described above and then in the computer section you set the loopback policy and apply the
GPO to the OU that the computers are in.
Then the users who login to this classroom will receive this User Policy setting and
when a user logs into another computer in a different OU they can still run the calc program
you apply the GPO to an ou with computers in it
and it tells all users who login to these computers to apply the user settings that are defined in the same policy
you use loopback processing mode when you want to apply a user setting
to all users who login only to a specific set of computers
sorry...that took longer to say than expected, hope it didn't add to the confusion
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Your understanding of Loopback processing is not correct.
User Configuration policies and Computer Configuration have nothing to do with each other, and this behavior isn't changed with the Loopback policy.
A user configuration policy is normally only applied to *user* objects in or below the OU to which the GPO is linked. Since this user object is always the same, it would be impossible to have different *user* policies depending on the *computer* the user is logging on to. Applying the Loopback policy to a computer makes this possible.
As soon as the Loopback policy is applied to a computer, *user* policies applied to this *computer* object will be applied to users logging on to this machine. The mode in which the Loopback policy is configured determines what happens with the "normal" user policies coming from the *user* *object* in AD. In Replace mode, the user object policies are discarded. In Merge mode, the user object policies are applied first, then the loopback user policies are applied (so the "looped back" user policies applied to the computer object have priority if they conflict).
Loopback processing of Group Policy
http://support.microsoft.c
fm250,
there is no "general precedence" when it comes to user and computer policies. User settings are written to HKCU, computer settings are written to HKLM, and it is *ONLY* the application evaluating the registry keys that decides whether it will look only in HKLM, only in HKCU, or in both, and which setting has priority in case of a conflict.
A typical scenario where loopback is required is a terminal server environment. For example, when the user logs on to his normal desktop, he should have relatively few restrictions, but when logging on to a terminal server, more restrictions need to be imposed. Most of these restrictions are user based, so with regular GPO processing in place, no matter where the user will log on, he will always receive the exact same set of user policies, because it's always the same user object at the same AD location with the same GPOs applied. Applying user policies to the terminal server OU at this point will have no effect, because the user object is not in or below this OU.
By enabling the loopback processing mode on a terminal server, *user* configuration policies applied to the computer object will now be processed when a user is logging on to a terminal server, even if the user object is NOT in the terminal server OU.
See the simplified AD structure below.
SomeUser will will always receive the GPO USER-StandardDesktop, because it is linked to the OU with his object in it.
WITHOUT the GPO COMPUTER-Loopback applied to the terminal server OU, the GPO USER-Terminalserver-Restri
WITH the GPO COMPUTER-Loopback applied, the GPO USER-Terminalserver-Restri
Business Accounts
Answer for Membership
by: fm250Posted on 2009-06-04 at 15:44:52ID: 24552089
Look this link, it might help. note that I have noticed when applying gp it sometimes takes a while to apply even if you update. hope this helps:
http://grouppolicy.editme. com/Loopba ck