Screen Saver Assigned from Group Policy on Windows 2000 Does Not Work (305357)



The information in this article applies to:

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

This article was previously published under Q305357

SYMPTOMS

At your first logon to a Windows 2000 Professional-based computer to which a Windows 2000 Server-based computer has assigned a specific screen saver, the assigned screen saver may not work. The screen saver was assigned as part of a group policy for clients.

CAUSE

This behavior can occur because the registry value that assigns the group policy Desktop properties is not created when the user logs on for the first time.

RESOLUTION

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 fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date       Time    Version        Size        File name
   --------------------------------------------------
   8/7/2001   04:21p  5.0.2195.3914    222,480   Gdi32.dll
   8/7/2001   04:21p  5.0.2195.3932    707,856   Kernel32.dll
   8/7/2001   04:21p  5.0.2195.3932    707,856   Kernel32.dll(uniprocessor)
   8/7/2001   04:22p  5.0.2195.3914  1,642,128   Win32k.sys(uniprocessor)
   8/7/2001   04:21p  5.0.2195.3914    243,472   Winsrv.dll(uniprocessor)
   6/25/2001  07:17p  3.10.0.103        47,808   User.exe
   8/7/2001   04:21p  5.0.2195.3914    379,664   User32.dll
   8/7/2001   04:21p  5.0.2195.3873    367,888   Userenv.dll
   7/23/2001  06:16p  5.0.2195.3914  1,642,128   Win32k.sys
   7/17/2001  05:38p  5.0.2195.3873    178,960   Winlogon.exe
   8/7/2001   04:21p  5.0.2195.3914    243,472   Winsrv.dll 
				

STATUS

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

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

For additional information about how to install multiple hotfixes with only one reboot, click the following article number to view the article in the Microsoft Knowledge Base:

296861 How to Install Multiple Windows Updates or Hotfixes with Only One Reboot

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Modification Type:MinorLast Reviewed:10/12/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE kbWin2000PreSP3Fix KB305357