[THIN] Re: Idle session limit...
- From: "Jim Kenzig http://thethin.net" <jimkenz@xxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Mon, 18 Aug 2003 16:15:49 -0400
Put the reg setting in a policy template, put the users in a group and
apply the template to the group.
JK
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Joe Shonk
Sent: Monday, August 18, 2003 3:20 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Idle session limit...
Explain... Groups do not have a property page for Terminal Server
settings. And to apply separate groups access to different ICA-TCP
configurations on the server would require multiple IP address to be
assigned.
Joe
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Jim Kenzig http://thethin.net
Sent: Monday, August 18, 2003 12:00 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Idle session limit...
Or put them in a group. ; )
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Jan Broucinek
Sent: Monday, August 18, 2003 2:56 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Idle session limit...
In User Manager, select all of the users that you want to affect (click
while holding Shift or Ctrl), then go to User and Properties, you can
then modify the timeout settings for the whole bunch of them in one
stroke. Then go back and set the one user to whatever you want him to
be.
Jan Broucinek, System Manager
Arthur Rutenberg Homes, Inc.
(727) 536-5900 voice
(727) 536-7168 x245 direct
(727) 538-9089 fax
www.arhomes.com
----- Original Message -----
From: Jim <mailto:JimH@xxxxxxxxxxxxxxx> Hathaway
To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
Sent: Monday, August 18, 2003 2:44 PM
Subject: [THIN] Re: Idle session limit...
You got it right.
You don't' really have many options here. Either you go with server
based limitations, or you set the ICA connection settings on the server
to 'inherit client config' and setup the user accounts in your domain
with the 20 minute idle session limitation.
If the domain is windows 2000, you 'Might' be able to use ADSI scripting
to change the 'idle session' timeout variable for all the users in one
pass. (haven't personally done it, but it should be possible, if anyone
else has done this . . and wants to insert some tips feel free).
Otherwise, your customer is going to be stuck making modifications to
all their users domain accounts . . . in order to stop a single user
from being logged out when they run their reports.
J
-----Original Message-----
From: joe@xxxxxxxxxxxxxxxxxxx [mailto:joe@xxxxxxxxxxxxxxxxxxx]
Sent: Monday, August 18, 2003 11:20 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Idle session limit...
I have a customer who is running TSE 4.0 w/ Metaframe XPa FR1. He has
the Idle Session Limit set for 20 minutes for the ICA-TCP Protocol, thus
setting the default for the machine and overriding any user specified
settings. Now he needs one user to be set for unlimited as the user
keeps getting logged off after 20 minutes while running long reports.
I suggested that he set not the ICA-TCP protocol for a Idle Session
Limit and instead set a 20 minute idle session limit in the user
properties instead. That way he as more granular control over the idle
session limit on a per-user bases. He didn't like that idea as he says
there are lot of users that would need to modified.
Any other ideas? Reghacks? Any programs which will keep the session
marked active instead of idle? Obviously MF FR2 or GPOs won't work
since he is running TSE 4.0.
Joe
Other related posts:
