The User Policy Cannot Be Refreshed After a Cached Logon (325551)



The information in this article applies to:

  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Professional SP3
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP3
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP3

This article was previously published under Q325551

SYMPTOMS

If a user performs a cached logon process on a Windows 2000-based member server or a Windows 2000-based workstation, the user does not receive group policies. When the user logs on, connects the computer to the network, and runs the following commands to refresh the group policies, the first command runs successfully but the second command does not refresh the user policy:

secedit /refreshpolicy machine_policy /enforce
secedit /refreshpolicy user_policy /enforce

The following errors are recorded in the Userenv.log file:
USERENV(254.248) 18:45:44:613 LibMain: Process Name:
C:\WINNT\system32\secedit.exe
USERENV(254.248) 18:45:44:613 RefreshPolicy: Entering with 0
USERENV(254.248) 18:45:44:613 RefreshPolicy: Failed to open event with 2
USERENV(254.248) 18:45:44:613 RefreshPolicy: Leaving.
This problem also occurs with remote access and virtual private network users if a user connects with a remote access/virtual private network connection that does not require the user to press CTRL+ALT+DELETE and to use the Log On to Windows dialog box, but instead uses the Log on using dial-up connection option.

CAUSE

An inappropriate function is used in the attempt to locate a domain controller.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE kbWin2000preSP4Fix KB325551