Re: Controlling logoff behavior
- From: "Alex Balcanquall - MS" <alexbal@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 31 Jul 2006 20:16:02 -0700
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 (for example after the shell has shutdown). I expect the app you need to write would be super small anyways.
--
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:8DE985B8-BC97-4DFD-A9AE-41D93BEEA45E@xxxxxxxxxxxxxxxx
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.
.
- Follow-Ups:
- Re: Controlling logoff behavior
- From: Tim
- Re: Controlling logoff behavior
- References:
- Re: Controlling logoff behavior
- From: Alex Balcanquall - MS
- Re: Controlling logoff behavior
- From: Tim
- Re: Controlling logoff behavior
- Prev by Date: Re: Spooler hang
- Next by Date: Re: Terminal Services and AD BDC
- Previous by thread: Re: Controlling logoff behavior
- Next by thread: Re: Controlling logoff behavior
- Index(es):
Relevant Pages
|