Time out issue on Terminal Server (Windows 2003)

[1LUV1T]

Hey guys, I have users nagging about their sessions being timed out after 15 minutes. I want to increase it to 60 minutes and have done so in all the places (I think) possible;

1. Secpol.msc (local policy)
2. Group policy in Active Directory (loopback enabled)
3. Terminal Server configuration (RDP setting)

Where else can I look?

The clients are connecting to our TS with Remote Desktop.
Thanks!

 

[dberg35]

In AD the user account.

 

[1LUV1T]

Terminal Services Configuration is set to 'Override' user settings (set to 1 hour).

Anyone else?

 

[1LUV1T]

Actually I see what they're referring too. It does not actually Disonnect or Log them off. It just 'locks' them out and they get the

"This computer is in use and has been locked. Only (username) or an administrator can unlock this computer" and so they have to reenter there passowrd to get back in the session.

 

[1LUV1T]

bump

 

[cmeagan656]

Turn off the screensaver on the TS. On W2K3 it seems to be on by default. I don't have a W2K3 server in front of me at the moment, its at work and I'm at home, or I'd tell you exactly how.

Cheers.

 

[Roadki11]

I dont understand what the problem is? a timed screensaver lockout is a good thing!

RoadKi11

 

[ShackDaddy]

So the users aren't just working along and suddenly are locked out. Their screens lock just like the workstations at most large corporations after being idle for 15 minutes. That's not a TS config issue, that's a policy setting.

ShackDaddy
Shackelford Consulting

 

[1LUV1T]

Ok this is really annoying now as I have tried every possible option including;
1. checking to see if screen savers are off on client machines, and terminal server (all are OFF)
2. checked group policies
3. checked local policies
4. edited registry for;
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval and HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime
and HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, create or edit the DWORD value of KeepAliveEnable and set it to 1

What else can there possibly be? I am timing a dummy PC connected to TS through RDP and exactly every 10 minutes of idle time, it is asking for the password.

 

[1LUV1T]

Ok I just broke the 10 minute limit and the last thing I did was set screen saver option in local policy to "0" (which probably means disable)... That's dumb because if screen savers are disabled on the server as a whole, it should be for everyone else by default at least.