Event ID 1704 indicates that Group Policy security settings are applied to a Windows 2000-based computer even though Group Policy security settings are not applied (884559)



The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Advanced Server

SYMPTOMS

When you update Group Policy security settings on a Microsoft Windows 2000-based computer, the following event is logged in the Application log: Event Type: Information
Event Source: SceCli
Event Category: None
Event ID: 1704
Description:
Security policy in the Group policy objects has been applied successfully. This event indicates that the operation was successful. However, Group Policy security settings are not actually applied to the computer. When you view the Userenv.log file in the %systemroot%\Debug\Usermode folder, you see entries that are similar to the following:
USERENV(b8.324) 18:18:14:894 ProcessGPORegistryPolicy: Failed to create archive file with 5
USERENV(b8.324) 18:18:14:894 ProcessGPOList: ProcessGPORegistryPolicy failed.
USERENV(b8.324) 18:18:14:894 ProcessGPOs: Extension Registry ProcessGroupPolicy failed, status 0x80004005.
For example, you experience these symptoms if you run the secedit /refreshpolicy machine_policy /enforce command to force an update of Group Policy security settings.

CAUSE

This problem may occur in situations where permissions are set on the Ntuser.pol file, and these permissions deny access to this file. If the Ntuser.pol file cannot be accessed, Group Policy processing is not completed successfully. In this scenario, no events are logged to the Application log to notify you that Group Policy is not applied to the computer.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, 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: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

This hotfix requires Windows 2000 Service Pack 4 (SP4).

Restart requirement

You must 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 file attributes) 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
----------------------------------------------------------
23-Mar-2004  17:17  5.0.2195.6824      42,256  Basesrv.dll      
20-Sep-2003  15:45  5.0.2195.6824     236,304  Cmd.exe          
19-Jun-2003  11:05  5.0.2195.6660     233,744  Gdi32.dll          
23-Mar-2004  17:17  5.0.2195.6824      54,544  Mpr.dll          
28-Aug-2004  20:53  5.0.2195.6958     335,120  Msgina.dll       
23-Mar-2004  17:17  5.0.2195.6892      90,264  Rdpwd.sys
26-Aug-2004  15:28  5.0.2195.6970   5,893,632  Sp3res.dll       
23-Mar-2004  17:17  5.0.2195.6897     403,216  User32.dll       
28-Aug-2004  20:53  5.0.2195.6972     393,488  Userenv.dll      
10-Mar-2004  17:37  5.0.2195.6898     181,520  Winlogon.exe        
23-Mar-2004  17:17  5.0.2195.6897     742,160  Kernel32.dll     
09-Aug-2004  18:51  5.0.2195.6966   1,632,624  Win32k.sys
25-Sep-2003  09:08  5.0.2195.6826     243,984  Winsrv.dll   

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies To" section.

MORE INFORMATION

For additional information about how hotfix packages are named, 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, 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


Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbBug kbfix kbWin2000preSP5fix kbHotfixServer kbQFE KB884559 kbAudEndUser kbAudITPRO