1 of 1 people found this helpful
I doubt that the reboots are coming from a task that has no targets and you haven't started. However, there are some items that are automatically updated on clients, which includes vulscan and some agent settings. It might be that some agent are starting to get a few updated settings or something. I would recommend that you look at the vulscan logs and you should be able to find more information about what task or action is presenting issues and what settings it might be contributing.
I have been working with LANDesk support on this and after going through the logs they agree with you. I just sent them my agent config yesterday, and they are looking to see if I missed something. What I do not understand is, if I have my config set in 27 different places to never reboot, if I missed one place somewhere, why would it ignore the other 27? In addition, why in the world would it give the user a pop up notification 12 hours before the reboot, and have no way to minimize the pop up and only have a 10 minute delay option. I will post an update when I hear back from support, but it seems like an odd problem for me when I have not heard of anyone else here having this issue.
Agents use agent settings to decide what to do when a reboot is needed. If each machine has a default setting and that default setting has been modified, then next time the VulScan runs it will get these new settings. Now if these machines are also pending a reboot for ANY reason then they will be prompted for a reboot.
What is the default Scan & Repair setting and what does it currently have set for reboot options? Remember as well that software distribution settings have been combined with patch management. Could anything else have been set to use different agent settings.
If that is OK, then other than an unusual product bug, could anybody else possibly have caused this by playing about with this setting? Hopefully LD will be able to see from the vulscan logs anyway.
MarXtar Ltd/MarXtar Corporation
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
LANDesk support ended up giving me a new vulscan.dll, apparently mine was not updating on the endpoints, so they were not getting the new agent reboot settings.