Show Verbose Security Status Messages (Windows 2000/XP)
This setting allows you to configure Windows so that you receive verbose startup, shutdown, logon, and logoff status messages. This may be helpful to in troubleshooting slow startup, shutdown, logon, or logoff behaviour.
User Environment Event Logging (Windows 2000/XP)
These settings can be used to selectively enable the user environment event logging features available in Windows.
Windows Installer Logging (All Windows)
Windows Installer can use logging to help assist in troubleshooting issues with installing software packages. You can enable verbose logging with this setting.
User Environment Debug Logging (Windows 2000/XP)
This setting enables debug logging of user profile and system policy processes which may be helpful in troubleshooting problems.
Create a Oakley Log for IPSec Troubleshooting (Windows 2000)
Enabling this setting causes Windows to create an Oakley.log file in the %SystemRoot%\debug folder for developers or network administrators with advanced IKE knowledge.
Change the Number of SQL Server Error Logs (Windows NT/2000/XP)
By default, Microsoft SQL Server 7.0 only stores seven error logs; Errorlog and Errorlog.1 through Errorlog.6. Since the log is re-created every time SQL Server is restarted you may want to keep more than seven logs archived.
Restrict Access to the Event Logs (Windows NT/2000/XP)
The Windows event log contains records documenting application, security and system events taking place on the machine. As these logs can contain sensitive data this tweak allows you to restrict access to administrators and system accounts only.
Remote Access Service (RAS) PPP Logging (Windows NT/2000)
Creates a file called PPP.LOG in the %SYSTEMROOT%\SYSTEM32\RAS folder to help diagnose connectivity problems between a PPP server and a PPP client when one of the computers is a Windows NT Remote Access Service client.
Remote Access Service (RAS) Device Logging (Windows NT/2000)
Creates a file called DEVICE.LOG in the %SYSTEMROOT%\SYSTEM32\RAS folder for information about commands that the modem is sending and errors that are reported. This file can be very useful in debugging RAS failures.
Logging