Some of the users complaint to me that their terminal service session screen was locked after a few minutes. In the begging, I thought their session was logged out, so I checked their session setting. I was surprised that their these users setting are the same with the rest of other staff that are not affected by the screen lock out.
I called them up to find out what really happened, and finally understood that only the screen was locked, not the session. Unfortunately there was no option to control the screen from the administration menu. So I Google around to find some answer, and from reading a few forums the setting was set at the policy, however we never set any screen lock policy.
Oh, before I go on, you probably thought this screen lock must have come from the screen saver, right? Yes, it is, but the user terminal service was configured for it to launch a designated application (via a script) that the user have no way of altering the screen saver setting. Strange thing is, this only affected on two staff, and not the rest.
So, I called the user up to get their password, and then change the Environment setting so that session is loaded in full. Then log in remotely to the server using her id, and then change the screen saver setting (which was set to start after 1 minute after being idle).