Microsoft KB Archive/830464

= Group Policy does not apply roaming profiles correctly if NTuser.dat and NTuser.pol files are not synchronized =

Article ID: 830464

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows XP Home Edition
 * Microsoft Windows XP Professional
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

-





SYMPTOMS
Group Policy settings and preferences that are targeted at one client computer are unexpectedly applied to a roaming profile user who logs on to a different client computer.



CAUSE
When a roaming profile user logs off, the NTuser.dat file is always updated on the roaming profile share. The corresponding NTuser.pol file is only updated if the timestamp of the local copy that was created at logon is newer than the copy found in the roaming profile share. A synchronization problem may occur if a user with a roaming profile logs on to multiple client computers at the same time. This can eventually cause policy settings to be applied incorrectly.

For example, if the Group Policy loopback feature is applied on one of the client computers, the NTuser.dat file on the roaming profile share may contain loopback policy settings that are not present in the NTuser.pol file. If this problem occurs, the loopback policy settings that are targeted at one client computer may be unexpectedly applied to a user who logs on to a different client computer.



Windows XP service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

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 Microsoft Windows Server 2003 Service Pack or Microsoft Windows XP 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 phone 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
Windows Server 2003, Windows XP SP1, Windows 2000 Server SP3, or Windows 2000 Server SP4

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. Windows 2000:

Date        Time   Version        Size       File name --  19-Dec-2003  14:40  5.0.2195.6824     42,256  Basesrv.dll 20-Sep-2003 16:45  5.0.2195.6824    236,304  Cmd.exe 19-Dec-2003 14:40  5.0.2195.6882    222,992  Gdi32.dll 19-Dec-2003 14:40  5.0.2195.6867    711,440  Kernel32.dll 19-Dec-2003 14:40  5.0.2195.6824     54,032  Mpr.dll 19-Dec-2003 14:40  5.0.2195.6883    334,096  Msgina.dll 19-Dec-2003 14:40  5.0.2195.6882     90,232  Rdpwd.sys 19-Dec-2003 14:40  5.0.2195.6882    380,176  User32.dll 19-Dec-2003 14:40  5.0.2195.6886    391,440  Userenv.dll 18-Dec-2003 16:13  5.0.2195.6886  1,630,192  Win32k.sys 10-Nov-2003 16:29  5.0.2195.6873    182,032  Winlogon.exe 19-Dec-2003 14:40  5.0.2195.6884    243,984  Winsrv.dll

Windows XP:

Date        Time   Version        Size     File name ---  23-Dec-2003  14:34  5.1.2600.1330  669,184  Userenv.dll

Windows Server 2003:

Date        Time   Version       Size     File name --  21-Dec-2003  12:14  5.2.3790.115  754,176  Userenv.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Microsoft Windows XP Service Pack 2.



MORE INFORMATION
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbhotfixserver kbqfe kbwinxpsp2fix kbwinservperf kbmgmtservices kbgpo kbgrppolicyprob kbgrppolicyinfo kbwinxppresp2fix kbwinserv2003presp1fix kbwin2000sp5fix kbbug kbfix kbqfe kbwin2000presp5fix KB830464

-

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

© Microsoft Corporation. All rights reserved.