Full Control Cache Update Locations
Control Cache Update Locations- We should have the ability to set the cache update location in Sophos Central. We have multiple locations and we see computers NOT updating locally and reaching across the MPLS and IPSEC tunnels to update from a remote locations instead of updating locally. This creates unneeded traffic on our network and slows down update time. Please fix this or give us full control to set primary and secondary update locations by computer groups.
And it´s not only the unnecessary traffic, look at the log files. If you have many updatecaches in other sites, which are not reachable from your client, but they are nearer from the "ip-distance", the client wait very long (80 seconds per update cache) until he get the correct update cache. In our site, we have waiting times up to ten minutes, until he get his correct cache.
This system that sophos is using here, is far away from any practice in a big company.
Still waiting for this feature to be looked at. This is causing much un-necessary traffic on our MPLS links
The logic for determining proximity to Update Cache for downloads should be determined based on speed and not IP address class as it is currently.
Link the existing “--messagerelays=” installer flag to utilize not only the Message Relay feature of the Update Cache but also the actual Update Cache
OR Add “--updatecaches=”
Allow the use of Sophos Computer Groups for Update Cache assignments (there’s already a flag to assign the computer to a specific group)
Same as Ken's experience here: First they tell you it's determined by speed and then they come out of the woodworks and tell you it's some arbitrary proximity determination based on IP range...
Sad really that this request has been sitting here for a year & that fact doesn't give me much hope for this ever to be implemented properly.
Another good idea poorly executed...
The way how Sophos calculates the distance to a update chache is not practicable and should urgently improved!
I was originally told that clients would ping servers in update cache list and then pull updates from the one with best response. Since then I was informed that it looks at the IP on the client and on the update cache and compares the bits and chooses one that is closet to match but that does not take into consideration any distance or response times. I have removed ALL my update caches because of this . Often Clients in the US and Canada where reaching out to Japan or Germany because it did not see the update cache that was local but on a different subnet. Until this is changed I will not use update Caches