But the user code component (Win32k.sys) was not modified to check the policy key location when reading the screen saver information.
Also, the original Group Policy snap-in System Administration template (System.adm) sets the ScreenSaveActive and ScreenSaverIsSecure values using REG_DWORD values instead of REG_SZ values, therefore the user mode component (Win32k.sys) does not apply the screen saver policy unless the policy is created by using the new updated System.adm administration template.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Windows 2000 Service Pack 1.
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