Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 6 subscribers
  • Views 1430 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

When will *Enterprise* Sophos 7.3.12 be updated *from Sophos*?

stevemaser

We have machines with 7.3.12 installed -- the Enterprise version -- that get it's updates from Sophos directly.

When now trying to run "Scan local drives" a box pops up that says:

Sophos Anti-Virus error

Threat data is too old.  Please update Sophos Anti-Virus

*When* will Sophos be providing the automatic update for 7.3.12 users to 8.0.*something*?

I'm assuming this error messages means all of the 7.3.12-running computers are actually *not* protected?

This seems pretty serious.   If Sophos is still holding back the 8.0.x automatic upgrades (and 7.3.12 is now "insecure"), they are doing a serious disservice to it's customers!

:1010232


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

    Hello Steve,

     

    I'm neither Sophos nor a lawyer so it's actually none of my business - just wondering why you use the SA version and also update from Sophos directly? Is it a Mac-only environment?

     

    How is/was the *home* version of Sophos able to update to SAV8, but the Enterprise version -- which gets it's updates from Sophos -- not

    The AutoUpdate component is the same for managed and SA builds (and the following applies to a site's Update Manager - SUM - as well). When updating from Sophos it looks for some hardcoded, (SAV-)version dependent bootstrap information (what stuff do you have for Mac SAV 7). The server examines the credentials and decides whether the client is entitled to download at all and if, which version and components to return (in form of a catalog). When a new version is available it is

    • not presented to all credentials at the same time - this is to distribute the load on the network over a certain period
    • for the first weeks presented only when specifically requested (AutoUpdate does this when the version has already been upgraded, SUM can be instructed by an administrator to request the new version) - this is to allow sites some control over the rollout of new versions

    Clearly as long as the "old" version is not actually retired it must be returned to all clients not explicitly requesting the new one. If a site has elected to stay at the old version for yet some time and clients occasionally update from Sophos (because it is configured as Secondary) the would suddenly upgrade - only to be forced to downgrade when they return to their home network. Thus as long as the old version is available to sites (and 7.3.12 is) it has to be assumed that it is not desired that a client is force-upgraded by a download from Sophos.

    Having said this, in order to use a new version on SA clients updating from Sophos only before the old one is retired it has to be installed manually (on Windows there's a hack making AutoUpdate look for the new version and it might be that something similar is possible on the Mac, but I don't know).

     

    Christian      

    :1010332
Reply
  • 0

    Hello Steve,

     

    I'm neither Sophos nor a lawyer so it's actually none of my business - just wondering why you use the SA version and also update from Sophos directly? Is it a Mac-only environment?

     

    How is/was the *home* version of Sophos able to update to SAV8, but the Enterprise version -- which gets it's updates from Sophos -- not

    The AutoUpdate component is the same for managed and SA builds (and the following applies to a site's Update Manager - SUM - as well). When updating from Sophos it looks for some hardcoded, (SAV-)version dependent bootstrap information (what stuff do you have for Mac SAV 7). The server examines the credentials and decides whether the client is entitled to download at all and if, which version and components to return (in form of a catalog). When a new version is available it is

    • not presented to all credentials at the same time - this is to distribute the load on the network over a certain period
    • for the first weeks presented only when specifically requested (AutoUpdate does this when the version has already been upgraded, SUM can be instructed by an administrator to request the new version) - this is to allow sites some control over the rollout of new versions

    Clearly as long as the "old" version is not actually retired it must be returned to all clients not explicitly requesting the new one. If a site has elected to stay at the old version for yet some time and clients occasionally update from Sophos (because it is configured as Secondary) the would suddenly upgrade - only to be forced to downgrade when they return to their home network. Thus as long as the old version is available to sites (and 7.3.12 is) it has to be assumed that it is not desired that a client is force-upgraded by a download from Sophos.

    Having said this, in order to use a new version on SA clients updating from Sophos only before the old one is retired it has to be installed manually (on Windows there's a hack making AutoUpdate look for the new version and it might be that something similar is possible on the Mac, but I don't know).

     

    Christian      

    :1010332
Children
No Data