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

No monthly update when updating directly through Sophos

Hello,

My first post :)

I have created a standalone installer package following KB below as some of our computers need to be installed by this way.

http://www.sophos.com/support/knowledgebase/article/67504.html

It is working fine...

Autoupdate location settings are:

* Primary update location = internal server

* Secondary update location = Sophos

We are using a message relay in our DMZ to collect information from our computers that are not always/often connected to our network.

However, i created the package in November 2011 and deployed it also in November 2011 on few computers for testing.

Updates are working well, communication with the management server through message relay, etc...

Since December, i noticed that all computers that are mainly updated from Sophos are displayed with 'Unknown' status in Sophos Console.

The detection data has not been updated to 4.72G (remains to 4.71G version) but IDEs count continue to increase.

I tried to delete status.xml file + force the update ==> same results.

Client version is 9.5.5

Is there a way to update Detection Data and Detection Engine when the main updates are provided by Sophos for some computers (due to budget constarints, we are not able to create a WebCID for the for moment)?

What is the impact to have Detection Data/Engine not updated and only IDEs detected?

Thanks by advance for your Help.

Regards,

Fabrice

This thread was automatically locked due to age.

Parents

0 QC over 13 years ago

Hello Fabrice,

a month has approx. 30.67 days :) - deploying a monthly update to all of the customers and all the distribution network in one shot would mean quite a load for a short period of time and then not much for the remaining 30 days or so. Instead deployment is staged over a few days. Not all licensees will get a new update on the same day and not all products are necessarily updated on the same day (as opposed to IDE updates which are "immediately" available). I just assume that the "CID" for stand alone clients is updated after the warehouse for the SUMs. Keep in mind that your SUM has only one version and the applicable IDEs avaiiable and that the updating mechanism is a little bit different for updating from your CIDs and from "Sophos" - and an "uplevel" client returning to its home CID would complicate things.

Simply put - the client, when comparing its cache to the update location contents, checks whether there are only IDE additions or other changes. The latter trigger the update which installs the newer versions (data, engine, rules, ...).

Christian
:19461
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 QC over 13 years ago

Hello Fabrice,

a month has approx. 30.67 days :) - deploying a monthly update to all of the customers and all the distribution network in one shot would mean quite a load for a short period of time and then not much for the remaining 30 days or so. Instead deployment is staged over a few days. Not all licensees will get a new update on the same day and not all products are necessarily updated on the same day (as opposed to IDE updates which are "immediately" available). I just assume that the "CID" for stand alone clients is updated after the warehouse for the SUMs. Keep in mind that your SUM has only one version and the applicable IDEs avaiiable and that the updating mechanism is a little bit different for updating from your CIDs and from "Sophos" - and an "uplevel" client returning to its home CID would complicate things.

Simply put - the client, when comparing its cache to the update location contents, checks whether there are only IDE additions or other changes. The latter trigger the update which installs the newer versions (data, engine, rules, ...).

Christian
:19461
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data