Machines last update not posting to EPO

[sw41]

We have an agent handler in the DMZ and EPO server internal.  Our agents are checking in with the AH in the DMZ and the status monitor shows connections and updates coming thru.  When we go into EPO, the devices no not show that they just checked in, instead last check in is 11/03/2020.

What do we check to figure out why the activity on the  AH is not updating in EPO?  The database is online and no errors.  I dont know where to go into the database to see activity coming in from the AH.  Not sure where to start with this.

[cdinet]

On the agent handler install directory on that server, in db\logs, check the server log for any errors.  If server log and masvc log on the client show all successful communication, then one thing to look at is whether these systems are connecting via vpn or not and if so, have you implemented solution in KB52949?  

What version of epo is this and what patch/update level?

If epo 5.10, what is the output of this query from sql?

select count (*) from epocomputerpropsstaging

[sw41]

ePO Build: ePolicy Orchestrator 5.10.0 (Build 2428)
Update Installed: Update 7 (2.0.0.907)

I checked the logs and am not seeing errors.  Checked the VPN thing and that is not the case as my test machine is not using VPN.

The sql result changes as I run it.  2 to 200, so thats active.

[cdinet]

Are you sure then that there are no duplicate systems?  Otherwise we would need to get a mer so we can open up the db files to see what properties are actually being sent to epo.

First of all, I would suggest installing CU9 - https://docs.mcafee.com/bundle/epolicy-orchestrator-5.10.0-release-notes/page/GUID-154723B4-925E-4C2...

That resolves an issue where props aren't updating properly.  After you install the update, it may take some wakeups or a couple of asci's for issue to work itself out.

[sw41]

not sure of anything at this point.  where can I go on the agent handler to see the database connection information??   A case and Mer have already been submitted but still trying to get this sorted out sooner than later.

[cdinet]

Connection information as in failing or what account it is using?  The db.properties file in the root of the db folder should show what account is being used.  The server log would show if there are communication failures.  From the sounds of it, I believe update 9 just might resolve your issue.  It will need to be installed on epo and all agent handlers.