Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 4725 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

End point 'Up To Date' notification period - customise?

Craig_IT

Hi Everyone,

New to the forums in search of some support that I haven't had any luck finding via the knowledge base.

Basically my endpoints are set to update every 120 minutes (every 2 hours / 12 times a day) as a lot of our workstations are turned on / used at different times through the day, so this hopefully captures as many as we can.

My problem is that even though they are getting updated every two hours, I will always have between 40 and 100+ endpoints listed as "Not since...." in the up to date column and it hasn't even been 2 hours from the date and time they list.  For example, they will say "Not since 14/09/10 10:15:13 AM" and the actual time is 11:30am on the same day.  This causes the "Out Of Date Computers" statistic on the EC dashboard to be grossly inaccurate and is no good for reporting or any kind of real troubleshooting / diagnosis of PCs truly out of date by more than a day / week / etc.

Is there a way to customise the period for the EC to determine what is out of date and what is not, a configuration setting somewhere or a file you can modify some parameters for?

Thanks,

Craig

PS...this is Sophos Enterprise Console 4 for anyone wondering....thanks.

:5015


This thread was automatically locked due to age.
Parents
  • 0

    Hi Christian,

    Thanks for the quick and informative response.

    I'm trying but I can not quite get my head around the concept you have described, everytime I think I have it figured out I realise I still don't really understand how it's supposed to be interpreted, as logic says:

     - I set an update interval of 2 hours

     - If SEC is reporting a computer as "Out Of Date" and the Up To Date column reads "not since X" which is outside of the 2 hours, then some other circumstance has stopped it updating such as the PC being off / network connection loss / fault within SEC during that update window, 

     - If SEC is reporting a computer as "Out Of Date" and the Up To Date column reads "not since X" which is inside of the 2 hours, this indicates to me that SEC wasn't able to update the PC within the update window, does this mean the window is too frequent and can't update that many PCs in that time frame and it just starts at the top again on the next update window therefore always missing these PCs?

    I suppose I was assuming that all the PCs are being updated without issue on time and that SEC was getting ahead of itself, "jumping the gun" you could say on reporting PCs out of date. So basically, updating issues aside, if the client version doesn't match the latest then it will be listed in this column and as "Out Of Date" even though theoretically it was supposed to be updated an hour ago?

    Thanks,

    Craig

    :5051
Reply
  • 0

    Hi Christian,

    Thanks for the quick and informative response.

    I'm trying but I can not quite get my head around the concept you have described, everytime I think I have it figured out I realise I still don't really understand how it's supposed to be interpreted, as logic says:

     - I set an update interval of 2 hours

     - If SEC is reporting a computer as "Out Of Date" and the Up To Date column reads "not since X" which is outside of the 2 hours, then some other circumstance has stopped it updating such as the PC being off / network connection loss / fault within SEC during that update window, 

     - If SEC is reporting a computer as "Out Of Date" and the Up To Date column reads "not since X" which is inside of the 2 hours, this indicates to me that SEC wasn't able to update the PC within the update window, does this mean the window is too frequent and can't update that many PCs in that time frame and it just starts at the top again on the next update window therefore always missing these PCs?

    I suppose I was assuming that all the PCs are being updated without issue on time and that SEC was getting ahead of itself, "jumping the gun" you could say on reporting PCs out of date. So basically, updating issues aside, if the client version doesn't match the latest then it will be listed in this column and as "Out Of Date" even though theoretically it was supposed to be updated an hour ago?

    Thanks,

    Craig

    :5051
Children
No Data
Unfiltered HTML