Thanks @MichalJ
Indeed, I found the "configuration" which is more a "task" to me. The Question / suggestion was more :
Why the notification send multiple time "configuration failed", when it could easily say :
The Client Task "Install EES" failed
And with eventually the information "Because XXXXX".
I have coded a small app that runs on client machines on the hour every hour and checks certain variables to see if a machine requires a reboot. If it does, the user is alerted via popup of the reason for the reboot.
We use labtech as our RMM and while it does have a built in popup system for alerting users of reboots, it doesn't cover all the cases in which we'd like to alert the user of a required reboot. We also wanted to consolidate the reboot requests into one branded popup, so things like feature updates, AV updates, if we as administrators request a reboot, etc would all trigger the same popup with reasons a reboot is required.
It's a WPF app written in C# so anything that can be checked like a file, reg flag, or WMI check would be useful.
We've started taking on clients recently that are already using ESET and have no reason to change. When it was just a couple of clients using ESET, I wasn't too worried about detecting the reboots. Now the ESET user base is increasing, I'd like to get it included.
1.: - I created a dynamic group for collect the computers with error message "Restart required" :
2.: - Then I defined a CRON triggered task for send a pop-up window message into the affected computers:
"Hello Collegue, please restart your computer as soon as possible because an ESET software update...bla..bla" or something like this
You can configure the CRON for example launch the message hourly, every 10 minutes or as you want