group policy could not be updated

Microsoft Windows server 2008 r2 standar...
December 16, 2009 at 20:18:24
Specs: 2008 R2, 4ghz/3gb
When I look in the application log, I see errors
1030, 1035. When I try to run gpupdate from
one of the member servers. I get this error:

Windows cannot query for the list of Group
Policy objects. Check the event log for
possible messages previously logged by the
policy engine that describes the reason for
this.

When I run it from the DC, I get this error:

Updating Policy...

User policy could not be updated successfully.
The following errors were encountered:

The processing of Group Policy failed.
Windows attempted to retrieve new Group
Policy settings for this user or computer. Look
in the details tab for error code and
description. Windows will automatically retry
this operation at the next refresh cycle.
Computers joined to the domain must have
proper name resolution and network
connectivity to a domain controller for
discovery of new Group Policy objects and
settings. An event will be logged when Group
Policy is successful.

Computer policy could not be updated
successfully. The following errors were
encountered:

The processing of Group Policy failed.
Windows attempted to retrieve new Group
Policy settings for this user or computer. Look
in the details tab for error code and
description. Windows will automatically retry
this operation at the next refresh cycle.
Computers joined to the domain must have
proper name resolution and network
connectivity to a domain controller for
discovery of new Group Policy objects and
settings. An event will be logged when Group
Policy is successful.


To diagnose the failure, review the event log or
invoke gpmc.msc to access information about
Group Policy results.

The domain was renamed from acmedmz.local
to acmenadmz.local

Windows cannot connect to acmedmz.local
domain. (Server Down). Group Policy
processing aborted.

Thank you,

Leto the just


See More: group policy could not be updated

Report •


#1
January 6, 2010 at 09:05:05
The issue was an orphaned entry pointing to the previous domain
name.

Thank you,

Leto the just


Report •

#2
October 28, 2010 at 07:29:44
How did you find that entry? I have the same issue right now

Report •
Related Solutions


Ask Question