Re: OU GPO Corrupts 2003 Servers only??
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Thu, 6 Apr 2006 07:56:32 -0700
Thanks for the reply Andrew. That was quite different.
"andrewjtx" <ajohnson@xxxxxxxxxxxxxx> wrote in message
news:1144326446.700427.40670@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Roger, thanks for the reply.
I just resolved the issue last night.
The MS support rep from HP had pointed me in the direction of the
"Impersonate a client after Authentication" and "Create Global Objects"
property. I had set these in the GPO to Administrators only. I was
unaware that SERVICE was required to had this permission as well. I
tested it out on another OU, just setting these two to Administrators
and was able to recreate the problem. Then I repaired the test OU GPO
and rejoined the test server to the domain. Problem did not present
itself again.
This goes to show what screwing around with the security policy can do
for you. I'll be sure to read all of the details of each setting next
time I want to make a change...
.
- References:
- OU GPO Corrupts 2003 Servers only??
- From: ajohnson
- Re: OU GPO Corrupts 2003 Servers only??
- From: Roger Abell [MVP]
- Re: OU GPO Corrupts 2003 Servers only??
- From: andrewjtx
- OU GPO Corrupts 2003 Servers only??
- Prev by Date: Re: only apply on Terminal Server, but not on client (Notebook)
- Next by Date: Re: GPO for Remote Access
- Previous by thread: Re: OU GPO Corrupts 2003 Servers only??
- Next by thread: Folder (my docs) re-driection question?
- Index(es):
Relevant Pages
|
Loading