Urbane.Tiger
New Member
I want to start a program when ever a User Account becomes the active account and to stop the program (using TaskKill) when a User Account ceases to be the active account
To start the program I set up a scheduled task (Start) triggered by User Logon, User Local Connect and User Unlock. To stop the program I set up a scheduled task (Stop) triggered by User Local Disconnect and User Lock.
The program is not started when triggered by a Logon trigger but it is started on a Local Connect or User Unlock triggers.
The difference is manifested in the events that are logged - these are the events logged (presented as a stack - ie last event at top of stack)
It seems that those last two events actually terminate the program - can anyone explain what's happening here, and how I can fix it.
To start the program I set up a scheduled task (Start) triggered by User Logon, User Local Connect and User Unlock. To stop the program I set up a scheduled task (Stop) triggered by User Local Disconnect and User Lock.
The program is not started when triggered by a Logon trigger but it is started on a Local Connect or User Unlock triggers.
The difference is manifested in the events that are logged - these are the events logged (presented as a stack - ie last event at top of stack)
Code:
[FONT=Courier New]
Logon Connect Task Category Op Code
---Event Id---
102 Task Completed (2)
201 Action Started (2)
129 129 Created Task Process Info
200 200 Action Started (1)
100 100 Task Started (1)
319 319 Engine Received Message (1)
119 120 Task Triggered Info
[/FONT]It seems that those last two events actually terminate the program - can anyone explain what's happening here, and how I can fix it.
Last edited:
My Computer
System One
-
- CPU
- Intell 8200
- Motherboard
- ASUS P%PKL
- Memory
- 4G
- Graphics Card(s)
- ATI 2400 PRO
- Hard Drives
- 1 x 74G WD Raptor 10K
1 * 500G WD SATAII
