Look at the inventory of an affected machine. In the LANDESK section of the inventory keep drilling down and you will see the locally scheduled tasks. Check what is set in there. Anything that might affect it?
Also, if you are on 9.5 and SP1, there is an Inventory Settings in the client configuration. This will cause an inventory (HW and SW) to run after a software distribution has taken place. That could be impacting. Any SW Distributions happening around that time?
Out of interest, the impact you are describing is very unusual. Are you able to replicate it by manually running an inventory scan? If so, then it would be a good idea to log this directly with support. There may be a way to work around this but also they could potentially issue an update that fixes the problem. Troubleshooting is definitely required.
Additional FYI. Existing locally scheduled tasks are set to run at the interval specified after the previous run completed. So if the scanner ran at 2pm and took 2 minutes to complete, a per day interval would run the next one at 2:02PM the following day. Normally this means that machines would end up with scans congregating near the beginning of the day because of devices are off at the weekend the next scan will happen close to the time the machine started up becuase more than one day has already passed since the end of the previous run.
Perhaps if you include a screenshot of the scanner configuration you have created. That way we can tell if there are any settings in there that might cause the scan to run at this unexpected time.
Mark McGinn
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based
Update - New v2.3 Now with Automated Subnet Rep Selection and Optional Maintenance of LANDESK Reps
The One-Stop Shop for LANDesk Enhancements
- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing