@nbirdi Have you checked the action history on the 3 machines where you ran the ad-hoc software scans? You may find that Task 3 has indeed run on those machines. Task 3 is only relevant immediately after Task 2 runs, when a software scan results package is available, and then becomes non-relevant again after it runs. It is normal for Task 3 to not be relevant most of the time.
What does the Scan Health widget in the BFI UI report?
Hi, itsmpro92.
Thanks for the response.
I did collect logs from the 3 clients on which I ran the ad-hoc scans. There was nothing unusual in the logs and they indicated that scan files were generated.
Upon discussions with our team at-large, it was suggested to stop the existing tasks, and recreate them using the latest fixlets which had just been updated in the BF console.
Yesterday, I recreated all tasks using the 9.2.15.0 fixlets and ran an ad-hoc SW scan on the same 3 servers. This morning, looks like the new “Upload Software Scan results” fixlet picked up these 3 servers and uploaded their scans… I confirmed that 2 of the 3 were inported into BFI. As for the 3rd scan, I’ll give it a bit mor etime befor einvestigating further.
The regular scans are scheduled to run Saturdays. Will know next week, if it was just that the fixlet version needed to be “refreshed”.
Essentially, I stopped all the previous tasks (were an older version of the fixlets) and recreated the tasks making sure they were all the latest version - 9.2.15.0 and, … waited.