Hey all.

I was hoping someone could clear up what occurs when the Last Update column changes dates.  What specific event causes this date to update. 

The problem I'm having is that I'm still seeing some XP computers flagging an alert that agents are not reporting under Agent Health.

BUT...if you look to the Groups section in the Last Updated column, all the dates are always current.  It is not until you look to the Agent Health Error on the specific computer (Groups--> All Devices--> click on device with error--> click on View Errors) where you will see another Last Updated date and this date will be older -- the reason I would assume then for the error to trigger. 

So this is confusing....two last updated dates with the second being buried and three or four mouse clicks away.

I also continue to have issues with XP systems and agent health even with computers where the Dec certificate update has been applied.

- Lars

Hi OIStaff,

Did you have a case open with our support team?  If so, can you list it here and I'll contact you directly to perform some troubleshooting with your XP clients.

As far as the last updated status...that can be the machine is connecting to the service but for some reason one of your agents isn't able to communicate or isn't working properly.  If you can either list your support case # or open one if you don't have one we can perform some deeper troubleshooting.

Thanks.

Hi Jon.

My intent with the question was to know what that column means and what triggers it to be updated.  It FOR SURE does not mean the date the computer itself was updated.

I mean, if you have agent errors being reported but the last updated date stamp is current, what's the use of the information?  I'm trying to understand just what I can use that information for.

Thanks.

Hi,

Last Updated refers to the last time the client checked into the service.  Something may be occurring separately with your machines updating or a specific agent may be failing, but they are still checking into the service.

I would really need access to logs and possibly a machine to determine exactly what is occurring, so if you have time please open a support case and we'll investigate.

Thanks.