Hello Atchi,
I'd first check the current Bigfix agent log file (../__BESData/__Global/Logs/xxx.log) on that AWS Instance if 'Install or Upgrade Scanner' fixlet became Relevant.
Furthermore, in the BES Console, right-click on that agent and pick up 'Send Refresh' from a pop-up menu.
Bigfix agent log file should reply with a following entry:
ForceRefresh command received.
That will allow to confirm Bigfix Server<->Bigfix agent connection flow.
at last, there is a useful trick to force the full BigFix Agent<->BigFix Server synchronization :
stop the BigFix Agent,
Delete the '../__BESData' folder,
start the BigFix Agent,
That way BigFix Agent should receive all due actions...
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------
Original Message:
Sent: Wed March 13, 2024 10:06 AM
From: Atchi Reddy Golamari
Subject: BigFix client installed on AWS Instance and able to see that instance in console.But when i execute Install or Upgrade scanner, that instance is showing "Not Reporting" status
BigFix client installed on AWS Instance and able to see that instance in console.But when i execute Install/ Upgrade scanner, that instance is "Not Reporting" status.
Also tried to run another Fixlet i.e. Identify Computers on Cloud. This fixlet also not executed and showing VM as "Not Reported".
Earlier we installed on few other AWS ES2 instances and they are fine. only facing issue with current installs. Please suggest.
------------------------------
Atchi Reddy Golamari
------------------------------