Article ID: 216357 - Last Review: February 22, 2007 - Revision: 3.4

Identifying Group Policy Client-Side Extensions

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q216357
Notice
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center (http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000) is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy (http://support.microsoft.com/lifecycle/) .
Expand all | Collapse all

SUMMARY

Group Policy architecture includes both server and client-side components. The server component includes the user interface that an administrator can use to configure a unique policy. When Group Policy is applied to a user or computer, the client component interprets the policy and makes the appropriate changes to the environment. These are known as Group Policy client-side extensions. A Globally Unique Identifier (GUID), a 128-bit number identifying a given object, identifies the extension to the operating system. As Group Policy is processed, the Winlogon process passes the list of Group Policy Objects (GPOs) that must be processed to each Group Policy client-side extension. The extension uses the list to process the appropriate policy when applicable.

When viewing event log entries and log files recorded by Group Policy and these client-side extensions, an administrator may need to identify the extension by its GUID.

MORE INFORMATION

Because the GUID for each client-side extension was assigned when the component was created, the GUIDs for each of the client-side extensions documented below are the same on each installation of Windows 2000.
  • GUID: 25537BA6-77A8-11D2-9B6C-0000F8080861
    Component: Folder Redirection
  • GUID: 3610EDA5-77EF-11D2-8DC5-00C04FA31A66
    Component: Microsoft Disk Quota
  • GUID: 42B5FAAE-6536-11D2-AE5A-0000F87571E3
    Component: Scripts
  • GUID: 827D319E-6EAC-11D2-A4EA-00C04F79F83A
    Component: Security
  • GUID: B1BE8D72-6EAC-11D2-A4EA-00C04F79F83A
    Component: EFS Recovery
  • GUID: C6DC5466-785A-11D2-84D0-00C04FB169F7
    Component: Application Management
  • GUID: A2E30F80-D7DE-11d2-BBDE-00C04F86AE3B
    Component: Internet Explorer Settings
  • GUID: 35378EAC-683F-11D2-A89A-00C04FBBCFA2
    Component: Registry Settings
  • GUID: e437bc1c-aa7d-11d2-a382-00c04f991e27
    Component: IP Security
Third-party programs and additional Microsoft services that install client-side extensions register those components in the following registry location:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions
For additional information about the GPExtensions registry entry, see the following article in the Microsoft Knowledge Base:
216358  (http://support.microsoft.com/kb/216358/EN-US/ ) Troubleshooting Group Policy Client-Side Extension Behavior
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Datacenter Server
Back to the top
Keywords: 
kbenv kbinfo KB216357