Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 2470 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

Configure Threshold for "Update Failed" Message

PeterB

Hi All,

My 1st post so be gentle :)

Apologies if this is a really dumb question but I have searched hi and low and cannot find an answer.

We are running Sophos Enterprise Console 5.1 and can find no way of configuring/controlling the "update failed" messages clients receive. As the majority of our endpoints are laptops they often get out of date by 24-48 hours, subsequently end users receive the "update failed" message and log tickets with the helpesk when there is basically nothing wrong and the client  has normally updated before the helpdesk has even responded to the ticket.

Is there a way to control when the endpoint displays the "update failed" message i.e. when the client is 7 days out of date or something?

Thanks in advance

Peter

:37999


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

    You might also find that depending on how the overall scheduling works, if your SUMs are updating during the process of the endpoints downloading the updates (especially where bandwidth throttling is configured) - we have seen incidences where endpoints cannot retrieve updates and will throw errors.

    The best way to check what the cause is to review the logs on the endpoint for the AutoUpdate component, as it will provide actual detail of the error. The messages sent to the console are generally vague and rarely ever provide any useful information other than updating failed for whatever reason.

    I have often found that updating fails due to network timeouts, random authentication failures (have yet to explain that one, but suspect it is an overload condition on the server), and SUMs updating while a download is taking place resulting in a checksum match failure. Each of those messages I could only find through reviewing an SDU from an affected endpoint.

    :38145
Reply
  • 0

    You might also find that depending on how the overall scheduling works, if your SUMs are updating during the process of the endpoints downloading the updates (especially where bandwidth throttling is configured) - we have seen incidences where endpoints cannot retrieve updates and will throw errors.

    The best way to check what the cause is to review the logs on the endpoint for the AutoUpdate component, as it will provide actual detail of the error. The messages sent to the console are generally vague and rarely ever provide any useful information other than updating failed for whatever reason.

    I have often found that updating fails due to network timeouts, random authentication failures (have yet to explain that one, but suspect it is an overload condition on the server), and SUMs updating while a download is taking place resulting in a checksum match failure. Each of those messages I could only find through reviewing an SDU from an affected endpoint.

    :38145
Children
No Data