How to Enable Logging for Security Configuration Client Processing in Windows 2000 (245422)



The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional

This article was previously published under Q245422
IMPORTANT: This article 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, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SUMMARY

This article describes how to enable logging output for the Microsoft Windows 2000 Security Configuration Client (also known as "SceCli") component during Group Policy processing. The Security Configuration Client configures user rights, group memberships and security policy, (for example, password policy or account restrictions) that have been set using Group Policy.

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To configure logging output for Security Configuration Client:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following key in the registry:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F79F83A}.

    NOTE: The above registry key is one path; it has been wrapped for readability.

  3. On the Edit menu, click Add Value, and then add the following registry value:

    Value name: ExtensionDebugLevel
    Data type: DWORD
    Value data: 2

  4. Quit Registry Editor.
To immediately generate logging output, type the following command at a command prompt on the client:

secedit /refreshpolicy machine_policy /enforce

When you run this command, the Winlogon.log file is created in the Windows_folder\Security\Logs folder.

Modification Type:MinorLast Reviewed:1/20/2006
Keywords:kbenv kbhowto KB245422