Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 0 subscribers
  • Views 11547 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

enterprise console trial

rino19ny

hi, if this is not the correct place kindly direct to the right one.

we're evaluating Sophos and have downloaded and installed the enterprise console as a trial.we're now deploying to the server (where the console is installed) and to my computer (already have kaspersky 6.x installed). in both instances, i keep getting in the console that the protection is out of date although if i hover the mouse over the sophos endpoint icon on the lower right corner of the screen, it says last checked for updates is today.

why does it keep  saying out of date? the update manager have already downloaded the latest.

:50466


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

    Hello,

    That registry key shouldn't be neccessary unless there is quite a complex updating hierarchy.  The way it works is as follows:

    1. The Sophos Update Manager (SUM) updates from Sophos, downloads files and places them in the CIDs, e.g.

    \\server\sophosupdate\CIDs\S000, etc.  The number of CIDs depends on the number of subscriptions and the number of sub-directories in a Sxxx depends on the number of packages in a subscription.

    2. When SUM has completed writing the packages to all the update locations, SUM sends back a message, via the Sophos Remote Management System (RMS) component to the management server and stores the package information in the database (Packages table).

    3. The clients are checking to the CID, every 10 mins, so you'd expect, that SUM updates the CID, up to 10 minutes laters, the clients notices the update, updates, and sends back a status message to the management server.

    4. The management server can then compare the package info from SUM, with the package info from the client and make a comparision, E.g. Up to date.

    The only problem I'm aware of in this area is if SUM is maintaining a large number of distribution points, or update locations over poor links, such that it takes a long time to push updates to all CIDs, and therefore for SUM to send back it's status message at the end of the process.  In this scenario, if a client updates from one of the first CIDs to be updated, it could potentially send back a status message before SUM has sent in a status message.  In this case, the computer would show as Unknown in terms of up to dateness until SUM send in a status message at the end of the update.  This is race condition is pretty rare and can be managed by installing SUMs in remote locations, removing unwanted packages, changing the clients update interval, etc..

    Regards

    Jak

    :50476
Reply
  • 0

    Hello,

    That registry key shouldn't be neccessary unless there is quite a complex updating hierarchy.  The way it works is as follows:

    1. The Sophos Update Manager (SUM) updates from Sophos, downloads files and places them in the CIDs, e.g.

    \\server\sophosupdate\CIDs\S000, etc.  The number of CIDs depends on the number of subscriptions and the number of sub-directories in a Sxxx depends on the number of packages in a subscription.

    2. When SUM has completed writing the packages to all the update locations, SUM sends back a message, via the Sophos Remote Management System (RMS) component to the management server and stores the package information in the database (Packages table).

    3. The clients are checking to the CID, every 10 mins, so you'd expect, that SUM updates the CID, up to 10 minutes laters, the clients notices the update, updates, and sends back a status message to the management server.

    4. The management server can then compare the package info from SUM, with the package info from the client and make a comparision, E.g. Up to date.

    The only problem I'm aware of in this area is if SUM is maintaining a large number of distribution points, or update locations over poor links, such that it takes a long time to push updates to all CIDs, and therefore for SUM to send back it's status message at the end of the process.  In this scenario, if a client updates from one of the first CIDs to be updated, it could potentially send back a status message before SUM has sent in a status message.  In this case, the computer would show as Unknown in terms of up to dateness until SUM send in a status message at the end of the update.  This is race condition is pretty rare and can be managed by installing SUMs in remote locations, removing unwanted packages, changing the clients update interval, etc..

    Regards

    Jak

    :50476
Children
No Data
Unfiltered HTML