Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 4981 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

All computers out of date on Enterprise Console 5.1

Norgenator

Hello,

Is there a place to adjust the latency when the computers display they are out of date on the Enterprise Console 5.1.0.1839?

This was fixed on a previous version of Enterprise Console (4.5.1.0). But the registry path \\EE\\ is not on 5.1.0.

I need the fix for the new version.. or maybe it is now a setting that I am missing. I have checked the forums and other tech sites for hours with no luck. Please help!

--

Below is the fix for the old version: 

Link to fix on previous version.

Fix for 4.5.1.0:

"It's a DWORD called ‘‘‘‘UpToDateLatencyMins’’’’ in the registry entry

[HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools]"

:25939


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

    Hi,

    You can create the key, it doesn't exist by default.  

    The question I would have is are you masking another problem by adding it?  The following describes how it works to help you perhaps trace a problem.

    When SUM pulls down a new update, it pushes the update to the CID, E.g.: "\\server\sophosupdate\CIDS\S000\" and once it has updated all the CIDs it needs to it will send back a status message to the management server.  The verison information of this new "update" is then added to the database if the information has come from the authoritative SUM.  This information goes into the "Packages" table of the database with a rollout number of 99999999.  

    Note: Package versions reported by the clients that hasn't come from SUM data don't have a rollout number 999999999 in the packages table.  When machines show as "Unknown" as their up to date status it is because the client has reported a version SUM hasn't to the database.  This may be the case when the SUM status message is slower to reach the database than the clients but should self correct.

    The clients on their polling interval to the CID, pull down the new update, install it and the client sends back a status message. This message contains the same verison information as SUM put into the database for that package and the machine is flagged in the GUI as up to date as the clients, PackageID (computersanddeletedcomputers table) links to the latest Package in the Packages table as maintained by SUM.

    The following will help understand what might be going on:

    • What is the update interval of your clients (updating policy)?
    • What is the update interval of your SUM(s)?
    • How many SUMs do you have?
    • Is the "LastMessageTime" for the SUM machines recent when clients show as out of date?

    Regards,

    Jak

    :25951
Reply
  • 0

    Hi,

    You can create the key, it doesn't exist by default.  

    The question I would have is are you masking another problem by adding it?  The following describes how it works to help you perhaps trace a problem.

    When SUM pulls down a new update, it pushes the update to the CID, E.g.: "\\server\sophosupdate\CIDS\S000\" and once it has updated all the CIDs it needs to it will send back a status message to the management server.  The verison information of this new "update" is then added to the database if the information has come from the authoritative SUM.  This information goes into the "Packages" table of the database with a rollout number of 99999999.  

    Note: Package versions reported by the clients that hasn't come from SUM data don't have a rollout number 999999999 in the packages table.  When machines show as "Unknown" as their up to date status it is because the client has reported a version SUM hasn't to the database.  This may be the case when the SUM status message is slower to reach the database than the clients but should self correct.

    The clients on their polling interval to the CID, pull down the new update, install it and the client sends back a status message. This message contains the same verison information as SUM put into the database for that package and the machine is flagged in the GUI as up to date as the clients, PackageID (computersanddeletedcomputers table) links to the latest Package in the Packages table as maintained by SUM.

    The following will help understand what might be going on:

    • What is the update interval of your clients (updating policy)?
    • What is the update interval of your SUM(s)?
    • How many SUMs do you have?
    • Is the "LastMessageTime" for the SUM machines recent when clients show as out of date?

    Regards,

    Jak

    :25951
Children
No Data