Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 8622 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

out-of-date computers has exceeded the critical level emails

rainyday

Hi,

We've been trying to work out how these warning emails can be made useful and are so far struggling, we receive multiple emails through out the day and upon checking the Enterprise Console 5.0.0.8 there appears to be no rhym or reason between what triggers them.

We have the configure dashboard settings set as follows:-

Policy and Protection

Computers that differ from group policy 1.00% warning 5.00% critical

Connected out-of-date computers: 1.00% warning 12.00% critical (this was increased to see if it would reduce emails, it didn't)

Latest protection from Sophos

Time since last update from Sophos: 24 hours warning, 96 hours critical.

Now my understanding of the above would result in computers only showing in the out-of-date computers section when they last updated over 24 hours ago but we don't see this, some are only out by 12 hours which shouldn't even mark them for warning never mind critical.

Can anyone explain why we are getting these critical out-of-date emails when machines clearly are not?

Thanks

:26145


This thread was automatically locked due to age.
  • 0

    Hello rainyday,

    Latest protection from Sophos

    applies to the updates SUM receives and sets the icon in the lower left Updates pane.

    As to Connected out-of-date computers : what is the updating interval on your clients? There's a (now undocumented) registry key for setting the interval after which a client is considered out-of-date (first mention by Jak in this post).

    Christian

    :26147
  • 0

    The client policy is set to check for updates every 30 minutes, ideally I would like to have them highlighted as a problem after 24 hours.  I've changed the registry key in the link to 240 and restarted the services, will see how this goes.  Am I correct in thinking I would set this to 1440 if I only wanted them to be registered as out of date after one day?

    Thanks

    :26157
  • 0

    Hello rainyday,

    don't know if there is a maximum value. Thinking about it - it's likely that the threshold is exceeded in the morning when the clients have to update after booting up, guess this can't be avoided. 

    Anyway - 30 minutes should be frequent enough if the default latency is still 60 minutes. Hm ...

    Christian

    :26163
  • 0

    Thank Christian, changing the registry has now resulted in the system alerting more like we'd expect.

    :26211