Upgraded BigFix to 10.0.1.41 and LMT to 9.2.21.0, after a few days seeing almost all clients displaying "Outdated Scan" in the Capacity Scan Health Widget in the ILMT Browser tool. I have updated all the scanner to the 9.2.21.0 version, I have tried to force a software and capacity rescan, force VM upload, restarted the BESFillDB and reimported, but the issue still persists.

The Outdated Scan status was introduced in 9.2.21 release. So you have to re-schedule "Run Capacity Scan and Upload Result (9.2.21.0)" fixlet in order to collect new data for "Scanner Information" analysis in last_hw_scan_success.info fle. The analysis has got "Time of Last Successful Capacity Scan" field which keeps date of the last capacity scan, then the LMT data import can load the information to LMT.

Hi Piotr, thank you for that quick response. As part of my troubleshooting, I have initiated the "Run Capacity Scan and Upload Result (9.2.21.0)" fixlet in order to collect new data for "Scanner Information" analysis, but I find that it is failing for 9 of my 32 clients. And it is these clients now that have the Outdated scan. What can I do to troubleshoot this situation?

I have verified that these 9 clients can connect back to the BigFix server on port 52311.

On the BES server, the root process is on 52311:

C:\Windows\system32>pslist | findstr /i "1172"

BESRootServer 1172 8 32 415 24500 0:18:26.734 59:00:42.358

C:\Windows\system32>netstat -ano | findstr /i "52311"

TCP 0.0.0.0:52311 0.0.0.0:0 LISTENING 1172

Thanks,

Bala

I restarted the BESClient on the 9 machines that had the Old scans, and their Run Capacity Scan fixlet jobs ran to success. After that the last_hw_scan_success.info got updated:

# cat last_hw_scan_success.info

2020-10-20 12:52:29 UTC

and then when I ran the data import in LMT, the 9 clients were no longer showing Old Scanner infor, but all 32 clients show old scan info: being more than 12 hours older. Is this something that I really need to worry about? Or should I schedule the capacity scans more frequently now for the new version?

The Run Capacity Scan fixlet has to run continuously on each agent and scan its capacity every 30 minutes. This is requirement for sub-capacity in order to catch capacity changes during e.g. VM mobility. The process checks old values with ones and save date of the validation. The date is used by the "Scanner Information" analysis afterwards. So you have to ensure there is no Outdated scans.