Microsoft KB Archive/931066

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:36, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


How to enable tracing for client-side extensions in PolicyMaker

Article ID: 931066

Article Last Modified on 5/24/2007



APPLIES TO

  • PolicyMaker Standard Edition 2.0
  • PolicyMaker Standard Edition 1.0



INTRODUCTION

By default, tracing for DesktopStandard PolicyMaker Standard Edition client-side extensions (CSEs) is disabled. You can enable tracing by using the administrative template that DesktopStandard provides.

By using this administrative template, you can customize tracing and other options for each CSE independently. The tracing function provides detailed output for each CSE in a plain text format. You can use the trace output to troubleshoot PolicyMaker Standard Edition configuration problems.

MORE INFORMATION

To enable tracing for PolicyMaker Standard Edition CSEs, follow these steps:

  1. Open Group Policy Object Editor to edit the Group Policy object (GPO) that will be applied to the computers where tracing is desired.
  2. In the console tree, expand Computer Configurations, right-click Administrative Templates, point to All Tasks, and then click Add/Remove Templates.
  3. In the Add/Remove Templates dialog box, click Add.
  4. Locate the following administrative template file, and then click OK.

    %windir%\inf\desktopstandard.adm

  5. In the Add/Remove Templates dialog box, click Close.
  6. A DesktopStandard node will appear under Administrative Templates. Locate each desired CSE under the new DesktopStandard node, enable the policy item, and then set the Tracing option to On.

    Note You can also modify the maximum size, the location of the trace file, and the quantity of the event logging.

For more information about each policy option, see the PolicyMaker Standard Edition Help document.

Note The path of the Pmuser.log file or of the Pmcomp.log file may differ according to the version of the Desktopstandard.adm template that you have imported. You can also change the path manually. Double-check the User Trace property and the Computer Trace property in the policy processing properties of the administrative template. If the trace file is in a hidden folder such as the GroupPolicy folder, a Windows Explorer search will only find the file if the Search hidden files and folders option is enabled. Make sure that the Tracing option is enabled on the client computer. To do this, check for the tracing registry keys in the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy


Each CSE has an associated UID that is stored as a key in this subkey. For example, the UID of PolicyMaker Drive Maps Policy Processing is {1EA5E892-2292-438f-8D05-40E7B0007585}. Not every UID that is listed in this subkey is a PolicyMaker UID.

Keywords: kbexpertiseinter kbhowto kbinfo KB931066