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

Domain DFS share as update source?

Hi,

Has anyone had any experience (good or bad) with using a
domain based DFS share to distribute updates? (EC 4.7)

I read in one post that it wasn’’’’t supported & there doesn’’’’t
seem to be many comments at all on the matter either way & can’’’’t find
anything in the Sophos documentation.

We are currently using SUM’’’’s spread across locations to
distribute updates as per the documentation, but as there are already DFS shares replicated to all
locations were wondering if this might be a more efficient way of getting
updates around the network. IE: setting \\DOMAIN\SophosUpdate
as a primary update source & letting DFS take care of deciding which server
clients should get updates from.

Thanks in Advance,

:19205


This thread was automatically locked due to age.
  • Hi,

    I suspect that it's fine for resolution but you may run into problems if you use it for replication.

    When SUM updates a share, it writes the master.upd file last as this is the file the clients ping to check for updates to the package, if that was moved first (well anything other than last), clients would believe there to be an update, try and fetch a file referenced in the checsum file and it may not have been replicated yet, leading to a failed update.

    So DFS might be a good way to reduce the number of update policies (as they could all point to the same DFS path), but then you could do that with local site DNS trickery anyway I suppose.  

    I would suggest instaling additional SUMs an have them pull updates locally where possible.

    Regards,

    Jak

    :19207
  • Thanks Jak,

    Sounds like we are best to stick with what we are already doing.

    :19209
  • the advantage of using DFS, independent naming of the share, can be maintained by using DFS without actually using the DFS-recplication. The update manager can still make the updates and keep the shares in sync with master.upd updated last.

    regards,

    Bart

    :36983