I have stood up a new 9.2.25.0 ILMT All-In-One server. The ILMT endpoints, prior to the fixlet update, were running the 9,2,15.0 ILMT scanner.
All but one endpoint were updated to the 9.2.25.0 IILMT Scanner.
The ILMT Task Install or Upgrade Scanner (9.2.25.0) is listed as non-relevant.
If I use the Analyze the Relevance of a Fixlet or Task (9.2.25.0) for the above Task, the problem endpoint lists all Relevances as True except for Relevance 4 which is False.
Please advise, thank you,
Karen
Which OS is the problem endpoint running?
Are you able to remove the scanner viaTask ID 4: Uninstall Scanner?
Well, I am getting closer to resolution, I think…
The endpoint is a 2012R2 Windows Server VM.
I was able to use the Uninstall Scanner fixlet to uninstall the old 9.2.15.0 scanner on the endpoint. Then the Install or Update Scanner fixlet became available for this endpoint and I was able to successfully run the task.
After that, I ran the Initiate Software Scan and the Run Capacity Scan and Upload Results. According to the BES Console, all endpoints reported a 0 return code for the tasks.
Via the ILMT interface, I did a Data Import. The import completed successfully but there were 12 warnings.
In the Overview report of the ILMT interface, it reports 1 failed scan and it is for the VM that I had just updated the scanner.
The scheduled import removed the failed scan notice but the ILMT was stating that it had no VM manager data on the endpoint. So for grins, I did another data import and the VM Manager data was found and the correct PVUs/core is now specified in the reports for this VM.