Article ID: 835901 - View products that this article applies to.
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 Type: Error
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 Domain Name\Computer Name.
Error 1377: The specified account name is not a member of the local group. Error removing Domain Name\Computer Name.
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.
Hotfix informationA 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:
PrerequisitesYou must have Microsoft Windows 2000 Service Pack 4 installed to install this hotfix.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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
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:
245422For 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:
(http://support.microsoft.com/kb/245422/ )How to enable logging for Security Configuration Client processing in Windows 2000
816915For 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:
(http://support.microsoft.com/kb/816915/ )New file naming schema for Microsoft Windows software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates