Have you tried "gpupdate.exe /force" and "gpresult.exe
/scope computer /v" and looked at what's really happening?
Roger SeielstadE-mail Geek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Schmieder,
MarcSent: Wednesday, April 06, 2005 8:13 AMTo:
Ac
]
[mailto:[EMAIL PROTECTED] On Behalf Of Schmieder,
MarcSent: Wednesday, April 06, 2005 12:19 PMTo:
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Audit Policies
are not applying in windows 2000
Darren,
Thank you very much for
the suggestions. Unfortunately everything checked out with the DB
: Wednesday, April 06, 2005
11:33 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Audit
Policies are not applying in windows 2000
You could have a corrupt local secedit.sdb
database on these machines, which would prevent the policy from being applied
correctly. This file is typically
You could have a corrupt local secedit.sdb database on
these machines, which would prevent the policy from being applied correctly.
This file is typically stored on c:\windows\security\database. You can run the
following command on one of these machines to check its integrity.
esentutl /g
