automatic session lock

[Edgar Zapata]

I have an XP SP2 box. I connect to a Windows Server 2003 standalone via terminal services.
For some reason, after some minutes without pressing any key, the session locks automatically.
Is there a way I can either change the lock time threshold or disabling session locking?
I have searched for a long while. I don't think it has anything to do with fast user switching.

thank you much.

[Jon Finley]

On the Server, you can go into Administrative tools, Terminal Services Configuration, Connections, and edit the settings for time-out behavior.

Jon

[Edgar Zapata]

Jon,
thank you.
I haven't even tried though, since TS time out works for allow/disallow disconnection.
The session doesn't get disconnected.
It is only that the session gets locked.

regards.

[Norman_21]

Hello Edgar,

I hope it's not too late. Refer to the MSKB:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840721

Meanwhile, the lock policy settings is located under:
[User Configuration\Administrative Templates\System\Logon/Logoff]

Disable Lock Computer


This MSKB maybe helpful to lock down a TS session:
http://support.microsoft.com/default.aspx?scid=kb;en-us;278295

Hope this help


Hope this help

[Edgar Zapata]

Latif,
Thanks for your help, however I am still unable to prevent the Terminal session from getting locked.

The user is able to unlock the session. It is only that we allow her access a Terminal Server in remote administration mode as the administrator. But we don't give her the password. We just type it ourselves everytime her TS session gets locked due to -I guess idle time, time out or smtg.
The thing is, as I mentioned regarding Jon Finley's response, that the session doesn't get disconnected. It ONLY gets locked.
There must be a way though to avoid automatic session lock.

I'll keep searching.
regards.

[Norman_21]

##The user is able to unlock the session. It is only that we allow her access a Terminal Server in remote administration mode as the administrator. But we don't give her the password. We just type it ourselves everytime her TS session gets locked due to -I guess idle time, time out or smtg.
The thing is, as I mentioned regarding Jon Finley's response, that the session doesn't get disconnected. It ONLY gets locked##

Two things to consider,

1. Create an OU letâ s call it TSUsers->create a user account letâ s call it tsuser1 in the TSUsers OU->use the account tsuser1 to logon from the TS administration mode.
My point is that you donâ t have to use the administrator account even if the TS is in administration mode? Using this step, means the session lock will not happen since this OU has no GPO applied yet.
However, if the lock happened again, then the Terminal Services configuration is being used not the TS GPO.

2. Youâ re confusing me between the term lock and the term idle session limit?
If the Disable lock policy is set to disabled or not configured then this is not a lock issue but most likely the idle time is enabled. Go to the startup menu -> programs -> administrative tools menu-> TS configuration -> right click RDP-TCP ->Properties-> and for the idle session limit settings on the sessions tab.

If above didnâ t show any settings enabled for the idle session limit, then right click the administrator account ->look for the idle time setup on the sessions tabs

The conclusion is that, the group policy hierarchy as following:
The TS Configuration overrides the user object and the GPO overrides the TS Configuration

Let me know but Iâ m sure this should fix your issue

Keep

[Norman_21]

Edgar,

Have you tried the steps in my last post?
Any updates please?

Thanks

[Edgar Zapata]

Finally got it.
I guessed it had nothing to do with disconnecting a session. That's why I discarded the Terminal Services Configuration at first glance.
I must recognize though, that I got so frustrated that after a while I tried TS Configuration as well as anything you guys suggested.
BTW, Latif, I couldn't try your suggestion #1 since this is only a member server.

To my surprise, it got fixed the moment I unchecked the Screen Saver "On resume, password protect" box.

[Norman_21]

Edgar,

The member server is the TS Licensing mode probably and as always recommended by Microsoft to join it to a DC so as to have control over TS users by deploying GPO?

My 2 Cents

Glad your problem is solved

[Edgar Zapata]

I have found a solution to this question as seen in the comments above.