Why does RD session become locked after some time of inactivity?

[systematic1]

Why does an active RD session go into locked computer mode (as if the user
had pressed Ctrl+Alt+Del and then clicked Lock Computer) after several
minutes of inactivity? Is this interval configurable?

We are currently migrating from a Windows 2000 server to Windows 2003 server
using RD (server is colocated at our ASP). Is this auto-locking a feature of
Terminal services or does it affect the console login as well?

[Vera Noest [MVP]]

Sounds like you have a Group Policy in place which enforces a
password protected screen saver. This might be a good setting on
workstations, but is normally not used in a TS session.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?c3lzdGVtYXRpYzE=?="

Post by systematic1
Why does an active RD session go into locked computer mode (as
if the user had pressed Ctrl+Alt+Del and then clicked Lock
Computer) after several minutes of inactivity? Is this interval
configurable?
We are currently migrating from a Windows 2000 server to Windows
2003 server using RD (server is colocated at our ASP). Is this
auto-locking a feature of Terminal services or does it affect
the console login as well?

[Yuri Greene]

This is default policy of Windows 2003 Server. You will need to disable in
the local policy or the domain controller policy---- User
Configuration\control panel\Display\password protect the screen saver

Post by systematic1
Why does an active RD session go into locked computer mode (as if the user
had pressed Ctrl+Alt+Del and then clicked Lock Computer) after several
minutes of inactivity? Is this interval configurable?
We are currently migrating from a Windows 2000 server to Windows 2003 server
using RD (server is colocated at our ASP). Is this auto-locking a feature of
Terminal services or does it affect the console login as well?