Just doing a bit of tracking of client events via ePO V4.5 and a feed to our monitoring server and found hundreds of events like this
"<server>_CLIENT time_Detected=09/17/13 08:36:16 UTC,Event_Description=Update Failed,Host_Name=<hostname>,OS_Platform=Professional,OS_Type=Windows XP,User_Name=<username>,Event_ID=2402,Error=Product has been reached to end of life"
These machines are DAT updating OK and typically have VSE 188.8.131.520, Agent 184.108.40.2060, Engine 5400.1158
But none of the products on the machines reporting this issue seem to be EOL?
Any ideas? A google of the exact error text doesn't return much.
btw... we are planning to upgrade to epo 4.6 and VSE 8.8 etc but just not this week!
Ok but this is a custom view of yours. If you click on the system and go to the Installed Products section do you have other prodcuts installed different to VirusScan and McAfee Agent?
I might be wrong but I believe this error could be due to Engine 5400 being superceded by 5600.
I don't think so, engine 5400 will be EOL on october (next month) so it shouldn't be.
Maybe it's a silly question but does this computer has SP3 installed for Windows XP or is it SP2?
El mensaje fue editado por: ulyses31 on 19/09/13 12:03:57 CEST
Good valid questions.....
I dismissed it being 5400 as that engine is used throughout and only some of the machines (a significant number) are reporting the client end of life error.
The machine I sampled is SP3 - I double checked.
I believe these client events are in direct response to the "compliance update" we run multiple times per day - I've double checked that job and it's only attempting an update of the DAT and engine on this job.
All very strange.
I only picked this up as I'm trying to reduce the load on our reporting server (and from ePO) on the client event trigger and there are hundreds of client events triggered for this error which seem superfluous. I know I could put a filter on the trigger but am curious as to what's causing the alert still.....
Thanks all for your input so far