almost number of machines shows offline for almost 2 hours and then reports online. Where as check the logs between client and server communication is happening properly.
Unable to understand where could be the issue, why it is delay in response to the console.
Can anyone suggest.
A computer shows offline on Console if it hasn’t been sending reports for the amount of time specified in the “Mark as offline after” preference of the Console (default 45 minutes). The interval between two reports might be affected by the amount of content that the computer needs to evaluate. So you may take a look at the log of one of the computers that shows offline and check if it hasn’t been sending reports for 45+ minutes. If it is the case, then it’s probably due to the amount of content to evaluate and not a symptom of any malfunctions.
Hello SysAdmin3,
Have you made any changes to the _BESClient_Report_MinimumInterval setting?
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Configuration%20Settings?section=_BESClient_Report_MinimumInterval
Are there many relays between those Clients and a Server?
Have you tried to send Force Refresh to those Clients?
As others have suggested, the most likely scenario is evaluation cycle taking too long so best to start there. I suggest you add in a property that looks at the average evaluation cycle and see if it falls within the expected report interval. Let it run for a while first, needs a few cycles to settle down.
average of evaluationcycle of client / 1000 * second / minute
*edit - see newer inspector as suggested by @AlanM 
average duration of evaluationcycle of client
If that seems normal and you also see normal behavior in the client logs, i.e. report times consistent with the report interval that you’ve set, then go up one level to it’s Relay and make sure it’s healthy and not congested. Log on directly or have a look at the Relay diagnostics page (disabled by default now so you may need to enable it):
If things again seem normal, follow the trail via any other Relays and then to the BigFix Server where you can check FillDB status and make sure reports aren’t being held up or discarded.
Thanks all I will check and confirm.
Its much easier to use the newer (and all supported versions of the client have this) average duration inspector which gives a time interval. See https://developer.bigfix.com/relevance/reference/evaluation-cycle.html#average-duration-of-evaluation-cycle-time-interval