Re: GPO for user not applied
- From: "Uffe" <uffe@xxxxxxxxxxxxxxxx>
- Date: Thu, 22 Mar 2007 14:08:17 +0100
Hi,
That was the problem, Authenticated users lacked read permissions on the OU where the user object is.
Thanks for your help Mike
Kind Regards,
Uffe
"Mike Luo [MSFT]" <v-miluo@xxxxxxxxxxxxxxxxxxxx> wrote in message news:ifdP5TEbHHA.296@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I checked the userenv.log file and found "GetUserNameEx failed with 1317".
This message means that the user can't be determined and apply GPOs.
This may be caused the Authenticated Users group having no permissions on
the container including users and computers, please check the domain, OU,
computers, make sure that Authenticated Users group has read permission.
Thanks & Regards,
Mike Luo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: GPO for user not applied
- From: Mike Luo [MSFT]
- Re: GPO for user not applied
- References:
- GPO for user not applied
- From: Uffe
- Re: GPO for user not applied
- From: Florian Frommherz
- Re: GPO for user not applied
- From: Uffe
- Re: GPO for user not applied
- From: Mike Luo [MSFT]
- Re: GPO for user not applied
- From: Uffe
- Re: GPO for user not applied
- From: Uffe
- Re: GPO for user not applied
- From: Mike Luo [MSFT]
- Re: GPO for user not applied
- From: Uffe
- Re: GPO for user not applied
- From: Mike Luo [MSFT]
- GPO for user not applied
- Prev by Date: RE: Desktop Standard Policymaker and W2K3 SP2?
- Next by Date: Re: Desktop Standard Policymaker and W2K3 SP2?
- Previous by thread: Re: GPO for user not applied
- Next by thread: Re: GPO for user not applied
- Index(es):
Relevant Pages
|