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

    Yet another thought that might be relevant to the discussion of slow links:

    The update done if you select an 'Update Now' or reconfigure a SUM is rather more careful about validating everything than the normal updates done by SUM. This is so that many updating problems (for instance due to corruption or tampering) can be fixed by selecting update now from SEC.

    However, in the case of slow links this has the side-effect of causing a detailed check of the files in the CID, which could indeed by painful. If this is causing significant problems, we may have to look at adding more configuration options for this.

    There is a third option to using remote CIDs or child SUMs: make the primary SUM files available from a web server, configure the endpoints to update via http from this, and add a standard caching proxy at the branch office. Many of our larger customers use this scheme, particularly as the branch offices often have proxies already. There are a few downsides to this though: SEC doesn't handle the association of endpoints with http locations seamlessly (we hope to improve this), it involves some extra infrastructure deployment, and endpoint updating can take a little longer.

    Cheers,

    John Reynolds

    :1851
Reply
  • 0

    Yet another thought that might be relevant to the discussion of slow links:

    The update done if you select an 'Update Now' or reconfigure a SUM is rather more careful about validating everything than the normal updates done by SUM. This is so that many updating problems (for instance due to corruption or tampering) can be fixed by selecting update now from SEC.

    However, in the case of slow links this has the side-effect of causing a detailed check of the files in the CID, which could indeed by painful. If this is causing significant problems, we may have to look at adding more configuration options for this.

    There is a third option to using remote CIDs or child SUMs: make the primary SUM files available from a web server, configure the endpoints to update via http from this, and add a standard caching proxy at the branch office. Many of our larger customers use this scheme, particularly as the branch offices often have proxies already. There are a few downsides to this though: SEC doesn't handle the association of endpoints with http locations seamlessly (we hope to improve this), it involves some extra infrastructure deployment, and endpoint updating can take a little longer.

    Cheers,

    John Reynolds

    :1851
Children
No Data
Unfiltered HTML