"Michael D. Alligood [CertGuard, Inc.]" <> wrote in
message news:...
> "John R" <jsr^^^813@zoom^^^internet.net> wrote in message
> news:#:
>
> You just take the fun out of everything.
Sorry, Michael, but I really do agree with the OP, and I have seen it
documented both ways as he stated. And I agree with your post as well, I
was not trying to disagree with you.
I forget who was asked if they wear boxers or briefs, and they answered
'depends'. That caused a good laugh because the answer was taken
differently than it was intended. I have found that the same situation
applies to this OPs question. IMHO, you have to look at the setting itself,
what the setting applies to, and then of course take loopback processing
into account. If the setting is to a service, or sometimes even to an
application, if that application or service starts up prior to a user logon,
it will be the computer configuration that will take priority unless it is a
registry setting that the application queries periodically like a SAV or
ForeFront Client Security registry setting, unless loopback processing is
specfied in replace or merge mode, unless, unless, unless. The fact that MS
even designed a loopback feature to allow for the computer configuration
settings to override the user settings would indicate that it is the user
settings that take precedence, but that isn't always necessary.
That is what I found in my testing. I was thoroughly confused on this
subject and actually spent about three weeks just changing two different
gpos, rebooting, running RSoP, etc, until I came to the answer 'depends'. I
don't remember if I was asked any questions on the test about conflicts, but
I do know that I was asked about loopback processing.
Fortunately, our organization uses GPOs sparingly, and almost all GPOs have
only user or computer settings, not both. RSoP is really the best tool to
test with prior to assigning a GPO to a production OU, and I use that
extensively.
John R