Make sure to take a look at what agent settings you have configured or are being used by the clients. While the whole agent hasn't been upgraded, some parts, such as vulscan, are updated automatically and are handling new agent behaviors, including reboot settings.
Could it be related to this thread:
MarXtar Ltd/MarXtar Corporation
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
Was this ever resolved for you? We're having the exact same issue. A small but increasing number of PCs running 9.5 SP2 are spontaneously rebooting over the course of the day.
Our investigation has determined that although the reboot settings say to reboot whenever the PC has been logged out for more than 3 minutes, that part of the settings is being ignored. Instead what's happening is localsch is creating tasks that don't fire until the user logs in.
The trigger for all of this was a weekly patch job that ran on Sunday morning. Let's say PC1 is vulnerable to six of the patches contained in the patch group being repaired. Vulscan repairs the first two on Sunday morning, then tells localsch to issue a vulscan /rebootwithui /offline upon the next login and also to issue a vulscan /reboot (task ids 559 and 567). Localsch, for reasons of its own, does not launch either of those tasks immediately, as expected. Then the user logs in 24 hours later and localsch wakes up and launches vulscan /rebootwithui /offline. The user gets the reboot prompt. Eventually the user gives in and clicks the Reboot Now button. When the PC comes back online, vulscan /continue immediate kicks off and repairs one of the remaining three patches. Then it tells localsch to run vulscan /rebootwithui again, which it does. The user clicks Reboot again. The cycle begins. Eventually the livid user has rebooted four times and calls the helpdesk asking when the madness will end.
We can't confirm that this only affects 9.5 SP2 agents but we haven't had any 9.6 SP1 agents affected to date, and a handful of tests have successfully rebooted my own 9.6 SP1 PC.
I never received a definite reason but was told it was likely due to vulscan updating itself and since LANDesk decided to apply our emergency distribution settings as the default reboot settings it allowed our devices to reboot without proper warning. The upgrade should have allowed us to pick the default options rather than just picking one randomly. Im really concerned about this with upgrading to SP1 and whether we will see similar behavior.
the same happened to us - I had opened a case with support & also found out restarts done by using the windows start menu do not necessarily report to the core as having been completed per the security scan - the "Reboot Now" button on the scan gui does, so the Landesk "Reboot Needed" attribute stays active if not rebooted through the landesk prompt. then the next time a scan runs, it will prompt again for a restart.
This was affecting some, but not all pc's. SP1 update was suggested to fix this & address one other issue I had reported. Once 9.6 sp1 was installed, I rebuilt the agents & spent some time targeting the problematic pc's first with the updated agent. at this point almost all my clients are up to date & reboots are working as they should.