How To Prevent Auditable Activities When Security Log Is FullLast reviewed: December 9, 1997Article ID: Q140058 |
3.50 3.51
WINDOWS
kbother
The information in this article applies to:
SUMMARYBecause the security log is limited in size, and because a large number of routine audit records can make it difficult to find records that suggest a security problem, you should carefully consider how you audit object access. Generating too many audit records require you to review and clear the security log more often that is practical.
MORE INFORMATIONWARNING: Using Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. If you have set the security log either to "Overwrite Events Older than n Days" or "Do Not Overwrite Events (Clear Log Manually)", you may want to prevent auditable activities while the log is full so no new audit records can be written. To do this:
To recover when windows nt halts because it cannot generate an audit event record:
|
KBCategory: kbother
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |