Microsoft KB Archive/246120
Article ID: 246120
Article Last Modified on 11/1/2006
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q246120
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
This article describes how to determine audit settings by checking the registry.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
For troubleshooting purposes, it may be useful to be able to determine the audit policy on a computer without using User Manager. This information is stored in the registry under:
NOTE: Administrators do not have access to this information by default. You must change the permissions on the registry keys.
This location contains a string of numbers, with the following format:
|A||Restart, Shutdown, System|
|B||Logons and Logoffs|
|C||File and Object Access|
|D||Use of User Rights|
|F||Security Policy Management|
|G||User and Group Management|
|Z||Determines if the policy is enabled or disabled.|
If any of the values (A,B,C,D,E,F,G) are set to 1, success auditing is enabled on those areas.
If any of the values (A,B,C,D,E,F,G) are set to 2, failure auditing is enabled on those areas.
If any of the values (A,B,C,D,E,F,G) are set to 3, both success and failures are audited on those areas.
If the value of Z is 1, the policy is enabled; if it is 0, auditing is disabled.
NOTE: You can have an audit policy (such as Audit Successful and Failed Logon Attempts), but have it disabled. You may also have an enabled audit policy that audits nothing.
Everything is Audited:
Nothing is audited (but auditing is enabled):
Keywords: kbenv kbhowto KB246120