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

Upgrading? Need advice? Let us know!

lilhavoc

I want to ask you, our esteemed customers, what information Sophos could provide to make upgrading easier. This applies to upgrades from any version, but I'd love to be able to address people's concerns about the upgrade from Enterprise Console version 3 to version 4 especially.

We've got a great couple of upgrade guides, but what else can we do? What would you like to know more about?

Want to tell us how to do our jobs?? :smileyvery-happy: We'd love to hear to your suggestions, so let's talk!!

Thanks,

Lil

:1039


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

    Hi Matt,

    The 'No action' part isn't relevant to SUM being busy. All these mean is that one of the schedulers has woken up (which they do every minute - yes, it's a pretty crude algorithm) and decided it doesn't need to trigger an action as it's not appropriate to the schedule (e.g. for the protection data on a 15 minute cycle, you'll usually get 14 no actions, then an action).

    More relevant is the log entries for what SUM is actually doing. There should only be a few ide releases a day, so sum should largely be idle. What's concerning is if something has gone wrong on your system such that the checks when there are no updates (which by default will occur every 15 minutes) are taking significant time.

    I don't think there has been a significant upgrade to SUM, but our operations group may have tinkered with something that may have caused sum to got through the self-update process to make sure it is on the correct version.

    Cheers,

    John Reynolds

    :1832
Reply
  • 0

    Hi Matt,

    The 'No action' part isn't relevant to SUM being busy. All these mean is that one of the schedulers has woken up (which they do every minute - yes, it's a pretty crude algorithm) and decided it doesn't need to trigger an action as it's not appropriate to the schedule (e.g. for the protection data on a 15 minute cycle, you'll usually get 14 no actions, then an action).

    More relevant is the log entries for what SUM is actually doing. There should only be a few ide releases a day, so sum should largely be idle. What's concerning is if something has gone wrong on your system such that the checks when there are no updates (which by default will occur every 15 minutes) are taking significant time.

    I don't think there has been a significant upgrade to SUM, but our operations group may have tinkered with something that may have caused sum to got through the self-update process to make sure it is on the correct version.

    Cheers,

    John Reynolds

    :1832
Children
No Data
Unfiltered HTML