[Release Notification] Endpoint Security and Control version 10.8.4.4 VE3.74.1 for Windows released

Hello all,

I can confirm that AutoUpdate 5.15.166.166 detects the corrupt iupd.cfg (the section with the products is missing causing AU to not consider SAVXP and RMS when checking for updates causing the computer to be out of date while AU claims to have Updated successfully) and repairs it.
ConfigurationImpl:: Bad iupd.cfg file.
ConfigurationImpl:: repairing corrupt config file using C:\ProgramData\Sophos\AutoUpdate\DefaultConfig
Just checked on an endpoint that was stuck on 10.6.4 (sic! - they aren't all under our jurisdiction ...) and after updating to 5.15 subsequently updated to SAV 10.8.4.4

Christian

Hello

Is autoupdate version 5.15.166 or 5.15.166.166?  We curently run 5.15.166.

Our Sophos Anti-virus is still at version 10.8.4.227

Paul Jr

Hello

Is autoupdate version 5.15.166 or 5.15.166.166?  We curently run 5.15.166.

Our Sophos Anti-virus is still at version 10.8.4.227

Paul Jr

Hello Paul Jr,

I'm practically on vacation so off the top of my head: Depends on where you look whether you see the fourth number (whatever it is called). Think I've mentioned it that the only change from 10.8.4.2 to 10.8.4.4. is the new AutoUpdate 5.15.166(.166).

Christian

Euh !?!?!?!?!?

We run AutoUpdate 5.15.166 ... BUT, we also run 10.8.4.227 ...  BUT, the difference between 10.8.4.2 and 10.8.4.4 is the addition of AutoUpdate 5.15.166.

What is this ? Do I get it correctly ???

How one is supposed to CLEARLY know he is running 10.8.4.4 ???  And why do that number "10.8.4.4" exist if it's not shown anywhere on any revision ?

Kneel before insanity ?

Paul Jr

Hello Paul Jr,

as of late, actually some ago, it became apparent that the version control system introduced in 2013 no longer fitted all uses. The version used to be the one of SAV proper. Initially Cloud/central used it as well but from the beginning there was an ambiguity as there were clearly two products that differed in their components.and the SAVversion equals Product version concept was no longer meaningful.

Only SEC/SESC retained the old system and is stuck with it and its deficiencies (and its use of the SAVversion as indicator). Guess Sophos don't want the SAVversion to fork and thus we have this confusing numbering at the moment.

Christian

Thanks for answering.

I was afraid I lost all my logic.  Happy to realized it's not entirely me after all.

Let's put it on the already thick pile of basic requests: -> Clear "versioning". 

Paul Jr Robitaille