RDP-TCP Properties - Sessions Tab - reasonable values

[Guest benxxv via WinServerKB.com]

Hi,

 

Can you suggest what are the reasonable values we can set for RDP-TCP

Properties - Sessions Tab - Override user settings

 

End a disconnected session:

Active session limit

Idle session limit

 

Though my question is a generic one, can anyone suggest the general practice

in the industry.

 

Regards.

 

--

Message posted via WinServerKB.com

http://www.winserverkb.com/Uwe/Forums.aspx/windows-ts/200710/1

[Guest Vera Noest [MVP]]

Re: RDP-TCP Properties - Sessions Tab - reasonable values

 

I'm not sure that there is a general practice, because it depends

very much on your needs and the type of work that is performed by

your users.

The only setting which most people will agree upon (I think) is:

Active sessions : No limit.

Idle and disconnected session is more difficult.

What kind of applications are your users running? Forcefully ending

disconnected or idle sessions can potentially lead to data loss in

some applications. That's the first thing to investigate.

If your users work only regular hours, say from 08:00 AM to 5:00

PM, and you have a backup running every night, starting at say

11:00 PM which requires that all users are disconnected from any

databases or documents, then that would be an argument to set a

time-limit on disconnected and idle sessions of 6 hours, since you

have to throw them out anyway before backup starts.

But if you don't have that requirement, then you could allow them

to forget to logoff when they go home, come back the next day and

connect to their disconnected session. That would be an argument to

allow disconnected and idle sessions for a maximum of 15-16 hours.

But then of course the specs of the server begin to play a role.

Can it sustain lots of disconnected and idle sessions?

 

Keep an eye on the type and number of sessions that you see on your

server during at least a week. If you then spot a problem with a

particular type of session (many endless idle or disconnected

sessions), try to set a time limit which addresses that specific

problem. And don't forget user education!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"benxxv via WinServerKB.com" <u30064@uwe> wrote on 10 okt 2007 in

microsoft.public.windows.terminal_services:

> Hi,

>

> Can you suggest what are the reasonable values we can set for

> RDP-TCP Properties - Sessions Tab - Override user settings

>

> End a disconnected session:

> Active session limit

> Idle session limit

>

> Though my question is a generic one, can anyone suggest the

> general practice in the industry.

>

> Regards.

[Guest benxxv via WinServerKB.com]

Re: RDP-TCP Properties - Sessions Tab - reasonable values

 

Thankyou Vera for the elaborated information.

 

After observing my server and terminal server active sessions for morethan 10

days, I put this message to user feedback.

 

My Server is Poweredge 2800 with 64BIT 2003 Server, SQL Server 64 Bit with

8GB RAM, 4 Xeon Processors. At any time, out of my 50 or more users, almost

15 user sessions are in active state which are past 15 to 20 hours idle time,

as I put No Limit for active sessions, these sessions are consuming the

server memory. And SQL is almost at 4GB RAM Usage. So, i thought instead of

No Limit, I should end the sessions, so that RAM gets cleared, but, whatever

free memory I keep available for the applications, SQL Server is consuming.

The RAM usage in question is by SQL Server. Bottom line, out of my 8GB RAM,

morethan 4GB is used by SQL Server, 3 GB by other applications and these TS

Idle (Active) Sessions, means 90% Memory in USE at any poing of time and only

1GB I see as Free......Any further suggetions ?

 

Regards.

 

Vera Noest [MVP] wrote:

>I'm not sure that there is a general practice, because it depends

>very much on your needs and the type of work that is performed by

>your users.

>The only setting which most people will agree upon (I think) is:

>Active sessions : No limit.

>Idle and disconnected session is more difficult.

>What kind of applications are your users running? Forcefully ending

>disconnected or idle sessions can potentially lead to data loss in

>some applications. That's the first thing to investigate.

>If your users work only regular hours, say from 08:00 AM to 5:00

>PM, and you have a backup running every night, starting at say

>11:00 PM which requires that all users are disconnected from any

>databases or documents, then that would be an argument to set a

>time-limit on disconnected and idle sessions of 6 hours, since you

>have to throw them out anyway before backup starts.

>But if you don't have that requirement, then you could allow them

>to forget to logoff when they go home, come back the next day and

>connect to their disconnected session. That would be an argument to

>allow disconnected and idle sessions for a maximum of 15-16 hours.

>But then of course the specs of the server begin to play a role.

>Can it sustain lots of disconnected and idle sessions?

>

>Keep an eye on the type and number of sessions that you see on your

>server during at least a week. If you then spot a problem with a

>particular type of session (many endless idle or disconnected

>sessions), try to set a time limit which addresses that specific

>problem. And don't forget user education!

>_________________________________________________________

>Vera Noest

>MCSE, CCEA, Microsoft MVP - Terminal Server

>TS troubleshooting: http://ts.veranoest.net

>___ please respond in newsgroup, NOT by private email ___

>

>"benxxv via WinServerKB.com" <u30064@uwe> wrote on 10 okt 2007 in

>microsoft.public.windows.terminal_services:

>

>> Hi,

>>

>

>>

>> Regards.

 

--

Message posted via WinServerKB.com

http://www.winserverkb.com/Uwe/Forums.aspx/windows-ts/200710/1

[Guest Vera Noest [MVP]]

Re: RDP-TCP Properties - Sessions Tab - reasonable values

 

That's one of the reasons that running TS and SQL on the same

server are not recommended.

I believe that by default, SQL takes all the memory it can get. But

you can use a startup parameter to the SQL service to change that

behaviour.

 

See SQL Books Online: Server Memory Options

http://msdn2.microsoft.com/en-us/library/ms178067.aspx

 

Maybe you'd better ask in an sql newsgroup, like:

microsoft.public.sqlserver.server

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"benxxv via WinServerKB.com" <u30064@uwe> wrote on 11 okt 2007 in

microsoft.public.windows.terminal_services:

> Thankyou Vera for the elaborated information.

>

> After observing my server and terminal server active sessions

> for morethan 10 days, I put this message to user feedback.

>

> My Server is Poweredge 2800 with 64BIT 2003 Server, SQL Server

> 64 Bit with 8GB RAM, 4 Xeon Processors. At any time, out of my

> 50 or more users, almost 15 user sessions are in active state

> which are past 15 to 20 hours idle time, as I put No Limit for

> active sessions, these sessions are consuming the server memory.

> And SQL is almost at 4GB RAM Usage. So, i thought instead of No

> Limit, I should end the sessions, so that RAM gets cleared, but,

> whatever free memory I keep available for the applications, SQL

> Server is consuming. The RAM usage in question is by SQL Server.

> Bottom line, out of my 8GB RAM, morethan 4GB is used by SQL

> Server, 3 GB by other applications and these TS Idle (Active)

> Sessions, means 90% Memory in USE at any poing of time and only

> 1GB I see as Free......Any further suggetions ?

>

> Regards.

>

> Vera Noest [MVP] wrote:

>>I'm not sure that there is a general practice, because it

>>depends very much on your needs and the type of work that is

>>performed by your users.

>>The only setting which most people will agree upon (I think) is:

>>Active sessions : No limit.

>>Idle and disconnected session is more difficult.

>>What kind of applications are your users running? Forcefully

>>ending disconnected or idle sessions can potentially lead to

>>data loss in some applications. That's the first thing to

>>investigate. If your users work only regular hours, say from

>>08:00 AM to 5:00 PM, and you have a backup running every night,

>>starting at say 11:00 PM which requires that all users are

>>disconnected from any databases or documents, then that would be

>>an argument to set a time-limit on disconnected and idle

>>sessions of 6 hours, since you have to throw them out anyway

>>before backup starts. But if you don't have that requirement,

>>then you could allow them to forget to logoff when they go home,

>>come back the next day and connect to their disconnected

>>session. That would be an argument to allow disconnected and

>>idle sessions for a maximum of 15-16 hours. But then of course

>>the specs of the server begin to play a role. Can it sustain

>>lots of disconnected and idle sessions?

>>

>>Keep an eye on the type and number of sessions that you see on

>>your server during at least a week. If you then spot a problem

>>with a particular type of session (many endless idle or

>>disconnected sessions), try to set a time limit which addresses

>>that specific problem. And don't forget user education!

>>_________________________________________________________

>>Vera Noest

>>MCSE, CCEA, Microsoft MVP - Terminal Server

>>TS troubleshooting: http://ts.veranoest.net

>>___ please respond in newsgroup, NOT by private email ___

>>

>>"benxxv via WinServerKB.com" <u30064@uwe> wrote on 10 okt 2007

>>in microsoft.public.windows.terminal_services:

>>

>>> Hi,

>>>

>>

>>>

>>> Regards.

[Guest benxxv via WinServerKB.com]

Re: RDP-TCP Properties - Sessions Tab - reasonable values

 

Dear Vera,

 

Thankyou. I explore further on this in SQL Groups.

 

Regards.

 

Vera Noest [MVP] wrote:

>That's one of the reasons that running TS and SQL on the same

>server are not recommended.

>I believe that by default, SQL takes all the memory it can get. But

>you can use a startup parameter to the SQL service to change that

>behaviour.

>

>See SQL Books Online: Server Memory Options

>http://msdn2.microsoft.com/en-us/library/ms178067.aspx

>

>Maybe you'd better ask in an sql newsgroup, like:

>microsoft.public.sqlserver.server

>_________________________________________________________

>Vera Noest

>MCSE, CCEA, Microsoft MVP - Terminal Server

>TS troubleshooting: http://ts.veranoest.net

>___ please respond in newsgroup, NOT by private email ___

>

>"benxxv via WinServerKB.com" <u30064@uwe> wrote on 11 okt 2007 in

>microsoft.public.windows.terminal_services:

>

>> Thankyou Vera for the elaborated information.

>>

>

>>>>

>>>> Regards.

 

--

Message posted via WinServerKB.com

http://www.winserverkb.com/Uwe/Forums.aspx/windows-ts/200710/1