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

Best practice: Secondary Update location; Sophos or own library?

Hi Everyone,

I (like many others) are in the middle of upgrading our Sophos environment from V7.x to V9.5.

One thought that has occurred to me is the current "best practice" thinking when it comes to the location of  the Secondary Update location.

We currently have an internet-facing password protected WebCID as our secondary update location.  Is it best to replicate this for V9.5, or should I direct the Secondary Update location to "Sophos" and not bother with my own secondary update location?

Thoughts for and against these approaches would be gratefully appreciated.

Many thanks in advance,

Steve

:8011


This thread was automatically locked due to age.
  • Hello Steve,

    I (like many others) are in the middle of upgrading

    ... while some others are preparing for 9.7 :smileywink:

    I'd use "Sophos" only if setting up a WebCID is not justified because the number of potential clients is very small. I was also glad to have one as secondary location (for mostly "internal" clients) when one of the management servers went belly up. Used it to redirect the clients to the new incarnation of their new management server.

    Christian

    :8019
  • Hello Christian,

    Many thanks for your reply.  I do intend to use my own secondary update location, I was just pondering what others viewpoint on it was.

    I am also awaiting V9.7 (but only once we are successfully running 9.5 across the company..) as we have an issue with the Web Protection functionality being incompatible with the ISA 2006 firewall client that we use.  Support have stated that this will be fixed in V9.7, so until then, we cannot make use of Web Protection.

    Best Regards,

    Steve

    :8057