Idle Question

  • Thread starter Thread starter Andrew Kennard
  • Start date Start date
A

Andrew Kennard

Guest
Hi all

If you set and Idle limit for a user and then tell it to "End Session" will
it send WM_CLOSE messages to the open apps or does it just 'kill' them ?

ie if a user started an intensive process and then walked away for a coffee
would it get killed with the timeout was reached or would it close
graciously ?

Thanks

Andrew
 
Re: Idle Question

What is the Windows version of Terminal Services are you running?
Please consider this feature carefully, as pontentially it will cause data
loss.
If a user coffee break is longer than the idle time limit, first a warning
dialog will show up:
"Session has been idle over its time limit, logoff will start in 2
minutes...."
if the session still in 'idle' (i.e. no mouse, keyboard or other input)
after 2 minutes over the idle time limit, the user session will be logoff.
If the session has running apps that don't want to be closed such as you
have unsaved excel spreadsheet, they will be 'killed', and the user will not
have the chance to save his/her work.
Different apps behave differently, I would suggest you try it out and see if
the behavior is what you expect.

Thanks
Soo Kuan



--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Andrew Kennard" <b@a.com> wrote in message
news:%23$jU75J0IHA.1240@TK2MSFTNGP02.phx.gbl...
> Hi all
>
> If you set and Idle limit for a user and then tell it to "End Session"
> will it send WM_CLOSE messages to the open apps or does it just 'kill'
> them ?
>
> ie if a user started an intensive process and then walked away for a
> coffee would it get killed with the timeout was reached or would it close
> graciously ?
>
> Thanks
>
> Andrew
>
>
 
Re: Idle Question

Windows 2003 Server Standard Edition

OK so by the sounds of it any time-out must be longer than any posssible
batch update of a database say

The problem we have is it is just too "easy" for the user to click the close
X at the top of the screen rather than log-off when they are done .... no
matter how many times you tell them

Thanks

Andrew

"Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in message
news:e8WDb5V0IHA.5944@TK2MSFTNGP04.phx.gbl...
> What is the Windows version of Terminal Services are you running?
> Please consider this feature carefully, as pontentially it will cause data
> loss.
> If a user coffee break is longer than the idle time limit, first a warning
> dialog will show up:
> "Session has been idle over its time limit, logoff will start in 2
> minutes...."
> if the session still in 'idle' (i.e. no mouse, keyboard or other input)
> after 2 minutes over the idle time limit, the user session will be logoff.
> If the session has running apps that don't want to be closed such as you
> have unsaved excel spreadsheet, they will be 'killed', and the user will
> not have the chance to save his/her work.
> Different apps behave differently, I would suggest you try it out and see
> if the behavior is what you expect.
>
> Thanks
> Soo Kuan
>
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Andrew Kennard" <b@a.com> wrote in message
> news:%23$jU75J0IHA.1240@TK2MSFTNGP02.phx.gbl...
>> Hi all
>>
>> If you set and Idle limit for a user and then tell it to "End Session"
>> will it send WM_CLOSE messages to the open apps or does it just 'kill'
>> them ?
>>
>> ie if a user started an intensive process and then walked away for a
>> coffee would it get killed with the timeout was reached or would it close
>> graciously ?
>>
>> Thanks
>>
>> Andrew
>>
>>
>
 
Re: Idle Question

But when they close the session window, the session becomes
disconnected. Maybe you should set a time-out limit on disconnected
sessions, but not on idle ones?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Andrew Kennard" <b@a.com> wrote on 18 jun 2008 in
microsoft.public.windows.terminal_services:

> Windows 2003 Server Standard Edition
>
> OK so by the sounds of it any time-out must be longer than any
> posssible batch update of a database say
>
> The problem we have is it is just too "easy" for the user to
> click the close X at the top of the screen rather than log-off
> when they are done .... no matter how many times you tell them
>
> Thanks
>
> Andrew
>
> "Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in
> message news:e8WDb5V0IHA.5944@TK2MSFTNGP04.phx.gbl...
>> What is the Windows version of Terminal Services are you
>> running? Please consider this feature carefully, as
>> pontentially it will cause data loss.
>> If a user coffee break is longer than the idle time limit,
>> first a warning dialog will show up:
>> "Session has been idle over its time limit, logoff will start
>> in 2 minutes...."
>> if the session still in 'idle' (i.e. no mouse, keyboard or
>> other input) after 2 minutes over the idle time limit, the user
>> session will be logoff. If the session has running apps that
>> don't want to be closed such as you have unsaved excel
>> spreadsheet, they will be 'killed', and the user will not have
>> the chance to save his/her work. Different apps behave
>> differently, I would suggest you try it out and see if the
>> behavior is what you expect.
>>
>> Thanks
>> Soo Kuan
>>
>>
>>
>> --
>> This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>>
>> "Andrew Kennard" <b@a.com> wrote in message
>> news:%23$jU75J0IHA.1240@TK2MSFTNGP02.phx.gbl...
>>> Hi all
>>>
>>> If you set and Idle limit for a user and then tell it to "End
>>> Session" will it send WM_CLOSE messages to the open apps or
>>> does it just 'kill' them ?
>>>
>>> ie if a user started an intensive process and then walked away
>>> for a coffee would it get killed with the timeout was reached
>>> or would it close graciously ?
>>>
>>> Thanks
>>>
>>> Andrew
 
Back
Top