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

New Office - best practise for client updates

Huwy

hi there,

At present we have Enterprise Console v4 installed on a server in our HQ and the clients get their updates from that server i.e. from the share \\HQ-Server-1\SophosUpdate\CIDs\S000\SAVSCFXP)

We have recently opened another office nearby and the clients at present are still retreiving the updates from the central (HQ)server.

To reduce traffic over the link between the 2 sites I have been asked to look into setting the clients to retreive their updates from a server in the new office.

I was therefore wondering what's the best way to go about that. Should I install a new instance of Enterprise Manager on a server in the new office? Or would it be better to replicate the existing share via DFS or whatever?

Thanks in advance,

Huw

:9481


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

    Hi,

    I would suggest installing an additional Sophos Update Manager (SUM) at the other site on a server.  This can update from the parent SUM (on the SEC management server) or Sophos.  I would suggest setting your first sourse as being a UNC path to the parent SUM and maybe Sophos as a secondary for failover purposes.  This will in effect cache you a local distribution point at the remote site so clients pull from that rather than all clients pulling accross the remote connection.

    I would ensure that the new SUM machine is all managed in SEC and the remote SUM is updating ok, creating the distribution locations and then change the updating policy on the remote SUM machine only (You may have to move it into it's own group temporarily to do this) to use it's local source.  This will ensure you have one SAV install at the remote site working using a local distribution point before you start changing the policies of all the clients at the remote site.

    Now it is also posible to convert that remote SUM install into a message relay so that all the RMS traffic of the remote site goes via the local server but I would start with updating as that can get fiddly if not really required.

    Hope this helps,

    Regards,

    Jak

    :9491
Reply
  • 0

    Hi,

    I would suggest installing an additional Sophos Update Manager (SUM) at the other site on a server.  This can update from the parent SUM (on the SEC management server) or Sophos.  I would suggest setting your first sourse as being a UNC path to the parent SUM and maybe Sophos as a secondary for failover purposes.  This will in effect cache you a local distribution point at the remote site so clients pull from that rather than all clients pulling accross the remote connection.

    I would ensure that the new SUM machine is all managed in SEC and the remote SUM is updating ok, creating the distribution locations and then change the updating policy on the remote SUM machine only (You may have to move it into it's own group temporarily to do this) to use it's local source.  This will ensure you have one SAV install at the remote site working using a local distribution point before you start changing the policies of all the clients at the remote site.

    Now it is also posible to convert that remote SUM install into a message relay so that all the RMS traffic of the remote site goes via the local server but I would start with updating as that can get fiddly if not really required.

    Hope this helps,

    Regards,

    Jak

    :9491
Children
No Data
Unfiltered HTML