We have seen strange client scan behavior on our Mac clients for a while, off site Mac OS (Lion through Mavericks) agents will do little more than send in a basic time stamp update to the core inventory service, which is misleading as the sofware and hardware scans are not being updated. When initiating a scan from the client, we saw the following:
ldiscan (303) <Critical>: Last scan date : Sun Dec 31 2000 18:00:00 CST
ldiscan (303)<Critical>: Last scan date occured more than 24 hours old (115510 hours, 7 minutes)
ldiscan (303s0<Error>:No destination. Not scanning to the cre, and nto scanning to file, stopping scanning now.
This after new agent installation, rebooting, verifiying (requesting) a certficate successfully to communciate via the gateway, confirmation that the software portal is fully functional, waiting several days, and attempting to force full scans via terminal on the client and even deleting and recreating the client on the core server, verifying all permissiosn to all of the folders on the core server and verifying all permissions we could think of in general(to cover the high points).
What brought this to our attention was the deployment of updated agents, the name of the LANDesk agent would never update in the console no matter what we tried.
Now I have gone into this same client again and changed the agent setting to allow it to store inventory scans locally in addition to sending to the core.
Fixed. Core updated immediately upon a scan request from the client. Nothing else changed. We have reproduced this scenario on several systems at this time.
Now we had local scans turned off, due to concerns that they would build up and eventually take up storage.... so we have two questions:
1. Has anyone had a similar experience?
2. if scans are allowed to store locally, how are those scans kept cleaned up on the clients for maintenence purposes?