G
Guest
Greetings everyone,
I have about 60 users whose screen savers do not automatically start after
the specified idle period. The screen saver names and idle times can be
changed and the registry shows that the changes are made but the screen saver
doesn't trigger. The user is able to do everything else on their system
without a problem. These are all local adminsitrative users. Please review
the following MS KB:
http://support.microsoft.com/kb/326719/en-us
This is the closest article that could apply to my environment. Many
systems in my company went from XP "Gold" to XP SP2. The article confirms
that the problem was first corrected in SP1. We currently correct the
problem by recreating the user's local profile. Is it possible that applying
the service pack does not correct the problem on an existing profile
originally created pre-SP2 installation, but it's corrected in profiles
created post-SP2 installation?
I have seen similar corrective behaviour with Windows 2000 Server SP4. If
the root directory of a server's boot volume has too many files, the server
will not boot even if SP4 has been installed on it. MS documents say the
problem was corrected in SP4. But further reading reveals that Windows 2000
installs that are service packed do not get the updated boot code to fix the
problem. You have to call MS to get a small email-able exe to update the
boot code. Servers installed with SP4 built-in install the updated boot code
and do not experience the problem.
Has anyone seen this screen saver behaviour before and corrected it? Any
feedback is appreciated.
Thanks!
- S
I have about 60 users whose screen savers do not automatically start after
the specified idle period. The screen saver names and idle times can be
changed and the registry shows that the changes are made but the screen saver
doesn't trigger. The user is able to do everything else on their system
without a problem. These are all local adminsitrative users. Please review
the following MS KB:
http://support.microsoft.com/kb/326719/en-us
This is the closest article that could apply to my environment. Many
systems in my company went from XP "Gold" to XP SP2. The article confirms
that the problem was first corrected in SP1. We currently correct the
problem by recreating the user's local profile. Is it possible that applying
the service pack does not correct the problem on an existing profile
originally created pre-SP2 installation, but it's corrected in profiles
created post-SP2 installation?
I have seen similar corrective behaviour with Windows 2000 Server SP4. If
the root directory of a server's boot volume has too many files, the server
will not boot even if SP4 has been installed on it. MS documents say the
problem was corrected in SP4. But further reading reveals that Windows 2000
installs that are service packed do not get the updated boot code to fix the
problem. You have to call MS to get a small email-able exe to update the
boot code. Servers installed with SP4 built-in install the updated boot code
and do not experience the problem.
Has anyone seen this screen saver behaviour before and corrected it? Any
feedback is appreciated.
Thanks!
- S