Microsoft KB Archive/835901

= A Restricted Groups policy setting may not remove security identifiers in Windows 2000 Server =

Article ID: 835901

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server

-





SYMPTOMS
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:

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:

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 \.

Error 1377: The specified account name is not a member of the local group. Error removing \.

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



CAUSE
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.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
You must have Microsoft Windows 2000 Service Pack 4 installed to install this hotfix.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
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.   Date         Time   Version            Size    File name ---  24-Mar-2004  02:17  5.0.2195.6876     388,368  Advapi32.dll 24-Mar-2004 02:17  5.0.2195.6866      69,904  Browser.dll 24-Mar-2004 02:17  5.0.2195.6824     134,928  Dnsapi.dll 24-Mar-2004 02:17  5.0.2195.6876      92,432  Dnsrslvr.dll 24-Mar-2004 02:17  5.0.2195.6883      47,888  Eventlog.dll 24-Mar-2004 02:17  5.0.2195.6890     143,632  Kdcsvc.dll 11-Mar-2004 02:37  5.0.2195.6903     210,192  Kerberos.dll 21-Sep-2003 00:32  5.0.2195.6824      71,888  Ksecdd.sys 11-Mar-2004 02:37  5.0.2195.6902     520,976  Lsasrv.dll 25-Feb-2004 23:59  5.0.2195.6902      33,552  Lsass.exe 11-Mar-2004 02:37  5.0.2195.6897     123,152  Msv1_0.dll 24-Mar-2004 02:17  5.0.2195.6897     312,592  Netapi32.dll 24-Mar-2004 02:17  5.0.2195.6891     371,472  Netlogon.dll 24-Mar-2004 02:17  5.0.2195.6896   1,028,880  Ntdsa.dll 12-Apr-2004 23:40  5.0.2195.6924     392,464  Samsrv.dll 24-Mar-2004 02:17  5.0.2195.6893     111,376  Scecli.dll 12-Apr-2004 23:40  5.0.2195.6923     261,392  Scesrv.dll 05-Feb-2004 20:18  5.0.2195.6896   5,869,056  Sp3res.dll 24-Mar-2004 02:17  5.0.2195.6824      50,960  W32time.dll 21-Sep-2003 00:32  5.0.2195.6824      57,104  W32tm.exe



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
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

Keywords: kbhotfixserver kbqfe kberrmsg kbbug kbfix kbqfe kbwin2000presp5fix KB835901

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.