Enterprise Console 4.5 -- Out-of-Date Computers increases dramatically

Hi,

I've posted a couple of posts to this forum on the subject of "up to date", they may be worth a read:

/search?q= 7511

/search?q= 5078

Essentially the mechanism works for any given client by matching a few fields the client has sent in within a status message (stored in the packages table of the Sophos database) against a package entry containing the same few fields that has been stored sent in by either a SUM or EMLibrary.  The package information put into the system by SUM/EMlibrary is essentially the authority to which all the clients are compared against.

So if the clients show "up to date" unknown but the IDE count, version number etc. is correct, chances are the status message from the current authoritative SUM hasn't arrived yet carrying the currency data to update the packages table with the authoritative package data.

Therefore I would suggest where possible to add the registry key on the SUM where the management server is (I assume that is update from Sophos):

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

to forcibly make that SUM authoritative.  

Making the SUM authoritative means that any status messages coming from that SUM are accepted as the authority as opposed to it being worked out which SUM is and possibly changing.  When doing this you should ensure that the chosen authoritative SUM has subscribed to all subscriptions that all the other SUMs are maintaining to ensure that all package information/conbinations are entered into the database.

The reason for the sudden decrease in out of date machines is when the status message arrives from the SUM.  If you can get that arriving before the clients have the package you will not see machine in the out of date state that aren't in terms of version and data out of date.

If you have any questions after reading the above 2 posts, please reply.

Regards,

Jak

Hi,

I've posted a couple of posts to this forum on the subject of "up to date", they may be worth a read:

/search?q= 7511

/search?q= 5078

Essentially the mechanism works for any given client by matching a few fields the client has sent in within a status message (stored in the packages table of the Sophos database) against a package entry containing the same few fields that has been stored sent in by either a SUM or EMLibrary.  The package information put into the system by SUM/EMlibrary is essentially the authority to which all the clients are compared against.

So if the clients show "up to date" unknown but the IDE count, version number etc. is correct, chances are the status message from the current authoritative SUM hasn't arrived yet carrying the currency data to update the packages table with the authoritative package data.

Therefore I would suggest where possible to add the registry key on the SUM where the management server is (I assume that is update from Sophos):

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

to forcibly make that SUM authoritative.  

Making the SUM authoritative means that any status messages coming from that SUM are accepted as the authority as opposed to it being worked out which SUM is and possibly changing.  When doing this you should ensure that the chosen authoritative SUM has subscribed to all subscriptions that all the other SUMs are maintaining to ensure that all package information/conbinations are entered into the database.

The reason for the sudden decrease in out of date machines is when the status message arrives from the SUM.  If you can get that arriving before the clients have the package you will not see machine in the out of date state that aren't in terms of version and data out of date.

If you have any questions after reading the above 2 posts, please reply.

Regards,

Jak