Hi Ahmed,
As for user logon/logoff events, you can use System Event Notification
Manager (see MSDN docs on the ISensLogon and ISensLogon2 interfaces). As for
running a process as a user, you can probably use the CreateProcessAsUser
API, but I am not sure how do you obtain the logged on user's token.
> Hi all,
>
[quoted text clipped - 5 lines]
>
> thanks in advance...
Ahmed Perlom - 28 Feb 2006 22:06 GMT
Thanks Dmytro.
The user identity might not be important to me. I wonder if there is nay
security constraints that a local system service could start another
executable whenever another user logins or fast switch to a session? Do you
think ignoring the user identity would make it any easier to implement?
> Hi Ahmed,
>
[quoted text clipped - 13 lines]
>>
>> thanks in advance...
Dmytro Lapshyn [MVP] - 01 Mar 2006 08:24 GMT
Ahmed,
"Local system" can be an account with quite restricted rights (for example,
AFAIR it cannot access the network). So you may wish to consider running
your service at least under the "NETWORK SERVICE" account or even a more
privileged account.
> Thanks Dmytro.
>
[quoted text clipped - 21 lines]
>>>
>>> thanks in advance...