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

    I'm not sure what happened with your SUM. Either you were unlucky and looked at the trace logs when updates were actually happening, or something unknown went wrong and a restart of the service fixed it. The times you are reporting now are closer to what I'd expect, except that as I mentioned before the no update check is a bit longer than it should be. Hopefully we'll improve this. You should be able to get the times down by using fewer subscriptions.

    As to the CPU usage when deploying to a remote link, SUM just uses standard Windows file i/o when talking to UNC. It's possible that with a slow link there are more callbacks in the Windows level code, but I've not profiled this.

    Cheers,

    John Reynolds

    :1836
Reply
  • 0

    Hi Matt,

    I'm not sure what happened with your SUM. Either you were unlucky and looked at the trace logs when updates were actually happening, or something unknown went wrong and a restart of the service fixed it. The times you are reporting now are closer to what I'd expect, except that as I mentioned before the no update check is a bit longer than it should be. Hopefully we'll improve this. You should be able to get the times down by using fewer subscriptions.

    As to the CPU usage when deploying to a remote link, SUM just uses standard Windows file i/o when talking to UNC. It's possible that with a slow link there are more callbacks in the Windows level code, but I've not profiled this.

    Cheers,

    John Reynolds

    :1836
Children
No Data
Unfiltered HTML