Jef-
I
don't know if it helps but the flags (145) thing means the
following:
Machine Policy is being applied as opposed to user
policy
This
policy is being applied as a background refresh (rather than
foreground)
No
changes were detected to the GPO during this processing cycle (so nothing was
applied)
The
failure status code is just a Win32 error code, which in this case means, "An
extended error has occurred."-- Not very helpful.
Are
you seeing other problems in terms of policy application other than these
errors? How often do these errors occur?
Darren
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 10:41 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Secedit Errors
Hello all,
I am getting repeated secedit errors which seem to be due to a corrupted secedit.sdb file on the DCs. After using ESENTUTL to repair the DB, and group policy applies correctly.
A day or so later, those that were repaired now have the same errors. Anyone have any idea where to halt this cycle? What am I missing?
Source: Userenv
Name: Unexpected Error applying group policy to machine account
Description: The Group Policy client-side extension Security was passed flags (145) and returned a failure status code of (1208).
There were originally some group policy errors, which were fixed. Policy applies correct as per the winlogon.log after it is fixed, but the problem returns.
any help would be appreciated.
Jef Kazimer
