Registry Tip #34: Enable user environment event logging in Windows 2000

Hits: Failed to execute CGI : Win32 Error Code = 3

To enable all available user environment event logging using Verbose mode without having to add a registry value for each component individually, add the following value:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Name: RunDiagnosticLoggingGlobal
Type: REG_DWORD
Value: 1

To enable verbose event logging for group policies only, add the following value:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Name: RunDiagnosticLoggingGroupPolicy
Type: REG_DWORD
Value: 1

To enable verbose event logging for remote boot only, add the following value:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Name: RunDiagnosticLoggingIntelliMirror
Type: REG_DWORD
Value: 1

To enable verbose event logging for application deployment only, add the following value:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Name: RunDiagnosticLoggingAppDeploy
Type: REG_DWORD
Value: 1





Keywords: Windows 2000 Registry Tip, tcp, tcpip, ip forwarding, routing