<div>
Do you have all users in the same OU and the same policy linked to them?
</div>


Do you have all users in the same OU and the same policy linked to them?

<div>
yes, so I guess that means that it is not the group policy, but rather a local variable
</div>


yes, so I guess that means that it is not the group policy, but rather a local variable

<div>
<div class="content wysiwyg-content">
I am running a Windows 2000 Active Directory domain with group policies that control the users desktop wallpaper, screensaver and desktop lockout timer. &nbsp;On some desktops, the screensaver never cuts on and it just sits there at the CTRL-ALT-Delete to unlock the computer prompt. &nbsp;This is the prompt where the user is already logged in and the desktop is just locked, not the CTRL-ALT-Delete prompt that you get when no one is logged in. &nbsp;The problem is that the screen burns in if the screensaver never cuts on and that is not a good thing. &nbsp;If the user logs off then the screensaver will cut on just fine, but if they stay logged in and just let it lock the desktop then it just sits there at that locked state all night or weekend long and burn in the screen. &nbsp;<br />
<br />
I am wondering why some of them do this, while others work fine. &nbsp;Is there an area in the group policy where I might have something set that would cause this?<br />

</div>
</div>


I am running a Windows 2000 Active Directory domain with group policies that control the users desktop wallpaper, screensaver and desktop lockout timer.  On some desktops, the screensaver never cuts on and it just sits there at the CTRL-ALT-Delete to unlock the computer prompt.  This is the prompt where the user is already logged in and the desktop is just locked, not the CTRL-ALT-Delete prompt that you get when no one is logged in.  The problem is that the screen burns in if the screensaver never cuts on and that is not a good thing.  If the user logs off then the screensaver will cut on just fine, but if they stay logged in and just let it lock the desktop then it just sits there at that locked state all night or weekend long and burn in the screen.  

I am wondering why some of them do this, while others work fine.  Is there an area in the group policy where I might have something set that would cause this?


Screensaver on Windows 2000/XP desktops will not come on

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.