Microsoft's official enterprise support blog for AD DS and more
Mike here. Sometimes you need to enable additional logging when you are troubleshooting a particular component in Windows. Group Policy Preferences includes the ability to create verbose debug logging for each included client-side extensions. You activate Preference debug logging through Group Policy. Preference debug logging policy settings are located under the Computer Configuration\Policies\Administrative Templates\System\Group Policy node when editing a Group Policy object.
Figure 1 Group Policy Preferences debug logging
You can individually enable each preference client-side extension. Logging and tracing entries provide you with a several configuration options including what type of data to write to the event logs (Informational, Errors, Warnings, or all), enable trace logging and the location of the trace log file, and the size of the file.
Figure 2 Preference Logging and Tracing policy settings
You can configure the location of the trace files; however, keep in mind that file system permissions changed on Server 2008 and Windows Vista. Make sure permissions do not interfere with creating the log file. You'll notice the default location for all three log files is %COMMONAPPDATA%\GroupPolicy\Preference\Trace. The variable %COMMONAPPDATA% is not recognized by Windows, however; it is meaningful to Preference client-side extensions. Preference client-side extensions recognize this variable and expand it according to operating system on which the client-side extension is installed. For Windows Server 2003 and Windows XP, %COMMONAPPDATA% expands to %SYSTEMDRIVE%\Documents and Settings\All Users\Application Data. The equivalent path for Windows Server 2008 and Windows Vista is %SYSTEMDRIVE%\ProgramData (this folder is hidden by default, but you can manually type the path in Windows Explorer).
You've installed Windows Vista Service Pack 1; you've downloaded and installed RSAT. You try to enable Logging and tracing, but it's not there. Well, there is a reason for this.
Figure 3 Logging and tracing missing from RSAT
Administrative Templates show in the user interface because of two files: an .ADMX and an .ADML. Logging and tracing does not appear because the GroupPolicyPreferences.admx and .adml files are not included with RSAT. You need to copy these to your local or central store.
You have two options as to how to get a copy of the Group Policy Preferences ADMX files. You can download the entire Windows Server 2008 ADMX file set, or you can download just the Group Policy Preferences ADMX file set. You can download the installer for either of these file sets from http://www.microsoft.com/downloads/details.aspx?FamilyID=927fc7e3-853c-410a-acb5-9062c76142fa&DisplayLang=en. These MSI applications install their contents to the default location of %PROGRAMFILES%\Microsoft Group Policy.
The Group Policy Preferences ADMX installation creates an additional folder named Preferences, which contains a single ADMX file with multiple locale folders. You want to copy the GroupPolicyPreferences.admx file into your policydefinition folder. If you are using a central store, then you must copy the file to the policydefinition folder on SYSVOL, otherwise; copy the file to your local store. You'll then want to copy the .ADML file to the corresponding locale folder located in your policydefinition folder. See the Managing Group Policy ADMX Files Step-by-step guide for more information on managing ADMX Files and creating a central store. After you've copied both the .ADMX and .ADML file into the proper store, then close all instances of GPMC and its editor. Restart GPMC and edit the GPO in which you want to add Logging and tracing policy settings. Expand the nodes under Computer Configuration and you should now see Logging and Tracing options.
- Mike Stephens
PingBack from http://www.ditii.com/2008/07/21/group-policy-preferences-debug-logging-using-rsat/
Great stuff from the Directory Services team. This is very helpful information. Sure you can find some of this information online (in rather dry form), but visiting this blog is a great way to stay focused on what's new and cool in Active Directory.
You Had Me At EHLO... : Where does the time go? -519 Jet_errLogSequenceEnd Microsoft Advanced Windows
Can you explain to me why the default path is
while for e.g. this History Files produced by GPP are stored within a "Microdoft-Subfolder":
(but in turn missing the "Preferences" subfolder)
To me this is not consistent.
In general using a company named folder as "root" should be the preferred approach.
OK, I can change GPP log paths individually, but people like to chose the proposed default value...
Just because. When it comes to logging throughout the OS, you are going to see a lot of inconsistencies. That's because logging was not designed for you or me - it was designed for MS testers. Generally in a very quick and dirty fashion. In this case the logging just happened to get into the UI, which is pretty unusual in itself (I think it was like this in PolicyMaker, before MS even bought the company and developers that originally made this component), but there are no 'style guideliness' for logging. And once a default path is used, it really cannot ever be changed, as that will mess with too many people that assume paths will never change.
http://blogs.technet.com/askds/archive/2008/04/02/directory-services-debug-logging-primer.aspx <-- shows the inconsistencies to the Nth degree.