Group policy errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Barry (anonymous_at_discussions.microsoft.com)
Date: 03/11/04 

Date: Thu, 11 Mar 2004 15:56:22 -0800

Hello,

I have some Windows XP Pro machines on our SBS company
network that are giving me group policy errors in the
event log:

They appear from either the logged in user or SYSTEM,
with the source as USERENV and Event ID's of 1005 and
1030, which always appear at the same time. Other
associated errors that appear are 1006 and 1053.

1005 is "Windows cannot connect to XYZ.local domain
(Operations Error). Group Policy processing aborted."

1030 is "Windows cannot query for the list of Group
Policy objects. A message that describes the reason for
this was previously logged by the policy engine."

1006 is "Windows cannot bind to XYZ.local domain.
(Timeout). Group Policy processing aborted."

1053 is "Windows cannot determine the user or computer
name. (An internal error occurred. ). Group Policy
processing aborted."

No Windows 2000 machines are affected. The difference
between the Windows XP machines with these errors and the
ones that don't seems to be the installation date - any
new machines (or one that I reformatted and reloaded)
since December last year do not have the problem.

This problem has existed while each of the machines was
connected to our old Windows 2000 SBS server. Three weeks
ago, we installed a new domain server with Windows
2003SBS. We did a complete new installation with no
promote/demote of domain controllers as it is now on a
new Domain name. Each machine was removed from the old
domain and connected to the new one. However, despite the
change of domain the problem on each XP machine still
exists.

>From this I would conclude that some 'mini disaster' on
the old server/network happened prior to December last
year that screwed up how each computer accesses the
active directory on the server. With the change of
server, whatever is causing this problem has remained.
Despite this, all the affected machines seem to work OK
on the network, apart from not applying any group policy
changes.

Besides reloading all the affected machines (about 6),
what else can I do?

If you need more information please ask.

Thanks

Relevant Pages