Logged on and locked
I just noticed with PDQ 10.1 that "Only run if no user is logged on" is running if a user is logged on but the machine is locked. Is this a change or a bug?
0
Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.
Comments
Hi Thomas,
This is not a bug but can be confusing. We take the states from Windows. Only run if a user is logged on should only run if the user is Logged in or Locked and Only run if no user is logged on should only run if the user is Logged Off or Disconnected. We'll work with the developers to add this to the product so it's easier to catch.
I have a followup question regarding this. I have to deploy a new antivirus at my company and want it to deploy during the night when noone is working. My problem is that people have a tendency to not sign out and sometimes not even saving their work when they leave. So i have to find a solution to push the new AV to computers that people is signed out of. I thought that "Only run if no user is logged on" would have been the solution but as i found out yesterday that doesnt work if the user is logged in and the computer is locked. Is there any way to do what i want?
The package involves uninstall of the old AV and then a force reboot so i have to make sure that it only runs on computers the users are signed out of.
Conversely, the condition "Only Run if a user is logged on" also detects locked state as not logged on. For a message, this is problematic if you want to give the user 10-15 minutes to close the applications being updated before you kill them. If they happen to be away and return to their desk and unlock, they may not be aware. If you can determine (locked) in Inventory why not Deploy?
Hi,
How can i monitor the user logon\logoff time on the inventory?
This PowerShell Scanner shows the last logon time for every user on a system by searching through the Event Log. You could modify it to also grab logoff time.
https://github.com/pdq/PowerShell-Scanners/tree/master/PowerShell%20Scanners/User%20Last%20Logged%20On