I have to develop a program which runs on a local pc as a service an deliver couple of user status to a server. At the beginning I have to detect the user logon and logoff.
My idea was to use the ManagementEventWatcher
class and to query the Win32_LogonSession
to be notified if something changed.
My first test works well, here is the code part (This would executed as a thread from a service):
private readonly static WqlEventQuery qLgi = new WqlEventQuery("__InstanceCreationEvent", new TimeSpan(0, 0, 1), "TargetInstance ISA "Win32_LogonSession"");
public EventWatcherUser() {
}
public void DoWork() {
ManagementEventWatcher eLgiWatcher = new ManagementEventWatcher(EventWatcherUser.qLgi);
eLgiWatcher.EventArrived += new EventArrivedEventHandler(HandleEvent);
eLgiWatcher.Start();
}
private void HandleEvent(object sender, EventArrivedEventArgs e)
{
ManagementBaseObject f = (ManagementBaseObject)e.NewEvent["TargetInstance"];
using (StreamWriter fs = new StreamWriter("C:\status.log", true))
{
fs.WriteLine(f.Properties["LogonId"].Value);
}
}
But I have some understanding problems and I’m not sure if this is the common way to solve that task.
If I query Win32_LogonSession
I get several records which are
associated to the same user. For example I get this IDs 7580798 and
7580829 and if I query
ASSOCIATORS OF {Win32_LogonSession.LogonId=X}
WHERE ResultClass=Win32_UserAccount
I get the same record for different IDs.
(Win32_UserAccount.Domain="PC-Name",Name="User1")
Why are there several logon session with the same user? What is the
common way to get the current signed in user? Or better how to get notified
correctly by the login of a user?
I thought I could use the same way with __InstanceDeletionEvent
to
determine if a user is log off. But I guess if the event is raised, I
cant query Win32_UserAccount
for the username after that. I’m right?
I’m at the right direction or are there better ways? It would be awesome if you could help me!
Edit Is the WTSRegisterSessionNotification class the correct way? I don't know if it's possible, because in a service I haven't a window handler.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…