Troubleshooting Group Policy With Log Files

By Author: iris
Total Articles: 286
Comment this article

You can generate a diagnostic log to record detailed information about MCITP: Enterprise Administrator Group Policy processing to a log file named Userenv.log in the hidden folder %Systemroof/o\ Debug\Usermode. The generation of this diagnostic log is known as enabling verbose logging.
This section contains information about editing the registry. Using the Registry Editor incorrectly can cause serious damage to your operating system, so be very careful.
To enable verbose logging to a log file, complete the following steps:
1.Log on as Administrator.
2.Click Start, and then click Run.In the Run dialog box, in the Open box, type regedit, and then click OK.
4.In the Registry Editor console, open the HKEYJLOCALJVlACHINE/Software/Microsoft/Windows NT/Current Version/Winlogon key, then click Edit, selectNew, and then select DWORD Value on the toolbar.
5.In the details pane, type UserenvDebugLevel as the name of the new value.Right-click the new value and select Modify.
6.In the Edit DWORD Value dialog box, type 30002 in the Value Data box. Ensure that ...
... the Hexadecimal button is selected. Click OK.
7.Log off and then log on again.
Open the mcitp 2008 file and view the enhanced Group Policy event logging.
To read or copy the logs on the target machine, you must have local Administrator rights.
The Userenv.log file, shown in Figure 11-25, provides details of errors and warnings in Group Policy processing on the computer on which it is set. Reading from left to right, this log shows a process code, the time it was processed (the date is not displayed), the process name, followed by a short statement of the error. The Userenv.log file has a maximum size of 1 megabyte (MB). At system startup, if the log file exceeds 1 MB, the con?tents are copied into a file named Userenv.bak and a new Userenv.log file is created.
By using the application event log in Event Viewer, you can view Group Policy failure and warning messages. Event log records with the source Userenv indicate records pertaining to Group Policy events. You can retrieve more detailed information about Group Policy processing by enabling verbose logging for the event log.
You can generate a diagnostic log to record detailed information about Group Policy processing to a log file named Userenv.log in the hidden folder %5ystemroof%\Debug\User/mode. The generation of this diagnostic log is known as enabling verbose logging.
Recently, several publishing projects (stored in electronic format) were lost when an employee's laptop was stolen from a publishing convention. Previously, another employee lost important publishing project files during a fire sprinkler free exam question papers system incident in which the employee's computer was destroyed.