This article has been archived. It is offered "as is" and will no longer be updated.
After you establish and then apply a Group Policy object (GPO) that defines restricted groups, the resulting group membership on the destination computer may not remove inactive computer accounts and inactive security identifiers (SIDs). Additionally, the following errors may be logged in the application log:
Event Type: Warning Event Source: SceCli Event Category: None Event ID: 1202 Date: 21/09/1999 Time: 18:15:14 User: N/A Computer: Computer Name Description: Security policies are propagated with warning. 0x4b8 : An extended error Occurred. Please look for more details in TroubleShooting section in Security Help.
Event Type: Error Event Source: Userenv Event Category: None Event ID: 1000 Date: 21/09/1999 Time: 18:15:14 User: NT AUTHORITY\SYSTEM Computer: Computer Name Description: The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (1208).
After you turn on debug logging, an error message that is similar to the following may be logged in the log file:
Remove Domain Name\Computer Name. Error 1377: The specified account name is not a member of the local group. Error removing Domain Name\Computer Name.
After you delete the account that appears in the error message, an error message that is similar to the following may be logged in the log file:
Remove SID: S-1-5-21-1398348832-478745078-1651329330-1035. Error 1377: The specified account name is not a member of the local group. Error removing SID: S-1-5-21-1398348832-478745078-1651329330-1035 Sid2Name does not resolve this account
This problem occurs because during the processing of the GPO, one of the user accounts or SIDs that is defined in the Restricted Groups policy setting cannot be validated or is not found on the local computer or on the domain. When this problem occurs, subsequent users in the GPO are not made members of the target group.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must have Microsoft Windows 2000 Service Pack 4 installed to install this hotfix.
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
One way to determine if an error occurred during the processing of a particular group is to check the log file. For additional information about how to turn on debug logging, click the following article number to view the article in the Microsoft Knowledge Base:
245422 How to enable logging for Security Configuration Client processing in Windows 2000
For additional information about the new file naming schema for Microsoft Windows software update packages, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For additional information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates