When a user logs on to a Microsoft Windows 2000-based computer, logon scripts do not run.
This problem occurs when the user's roaming profile was created on a Microsoft Windows XP-based computer, but the user has then logged on to a Windows 2000-based computer. Windows XP and Windows 2000 use different methods of creating registry keys for a user profile for a defined logon script that is set through Group Policy. The Windows 2000-based computer does not parse the Windows XP profile registry keys for the logon script.
Hotfix Information
A 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:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
No prerequisites are required.
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) 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.6824 42,256 Basesrv.dll
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
24-Mar-2004 02:17 5.0.2195.6898 242,448 Gdi32.dll
07-May-2004 20:08 5.0.2195.6920 124,688 Gptext.dll
24-Mar-2004 02:17 5.0.2195.6897 742,160 Kernel32.dll
24-Mar-2004 02:17 5.0.2195.6824 54,544 Mpr.dll
24-Mar-2004 02:17 5.0.2195.6895 335,120 Msgina.dll
24-Mar-2004 02:17 5.0.2195.6892 90,264 Rdpwd.sys
05-Feb-2004 20:18 5.0.2195.6896 5,869,056 Sp3res.dll
24-Mar-2004 02:17 5.0.2195.6897 403,216 User32.dll
05-Aug-2003 22:14 5.0.2195.6794 385,808 Userenv.dll
07-May-2004 01:39 5.0.2195.6920 20,240 Userinit.exe
11-Mar-2004 02:37 5.0.2195.6897 1,720,368 Win32k.sys
07-May-2004 01:40 5.0.2195.6920 182,032 Winlogon.exe
25-Sep-2003 18:08 5.0.2195.6826 243,984 Winsrv.dll
24-Mar-2004 02:17 5.0.2195.6897 742,160 Kernel32.dll
11-Mar-2004 02:37 5.0.2195.6897 1,720,368 Win32k.sys
25-Sep-2003 18:08 5.0.2195.6826 243,984 Winsrv.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
816915Â
(http://kbalertz.com/Feedback.aspx?kbNumber=816915/
)
New file naming schema for Microsoft Windows software update packages
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates