We have a single site with a Management point on a seperate box (sql replica). In my console, I have columns added for the inventory dates and when looking at the dates, my most recent date is yesterday. If I connect to a machine with an old date, confirm that it indeed, hasnt done an inventory, and initiate an inventory, it is successful. I can then run a report for the last inventory date on that computer and the last inventory date is updated. I dont think its a coincidence that the reporting server is the management point so the data is practically real time. When my console connects up to the primary the old date is still in there. I have become more patient since using CM but I need that updated data in the console sooner, not just on the report. It is updating eventually because I have dates in there from yesterday. But I would like to see today's data today.

Everything with the replica is syncing just fine, I have no errors in my transaction log, my site components are nice and green :) any ideas of where to check/adjust

Where are you seeing this? Resource Explorer or one of the status update pages, or ???

resource explorer is up to date, and the reports last inventory date for a specific computer is correct. but in the console I added a column for last inventory date and that's the one that's not right.

It is like to be one of a few issues:

• WMI caching
• Local PC caching content
• Duplicate PCs within the console

What problem is this causing you? aka why do you care?

other than the fact that its my job to care....

our technicians build collections off criteria that often depends on data collected in inventory. If I troubleshoot anything, I often have my console open with the columns with last activity and inventory dates. this can quickly narrow down a lot of issues and tip me off as to whether a machine is likely in use without me needing to run any report, connect to any machine, etc. If the date in the console is old and I connect  to the machine only to find out that everything is working fine I have been misled and wasted time. 

Also knowing this may be a symptom of some other issue or a misconfiguration I felt it was a cause for concern. 

I assume those are good enough reasons to care.

Dont get me wrong, Im not saying it is not important. I just trying to understand you needs and possible suggest a solution. I will run a few test in my lab and get back to you, next week.