Article ID: 216357 - View products that this article applies to.
This article was previously published under Q216357
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(https://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
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.
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.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensionsFor additional information about the GPExtensions registry entry, see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/216358/EN-US/ )Troubleshooting Group Policy Client-Side Extension Behavior
Article ID: 216357 - Last Review: February 22, 2007 - Revision: 3.4