Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Software installation can provide a detailed log that you can use to troubleshoot Group Policy issues.
Software Installation CSE logging, by default, is set to only log errors. To avoid using unnecessary disk space, you should leave software installation logging at the default setting. You can enable software installation logging to gather verbose troubleshooting information when investigating software installation errors on a client computer.
Warning
This section 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, see Description of the Microsoft Windows Registry on the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=35500).
To enable software installation logging on the client computer
Log on to the administration computer as the administrator.
Click Start, Run, and then run Regedit to add the following registry value (or modify it, if the value already exists):
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Enter the following:
Value: AppmgmtDebugLevel
Value Type: REG_DWORD
Value Data: 9B (Hexadecimal)
FdeployDebugLevel can have the following values:
NORMAL 0x00000000
VERBOSE 0x0000009B
The default value is NORMAL (0x00000000).
The log file can be found at: %Systemroot%\debug\usermode\appmgmt.log.