G
Guest
We tried some of the Audit Events with our Windows 2000 Small Business
Server. For the Domain Controller Security Policy, and Domain Security
Policy, we defined the Audit Logon Events and Audit Object Access.
Audit Logon Events
We tried auditing both Success and Failure attempts last Thu, but on Fri we
changed to audit the Failure attempts only. But we don't understand why till
now, Success attempts are still logged. Why is it so?
Audit Object Access
We defined this with the intention to keep track of the personnel who
changed the files in a specific folder. If this is not defined, the changes
are not logged. But with this defined (as we audit both Success and Failure
attempts), there are so many unrelated events logged. Our primary goal is
only to monitor changes in one folder. What can we do to achieve this?
And now, after defining only 2 events, log files of the client PCs become
full every day. And administrators have to login to clear them, otherwise
users cannot login. What should we do?
Server. For the Domain Controller Security Policy, and Domain Security
Policy, we defined the Audit Logon Events and Audit Object Access.
Audit Logon Events
We tried auditing both Success and Failure attempts last Thu, but on Fri we
changed to audit the Failure attempts only. But we don't understand why till
now, Success attempts are still logged. Why is it so?
Audit Object Access
We defined this with the intention to keep track of the personnel who
changed the files in a specific folder. If this is not defined, the changes
are not logged. But with this defined (as we audit both Success and Failure
attempts), there are so many unrelated events logged. Our primary goal is
only to monitor changes in one folder. What can we do to achieve this?
And now, after defining only 2 events, log files of the client PCs become
full every day. And administrators have to login to clear them, otherwise
users cannot login. What should we do?