Verbose logging tracks all changes and settings applied using Group Policy and its extension to the local computer and to users who log on to the computer. The log file is located at SystemDrive \Debug. This folder is a hidden folder. Enabling verbose logging involves adding the registry key for verbose logging. By performing the following steps, you can enable verbose logging for Group Policy and its extensions.
To enable verbose logging (Userenv.log)
Log on as the local administrator.
Click Start , and then click Run .
In the Open text box, type regedit , and then click OK .
Open the HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/Winlogon key, and then click Edit on the toolbar.
Click Add Value , and enter the value name UserenvDebugLevel .
Set the Data Type to REG_DWORD, click OK , and then under Value , enter the number 30002 . Set the option button to Hex .
Log off and then log on again.
30002 is for verbose logging, 30001 is for errors and warnings only, and 30000 logs nothing. The log will be found at %windir%\debug.
To enable verbose logging using a different method
Log on as local administrator.
Copy the file Envdebug.ini to the root of the system drive (C:\Temp)
Click Run , type Regini C:\envdebug.ini , and then click OK .
You must refer to Regini.exe in the path.
You can remove the registry key for verbose logging by taking the following steps.
To disable verbose logging
In a registry editor, navigate to the following registry subkey:
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/Winlogon
Delete UserenvDebugLevel entry.
Software Installation and Maintenance Logging
Follow the steps mentioned earlier to use Regedit to add the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Diagnostics\Appmgmtdebuglevel
Value: = 0xF (15)
Windows Installer Logging
Follow the steps listed earlier to use Regedit to add the following key:
REG_SZ = vicewarmup
REG_DWORD = 3
Do not use a registry editor to edit the registry directly unless you have no alternative. The registry editors bypass the standard safeguards provided by administrative tools. These safeguards prevent you from entering conflicting settings or settings that are likely to degrade performance or damage your system. Editing the registry directly can have serious, unexpected consequences that can prevent the system from starting and require that you reinstall Windows 2000. To configure or customize Windows 2000, use the programs in Control Panel or Microsoft Management Console (MMC) whenever possible.