Re: Controlling logoff behavior

Thank you so much for your reply. Very helpful stuff.

Sounds like I need to have my own windows process running at all times that
the user is logged in, waiting for the logoff request. If I am misreading
this, or if there is a less invasive means, please let me know.

"Alex Balcanquall - MS" wrote:

Hi,

There are security implication to intercpeting logoff events. However here
are a couple of paths for you to investigate:

1) have a process that runs that interruprs the session ending event
http://msdn2.microsoft.com/en-us/library/microsoft.win32.systemevents.sessionending.aspx

2) leverage the WM_QUERENDSESSION function
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shutdown/base/wm_queryendsession.asp


--

Alex Balcanquall
Product Manager
Terminal Services Team
Microsoft

-This e-mail is provided "AS IS" with no warranties, and confers no rights-




"Tim" <Tim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B1B2801A-1024-47B7-BF0A-94C413878C2E@xxxxxxxxxxxxxxxx
TS Gurus:

We are implementing a vendor package which takes advantage of Win2K3
Terminal Services. I have no access to the vendor's source code, and
asking
them to change it will elicit a laugh. At times, this package is too
clever
by half, in that it leaves processing going in the background of the TS
session, after the user has closed the application windows. If the user
logs
out of the TS session, the background processing ends, because the exe is
running within the TS session. Then the user's processing does not
complete,
angry e-mails are sent, my career is toast, etc.

Here's what I would like to do. If a user attempts to log off from his TS
session, and there is background processing going on, I would like to
change
his logoff to a disconnect, so that his processing can continue.

I know how to do everything I need to do, except 1) intercept the logoff
attempt (I can probably work around this) and 2) cancel the logoff attempt
and instead disconnect the user.

Any assistance would be appreciated.


.

Relevant Pages

  • Re: Controlling logoff behavior
    ... You are correct - you need a program running all the time - theire may be other possibilities such as running the application in a USER based logoff script, but this might be too late. ... Terminal Services Team ... > session, after the user has closed the application windows. ... > out of the TS session, the background processing ends, because the exe> is ...
    (microsoft.public.windows.terminal_services)
  • Re: Controlling logoff behavior
    ... If I have a program running all the time within a user's ... TS session, awaiting a logoff request, there is no way that I can guarantee ... out of the TS session, the background processing ends, because the exe ...
    (microsoft.public.windows.terminal_services)
  • Re: Controlling logoff behavior
    ... There are security implication to intercpeting logoff events. ... session, after the user has closed the application windows. ... session, and there is background processing going on, I would like to change ...
    (microsoft.public.windows.terminal_services)
  • Re: Controlling logoff behavior
    ... A logoff script can be set using Group Policy. ... TS session, awaiting a logoff request, there is no way that I can ... I have looked everywhere for where to set a user's logoff script. ... out of the TS session, the background processing ends, because the ...
    (microsoft.public.windows.terminal_services)
  • Re: RWW - log off after timeout?
    ... doing something at the time of the logoff or if the session has just been ... "orphaned" (user did not log off the LAN workstation, RWW session timed out, ... determine if the RWW part of the session has "timed out" while the RDP ... open files on his workstation when RWW timed out (again, ...
    (microsoft.public.windows.server.sbs)